He forgot the part about jumping on every new JS library bandwagon when its still in beta and impressing all his friends with a new framework nobody has heard of.
Your comment just reads as "I've been using MooTools since my pappy was alive! It works so why change it."
If you want to stagnate and use the same tools, go for it. Other people will continue to push the envelope and improve the day to day lives of thousands of programmers everywhere.
If people were afraid to try new things, we wouldn't have things like Ember, or React, or Meteor, or Mythril, or Rails. You don't have to try every single thing that comes out, but at least be aware of them, and give them a cursory 30 minutes glance. You like programming, I assume? This should be fun, and it is!
> If people were afraid to try new things, we wouldn't have things like Ember, or React, or Meteor, or Mythril, or Rails.
Or washing machines. Or cars. Or penicillin.
The anti-innovation mindset that pervades in this industry just baffles me. Sure, don't rewrite the accounting system every time a new framework comes out, but don't knock those forging the future either. (I know you weren't, I'm adding to your reaction to the parent.)
The anti-innovation mindset that pervades in this industry just baffles me.
Developers in the industry are often in the business of selling their experience with particular technologies. New technologies becoming popular reduces the market value of that experience. The "anti-innovation" mindset -- and more specifically the public dismissal of new alternatives -- is often simple self-interested marketing.
There's not a problem with trying to build new things, quite the opposite. The problem is not so much with the creators but with the adoptees. Just because you're using something "new", that does not give you the right to say that whatever else someone is using that's not what you are using, shit. That and writing bullshit comparison articles between X and Y and proclaiming that X is amazing and you are lame and outdated if you are still using Y. If there's a profession that's as full of posers and hipsters this has to be it.
> Your comment just reads as "I've been using MooTools since my pappy was alive! It works so why change it."
I didn't mean it to read like that - I'm not against new frameworks, just developers who jump on them and think they are the greatest thing since sliced bread before they're really vetted and most of the bugs have been worked out.
Comments
He forgot the part about jumping on every new JS library bandwagon when its still in beta and impressing all his friends with a new framework nobody has heard of.
Your comment just reads as "I've been using MooTools since my pappy was alive! It works so why change it."
If you want to stagnate and use the same tools, go for it. Other people will continue to push the envelope and improve the day to day lives of thousands of programmers everywhere.
If people were afraid to try new things, we wouldn't have things like Ember, or React, or Meteor, or Mythril, or Rails. You don't have to try every single thing that comes out, but at least be aware of them, and give them a cursory 30 minutes glance. You like programming, I assume? This should be fun, and it is!
Or washing machines. Or cars. Or penicillin.
The anti-innovation mindset that pervades in this industry just baffles me. Sure, don't rewrite the accounting system every time a new framework comes out, but don't knock those forging the future either. (I know you weren't, I'm adding to your reaction to the parent.)
Developers in the industry are often in the business of selling their experience with particular technologies. New technologies becoming popular reduces the market value of that experience. The "anti-innovation" mindset -- and more specifically the public dismissal of new alternatives -- is often simple self-interested marketing.
There's not a problem with trying to build new things, quite the opposite. The problem is not so much with the creators but with the adoptees. Just because you're using something "new", that does not give you the right to say that whatever else someone is using that's not what you are using, shit. That and writing bullshit comparison articles between X and Y and proclaiming that X is amazing and you are lame and outdated if you are still using Y. If there's a profession that's as full of posers and hipsters this has to be it.
That's hyperbole though - not once have I seen an article say something like "Use gulpify, browseriffy sucks and you're a shit developer."
I didn't mean it to read like that - I'm not against new frameworks, just developers who jump on them and think they are the greatest thing since sliced bread before they're really vetted and most of the bugs have been worked out.