3 ms·
> Has JavaScript changed for the worse? Clarification - I don't think JS has changed for the worse, but I do not think it is clear that all the changes have be
by game_the0ry 6y ago
> Has JavaScript changed for the worse?
Clarification - I don't think JS has changed for the worse, but I do not think it is clear that all the changes have been for the better, both for the language and the ecosystem.
I see it as a double edged sword.
Take the example of handling asynchronous operations - async/await is good solution for that. But now you will be working in code bases with callbacks, promises, async/await, and possibly even generators - with generators being an example of an area that was not a clear improvement in the right direction, but an experiment now obsolete because of async/await.
I'm a fan of improvement, but nowadays I try not to pick up the latest trend for concern that it might be obsolete in the near future. You demonstrate this - you picked something you like (ember) and just stuck with it. Ember solves problems, it works, no reason to refactor your ember projects to react.
- cpr 6y agoQuite the contrary: Generators are quite useful in their own right, independently of asynchronicity.