19
lig1
4y

Me listening about PHP advantages

Comments
  • 0
    yet i do know when and why it is appropriate to use php
  • 4
    @DarkMukke I believe it's ok to develop devRant backend using it
  • 2
    wtf seriously

    wat animal is thatttt
  • 0
    @leviathan07 a sleepy one
  • 0
    @leviathan07 it's a sloth;

    so what's the language for the web in 2016? python, ruby, c#, java?
  • 0
    @orijin exclude Ruby, add es6 and you've just guessed 4 mature languages for almost anything
  • 0
    @lig1 how could i forget js!?

    *goes stand in a corner*
  • 0
    @orijin btw js was complete shit before es6, specifically es2015 is really usable already
  • 2
    Sloths are always awesome. As are penguins 😁
  • 2
    @lig1 you realize es6 and es2015 are the same?
  • 0
    @orijin I know they are not. At least one obliged the other. You should read 'bout that
  • 4
    @lig1 Sorry mate, but it is you that need a bit of reading 😃

    The official name is "ECMAScript 2015 Language" and it's the 6th Edition of the ECMA-262 standard. There for two handy abbrevations: ES6 and ES2015.

    However there is already 7th installation of the standard most notably introducing async/await functionality: "ECMAScript 2016". And ES2016 is popping up as the short name for this one.

    While ES2016 and ES6 are not the same, ES2015 is exactly the same as the latter.
  • 2
    @orijin not gonna check your facts but I would say "case closed" 😄
  • 0
    @orijin it is true that es6 was renamed to es2015 at the time it was draft. So, most of the linters treat es6 as something that is not yet es2015, a draft. Often this means no imports...
  • 1
    @lig1 again, there was no rename. ECMAScript 2015 Language was up to recently reffered to as ES6 by people when ES2015 became more popular for the same language version.

    And what is so shit about ES5? Besides nicer syntax, symbols, generators, typed arrays and some date/number/string functions, everything else was already possible.

    I'm not saying ES6 doesn't introduce much needed improvements but ES5 wasn't shit.
  • 1
    and here i'm stuck still have to support IE8
  • 0
    @orijin there was versioning theme change. They decided to use years when es6 was at the draft stage
  • 0
    @orijin nice things are modularity and syntax sugar that makes it at least minimally usable
  • 0
    @DarkMukke so sorry to hear that :(

    if you avoid getters and setters you can transpile it with babel for full ie8 support.

    also classes with super need the loose option for pollyfills to work correctly in ie8
  • 2
    @orijin yeh i know, use poly fills the whole time, but sometimes i think why should i support all these IE people, do I really want them as my customers ?
Add Comment