Microsoft is fragmenting their developers tools so much that it becomes so diluted that no one cares anymore. There is no point it going to TypeScript 3.0 if they are going to release the next TypeScrip in 1 month from now, then another one, and another one and another one.
Rule number one in successful projects: "Pick one and stay with it until it is completed."
Don't change your language, framework or tools midway your project because you create a setup that will fail!
I recall from the blog post that the changes were somewhat small. That said, I think you have a very good point reg. frequent changes. It is something that has also affected the Scala community negatively (though the changes are not nearly as frequent/large for Scala as for TypeScript, I believe). I believe it is however something of a trade-off - if you do not have frequent changes, then it can become much harder to evolve and develop the language. I wonder if TypeScript will slow down its evolution. I guess it won't slow down a lot if it slows down, for the rest of the browser front-end environment tends to change rapidly, and will likely continue to do so for at least some years to come.
The frequent changes likely hurts (much) more the larger and/or numerous your code bases are in TypeScript.
This rapid release of tools have given even most die hard's of latest technologies a burn out where I work. They used to be excited now they stopped caring. Maybe they started to realize that they are more busy updating to the latest tools and learn new stuff than being productive.
It sounds like you/they are front-end devs. I do not work in that field, but if I was, I would seek to learn the core and most successful theories and ground concepts as much as possible, though that is easier written than done. It seems like a fairly active field, and if it is like distributed and concurrent programming, even the fundamental thoughts, ideas and approaches are (still) evolving, changing and developing. That way, it might be more feasible to generalize and re-use what one learns. The learning of the specific APIs are typically much less reusable and long-term useful. So, if possible, sticking to a few frameworks and technologies, switching/updating every few years, be productive in them and earn your salary, and learn the most successful concepts and theories seem like one way that might be OK. And also go after what interests you and what fits your skillsets, talents and plans.
4 comments
0 u/roznak 02 Aug 2018 23:50
Microsoft is fragmenting their developers tools so much that it becomes so diluted that no one cares anymore. There is no point it going to TypeScript 3.0 if they are going to release the next TypeScrip in 1 month from now, then another one, and another one and another one.
Rule number one in successful projects: "Pick one and stay with it until it is completed."
Don't change your language, framework or tools midway your project because you create a setup that will fail!
0 u/notenoughstuff [OP] 03 Aug 2018 16:16
I recall from the blog post that the changes were somewhat small. That said, I think you have a very good point reg. frequent changes. It is something that has also affected the Scala community negatively (though the changes are not nearly as frequent/large for Scala as for TypeScript, I believe). I believe it is however something of a trade-off - if you do not have frequent changes, then it can become much harder to evolve and develop the language. I wonder if TypeScript will slow down its evolution. I guess it won't slow down a lot if it slows down, for the rest of the browser front-end environment tends to change rapidly, and will likely continue to do so for at least some years to come.
The frequent changes likely hurts (much) more the larger and/or numerous your code bases are in TypeScript.
0 u/roznak 03 Aug 2018 19:26
This rapid release of tools have given even most die hard's of latest technologies a burn out where I work. They used to be excited now they stopped caring. Maybe they started to realize that they are more busy updating to the latest tools and learn new stuff than being productive.
0 u/notenoughstuff [OP] 03 Aug 2018 19:56
It sounds like you/they are front-end devs. I do not work in that field, but if I was, I would seek to learn the core and most successful theories and ground concepts as much as possible, though that is easier written than done. It seems like a fairly active field, and if it is like distributed and concurrent programming, even the fundamental thoughts, ideas and approaches are (still) evolving, changing and developing. That way, it might be more feasible to generalize and re-use what one learns. The learning of the specific APIs are typically much less reusable and long-term useful. So, if possible, sticking to a few frameworks and technologies, switching/updating every few years, be productive in them and earn your salary, and learn the most successful concepts and theories seem like one way that might be OK. And also go after what interests you and what fits your skillsets, talents and plans.