4 ms·
The author is completely wrong. I think he had misunderstanded the main objective behind using a framework like angular. Angular is not build for developing a
by jordic 10y ago
The author is completely wrong.
I think he had misunderstanded the main objective behind using a framework like angular.
Angular is not build for developing a feature for an exisitng webpage. It's developed for building complex and large web applications, in a safe an eficient way.
I'm talking from my experience: We have developed a k3-k6 elearning/game platform in two months. Actually, it has 5 game types, a game creator/editor, user profiles, game boards.. it has around 20 to 30 routes (mostly dinamic) serving stored games and boards. Around 50 to 60 components (with some of them using pixi.js as a canvas render engine)
And despite of the growing feature list, we are still super confortable with the codebase. (We are just on the second iteration, starting the three).. You know something is good, when you are able to throw away parts of it and rewrite them without much drama....
The main application build, when gziped is around 380K ( Think that only firebase + pixi.js are around 150). But also we know that we will be able to split features (modules) for lazy loading them.. (and also our build will be smaller... because soon will be able to treeshake it)
PD: If your main use case is build a slider for a wordpress theme, angular doesn't fit, but instead, if you think on building (a desktop grade) application for the browser, even for the mobile browser you will find angular your best alliated.
- Udik 10y agoI'm not sure how this proves the author wrong though. The fact that Angular2 can actually be useful in a very specific use case doesn't mean it's not poorly designed, horribly documented, cryptic and inconsistent (just to summarize briefly what I think the post says).
- jordic 10y agoSorry I will not argue on all of the exposed things by the author.. for example (decorators) is something that is also used on react libs. The point to modules is completely wrong.. modules exist to allow lazy bundle (load) parts of your app. Btw, I suspect the problem is mainly on the user level.. (anyone says that angular is targeted for novice users) at least to start architect the app..
- piaste 10y ago> I'm talking from my experience: We have developed a k3-k6 elearning/game platform in two months. Actually, it has 5 game types, a game creator/editor, user profiles, game boards.. it has around 20 to 30 routes (mostly dinamic) serving stored games and boards. Around 50 to 60 components (with some of them using pixi.js as a canvas render engine) Interesting. I'd like to know, what is the size of your production team? And how experienced are they?
- jordic 10y ago1 full time main developer.. two more working partially (5 hours/week) 45h / weeek No prior experience with angular2. But we are long experienced front-end devs...