The second sentence really tells all. " Just learned Backbone.js and only found out it’s already out of fashion." This is why critical thinking and a sight of the big picture is so important. Who cares if something is fashionable? Does Backbone help you solve your problems? Yes? then use it. No? Don't use it.
This really bears repeating over and over again, and I think it's a corollary of "start by writing the dumbest thing that can possibly work."
If you start with dumb, simple things, the problems become more obvious. Dumb simple things tend to shake out the parts that are tedious to build, or non-conformant, or confusing to read, or hard to maintain. It may be that Backbone (or any of the dozens of other gizmos) alleviate the problems, but you really have to understand the problem first.
I really think a lot of people are seduced by the marketing of various tools and frameworks into thinking they have (or will have) problems that they don't actually have. Then they end up with over-engineered solutions that are all the things they hoped to avoid.
Don't meant to criticize backbone, or any other framework (or language, or platform). A fancy, hip tool can be just thing. The question is: do you know what "the thing" is really for, and does it fit your situation?
I hear what you're saying, and I basically agree. However, I still see some shops building new product with Jakarta Struts, hand coded javascript, and no continuous integration. They spend way too much time doing things that could be automated, which would allow them to spend more time on quality, or more features. (Say, if you want to use a java webstack, have you heard of spring & jquery, and maybe you should try hudson for your builds?) So, its also important to keep abreast of whats happening in the field, so long as you don't fetishize the newest/latest thing.
I agree 1000% - very good point. The best tools (for you) are the ones that solve the problems that bug you the most and feel the most "right". It's a personal thing.
For example: In my case, I used to write a lot of plain HTML. I found it got annoying to type brackets and keep track of all the closing tags. So I tried ZenCoding, and it helped, but only on creation, not on editing. I finally settled on haml, because to me (not everyone), it solves the exact problem that I found troublesome and gave me the results that I like. No closing tags, cleaner markup. Others may disagree, but that doesn't matter - I like it for my purposes, and that's all it takes.
So to your point - learn the underlying tech, find your personal pain points, and use the tools that best solve them for you.
Haml is soo 2012. :) Try Jade (http://jade-lang.com/), it has a much cleaner syntax and integrated markdown support. You can even use it as a preprocessor for other templating languages.
No, this isn't correct. Fashionability has nothing to do with it. PHP is not fashionable - in fact I'd argue that right now it might be the most despised language around - but upstream development isn't slowing down at all but in fact speeding up and it's being improved at a very rapid pace as of late.
I think choosing fashionable tools because you think upstream maintenance will continue into the future is actually misguided. In my experience the old, boring tools are what have staying power. The new fashion comes out, gets lot of attention, then the next big thing steals its thunder and you start seeing your fashionable tool's upstream updates go from a stream to a trickle to droplets here and there and finally you start to wonder if the project is dead.
Maybe you meant something different but just by going off what you said I'd say you're wrong. There's a difference between something popular with staying power and the latest fashion. I think the JavaScript world, node.js in particular, is in a period where for all its new hotness we'll start to see a lot of these popular modules just die. I think node may soon become a good example of why fashionable tools are not to be relied upon. That isn't to say that node itself is going anywhere but rather that its in a transition period from new hotness to something more stable and the NPM packages are what we'll see start dropping like flies before we can be sure what we can count on later.
Right, the difference between "fashionable" and "unfashionable" is just what the cool kids on HN say it is.
To take your example on a stroll, PHP is like regular (non-skinny) blue jeans. Everyone knows them, most people use them, every store carries them, at one point in history they were revolutionary, they're probably never going to go away. But the cool kids say skin-tight crazy-colored jeans are the new hotness...
I think this goes for the latest and most hyped where the communities could be small. A good middle ground would be well-established projects with a relatively big community and preferably strong industry ties. Usually projects over a certain size will survive by some faction of the community even if it's losing steam or something dramatic happens sort of like MySQL and MariaDB.
