4 ms·
I have to admit, I’ve been avoiding TypeScript and React for any professional projects. TypeScript due to lack of experience, but I understand the benefits. R
by adreamingsoul 5y ago
I have to admit, I’ve been avoiding TypeScript and React for any professional projects.
TypeScript due to lack of experience, but I understand the benefits.
React due to many reasons, but most of which is that I don’t agree with the “benefits”.
I have been working with the Frontend for over a decade and have been on the forefront of its progression. KnockoutJS was a pivotal moment and cemented what followed with Backbone, Angular, Vue, and React (and several others).
It don’t think the current state of development is going in the right direction. But that’s just my opinion and a wild one at best.
- onion2k 5y agoThere's no reasonable argument that you can make in favor of Knockout, Backbone (I hope you mean Marionette though... no one used Backbone on its own), Angular, or Vue that doesn't also apply to React.
- stopyellingatme 5y agoI’ve been using typescript for years and I’m still constantly learning new things. Certainly has benefits, but also a large conceptual (and often syntax) hump. On the frontend, maybe look at Svelte? I’m not going to try and sway you from your current chosen stack, but my personal experience with it (compared to the others) is that it’s like coming home. More like the natural evolution of early web tech, imo.