3 ms·
I think OP makes some good points. And missed an opportunity to another one. The transition from "infatuation" to "grudging resentment" (recognizing the fundam
by jrochkind1 9y ago
I think OP makes some good points. And missed an opportunity to another one.
The transition from "infatuation" to "grudging resentment" (recognizing the fundamental problems with the approach and how they get in your way) is likely to happen with _any_ platform/framework.
When you the emoter develops more experience with it, and also when _it becomes more mature_. A less mature framework, problems that get in your way -- or legit use cases there's no convenient solution for -- can be explained away as "well, it just hasn't gotten there yet." They're still getting in your way, but you forgive it. Even when the things that were easy in the last framework are hard in the new one -- it's just not there yet, and hey, these _other_ things are easy that used to frustrate me a lot!
But eventually it will be mature, and it will still have problems, including fundamental ones with it's approach that get in your way, and also always including (for something mature) "legacy" problems, where most people now realize some choices could/should have been made differently, but it's too hard to change now (for backwards compat, and just cause so much code has been built up).
Leaving the mature thing you have become good at for the new exciting immature thing (you aren't yet expert enough at to see the flaws in) will provide temporary relief at best. The grass is always greener.
[This does not neccesarily apply to some things that are _just bad_. Things that people are using despite the fact that they are _not_ helping them develop quality software efficiently. Those things should just be left. Ultimately one would like to believe that a mature solution that helps you develop software more efficiently will win out in the end -- we know there are 'political', 'marketing', and other considerations that make this not always true. But I want to draw attention to the fact that we are not good at judging whether a new immature framework/platform/language/ecosystem we have little experience with will actually help us develop quality software more efficiently than the mature thing we are expert with, and know all it's warts.]