5 ms·

> It was nice ten years ago when JavaScript was absolutely horrendous but not now. ECMAScript 5 was released in December 2009, Coffeescript first appeared the

> It was nice ten years ago when JavaScript was absolutely horrendous but not now. ECMAScript 5 was released in December 2009, Coffeescript first appeared the same month with release 0.1.0. What was absolutely horrendous about ECMAScript 5? edit: Javascript 1.8 shipped with Firefox 3 in June 2008.

keymone 9y ago
i don't even.. for people making these claims there's just no way to convey how horrific js development was until quite recently (it still is far worse than most popular languages out there tbh) other than inventing a time machine and sending you there, but then it's a kind of punishment i wouldn't want upon my worst enemy. browser fragmentation rings any bells? were you actually doing js dev back then?
- tigershark 9y ago
  What is the connection between browser fragmentation and coffescript syntax? Coffescript was born to have a lighter JavaScript-like syntax, not to remove browsers fragmentation.
  - keymone 9y ago
    the connection is between fragmentation and claim that ecmascript and js 1.8 were released and everything magically became great in december 2009 as was implied by the grandparent.
    - oneweekwonder 9y ago
      > magically became great in 2009 as was implied by the grandparent. I implied nothing, I asked you a question. Might have been a bit open ended but you made a claim that did not reflect with my reality. So I did a reality check. If there was a "magic" moment I will give chrome released late 2008 and firebug 1.4 released early 2009 the attribution for a turning point in webdev.
      - keymone 9y ago
        > I implied nothing X was horrible ten years ago -> but X' was actually released 10 years ago, what was horrible about X'? sorry, there is no way for me to interpret that other than implying that my statement was false. there were multiple magic moments, but js didn't stop being horrible on daily basis for another couple years. having chrome debugger or firebug didn't save you from having to support internet explorer, did it?
        oneweekwonder 9y ago
        > save you from having to support internet explorer, did it? I showed IT how we can keep firefox updated on all our machines using AD. External sites said best viewed with firefox and mentioned ie6/ie8 a steph-child. My solution not acceptable for everybody, but my employers were happy and I could continue being productive without worrying to much about ie.
        keymone 9y ago
        lucky you
- oneweekwonder 9y ago
  > were you actually doing js dev back then? Actually started webdev in 2004 php3 and basic js. Back then the joke was "nobody know how to code js, everybody just copied this one piece of code and mutated it from there". It sadness me to think such behavior is more entrenched in todays development environment with sites like stack-overflow. Don't get me wrong I'm grateful that sites like SO exist. I'm also grateful that when I had to learn the ropes or solve "hard problems", I could not turn to my browser. Like I do today; every fsck'ing time; because it is easier and I'm lazy.

keymone 9y ago

i don't even.. for people making these claims there's just no way to convey how horrific js development was until quite recently (it still is far worse than most popular languages out there tbh) other than inventing a time machine and sending you there, but then it's a kind of punishment i wouldn't want upon my worst enemy. browser fragmentation rings any bells? were you actually doing js dev back then?

tigershark 9y ago
What is the connection between browser fragmentation and coffescript syntax? Coffescript was born to have a lighter JavaScript-like syntax, not to remove browsers fragmentation.
- keymone 9y ago
  the connection is between fragmentation and claim that ecmascript and js 1.8 were released and everything magically became great in december 2009 as was implied by the grandparent.
  - oneweekwonder 9y ago
    > magically became great in 2009 as was implied by the grandparent. I implied nothing, I asked you a question. Might have been a bit open ended but you made a claim that did not reflect with my reality. So I did a reality check. If there was a "magic" moment I will give chrome released late 2008 and firebug 1.4 released early 2009 the attribution for a turning point in webdev.
    - keymone 9y ago
      > I implied nothing X was horrible ten years ago -> but X' was actually released 10 years ago, what was horrible about X'? sorry, there is no way for me to interpret that other than implying that my statement was false. there were multiple magic moments, but js didn't stop being horrible on daily basis for another couple years. having chrome debugger or firebug didn't save you from having to support internet explorer, did it?
      - oneweekwonder 9y ago
        > save you from having to support internet explorer, did it? I showed IT how we can keep firefox updated on all our machines using AD. External sites said best viewed with firefox and mentioned ie6/ie8 a steph-child. My solution not acceptable for everybody, but my employers were happy and I could continue being productive without worrying to much about ie.
        keymone 9y ago
        lucky you
oneweekwonder 9y ago
> were you actually doing js dev back then? Actually started webdev in 2004 php3 and basic js. Back then the joke was "nobody know how to code js, everybody just copied this one piece of code and mutated it from there". It sadness me to think such behavior is more entrenched in todays development environment with sites like stack-overflow. Don't get me wrong I'm grateful that sites like SO exist. I'm also grateful that when I had to learn the ropes or solve "hard problems", I could not turn to my browser. Like I do today; every fsck'ing time; because it is easier and I'm lazy.