I feel like this is a pointless thing to note and a bad faith argument. If you just compare "@angular/core" to "react" the stuff inside them is pretty comparable. So what does React make easier? Templating. You have to learn JavaScript with sugar, rather than a custom templating language. Modules. With React you have to learn ES6 import statements and you're done, but with Angular your have to learn that plus the convoluted and messy NgModule system. And not to mention Reacts patterns don't force you to learn DI out of the gate. I'm not going to say DI is bad, but I'm going to say the concept is weird for beginners and that above all, in a client, it's very rarely got a purpose. 99% of folks Angular service @Injectables are just one instance.
Personally I liked the nudge to learn typescript. I've been using it since it's was in Angular RC candidates so at the time the browsers didn't even support const and let or the class keyword so in those times it was letting you use next gen js features w/o babel.
That has become much less of a point nowadays though.
I'm general I feel like it promotes learning of good software architecture patterns rather than proprietary syntax.
Kind of feels like you're suggesting it's a bad thing for developers to learn how the concept of dependency injection works, or how strong programing patterns help.
I don't see it as a drawback to basically teach developers SOLID design principles as they learn a framework at the same time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I feel like this is a pointless thing to note and a bad faith argument. If you just compare "@angular/core" to "react" the stuff inside them is pretty comparable. So what does React make easier? Templating. You have to learn JavaScript with sugar, rather than a custom templating language. Modules. With React you have to learn ES6 import statements and you're done, but with Angular your have to learn that plus the convoluted and messy NgModule system. And not to mention Reacts patterns don't force you to learn DI out of the gate. I'm not going to say DI is bad, but I'm going to say the concept is weird for beginners and that above all, in a client, it's very rarely got a purpose. 99% of folks Angular service @Injectables are just one instance.
Good point.
Personally I liked the nudge to learn typescript. I've been using it since it's was in Angular RC candidates so at the time the browsers didn't even support const and let or the class keyword so in those times it was letting you use next gen js features w/o babel.
That has become much less of a point nowadays though.
I'm general I feel like it promotes learning of good software architecture patterns rather than proprietary syntax.
Kind of feels like you're suggesting it's a bad thing for developers to learn how the concept of dependency injection works, or how strong programing patterns help.
I don't see it as a drawback to basically teach developers SOLID design principles as they learn a framework at the same time.