It's that time of the year when you are creating a new repo for some reason and the choice is to typescript or not to typescript.
You decided to t...
For further actions, you may consider blocking this person and/or reporting abuse
This is a great round op of questions. I tend to see the majority of developers, just following the hypetrain of new frameworks. without thinking about how the project would look in 1-2 years time. Deno just released their first production ready version, and im still curious to see how it will perform in the next year or so.
I always try to first look for the best solution that fits my business needs first, then i look to see if any new frameworks might be usefull or not. But i always go with the idea, that v1 of each new framework is not worth it yet.
But what i have learned, is that it is always worth it, to ensure that the project im developing, can be completly migrated to another framework without much work. This of course cost up front in development time, but i believe it to be better to be prepared for the future, than just joining a hype train.
Hype trains are for entertainment, not for software development.
So true. V1 is usually for hobbyists and for "my first home page" type of projects.
Couldn't agree more, without proper abstractions in long-lived projects you are going to pay for an initial development speed boost of a framework 1000x in later project stages. At least that's my subjective experience