Personally it's a combination of wariness and weariness. Wary of getting onto the new–new hotness bandwagon just because it’s the new–new thing, and weary of b

Personally it's a combination of wariness and weariness. Wary of getting onto the new–new hotness bandwagon just because it’s the new–new thing, and weary of being pushed into a new–new thing because it’s the new–new thing and not necessarily the best solution for the problem at hand. Increasing my productivity is irrelevant if it decreases usability or performance of whatever it is I’m building. If it isn’t serviceable, or maintainable, I won’t consider it. If it’s a proprietary solution that depends on the company surviving, I won’t consider it. For me it’s a tradeoff of risks. Will the benefit of rewriting everything, again in this new language and framework pay off in reduced operational or service costs or improved performance? If it won't, then investing money and time chasing after the new–new thing just seems to be a waste.