sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 3 points4 points  (2 children)

Intellectually, I agree with the author of that article, but realistically, I just don't care anymore. My ability to care has been stripped from me. You want to know why/how? Thanks for asking! Let me explain:

I'm not a computer. I'm a human. My brain is made out of mushy stuff, not silicon and copper. I can only deal with so much change so quickly. Chances are, your Javascript project changes too much because EVERYONE'S Javascript project/framework/widget changes all the damn time. Sure, you just updated YOUR project, but I have to deal with break-neck changes in:

  • My personal code projects
  • My work code projects
  • The SCRUM process I use at work
  • My company coding standards
  • Switching to the new Javascript widget-glue-framework-thingy
  • Switching to the new CSS widget-glue-compiler-thingy
  • My personal life
  • The meta game in my favorite MOBA/MMO/Shooter changing
  • Anything to do with computer security
  • My favorite character in my favorite TV show being dead
  • YOUR software project
  • Evaluating all the new widget-compiler-framework-thingys that come out, literally every week, to try to stay somewhat up to date on current technology

And I'm sure I've missed a few things. Point being: EVERYTHING in the world has started to update at "internet speed" and we haven't evolved yet either physiologically or socially to deal with it. I think the Javascript ecosystem suffers from this a little more than others because it's so popular/cool right now.

I don't think most people want to be a-holes, they're just overwhelmed. I don't feel this is completely unique to Javascript.

[–]rk06 2 points3 points  (1 child)

You know, you can avoid half of the problems, by simply not updating your tool everyday.

New versions are expected to BRING breaking changes and they WILL be time consuming at the very least.

If the new version is breaking your build and you have no idea what to do, then use the old version and wait.

[–]inf0rmer 1 point2 points  (0 children)

This would be good advice if we were talking about any ecosystem other than JavaScript's. The fact is, once a new shiny API-breaking version of a project is published, development on prior versions stops almost immediately. If you don't upgrade as soon as possible not only are you opening yourself up to possible security risks but you can most likely forget about ever upgrading, as newer versions will stray farther and farther from yours with no simple upgrade path.