2 ms·
As a developer who didn't care for Angular 1.x and strongly argued in favor of a simple approach for years (Backbone, etc). I've been using Angular 2 in a majo
by georgefrick 10y ago
As a developer who didn't care for Angular 1.x and strongly argued in favor of a simple approach for years (Backbone, etc).
I've been using Angular 2 in a major enterprise project since RC1. Even with some of the headaches between RC releases; all of the reasoning behind those changes is technically sound.
It's easy to write components and wire everything, and even small things like async validators are fluid and easy to implement.
I'm loving it, and while the entire build system is still a bit of a dumpster fire; we're doing great on things like testing, code coverage; etc.
There are a lot of problems with lazy developers hoping a blog will tell them how to do every little thing. The source code is on Github. If you can't get something working right; maybe go read the source code of the classes you are interacting with. I've found 99% of the time now that simply reading through the code gives me not only the transparency needed, but a clear path to a better solution. Kudos to them on the new forms; they're awesome.
- Bahamut 10y agoOne thing that is hugely helpful that many developers don't do is read the tests for the library they use - in particular with Angular, reading the tests in the Angular codebase actually assist greatly in how to use a feature.