This, I think, is a common problem with library writing in general, and doubly so for Javascript. Ember tries, but it's still remarkably easy to get a cryptic error from it.
The ergonomics for using libraries needs to improve a great deal. I have my fingers crossed that this will be something most people have on their radar soon, but I'm not holding my breath.
"Silently fail with no warnings" is like the angular
motto... At least in Angular 1 if something failed
usually angular would just show an empty string on
the screen.
But basically it still is a awful framework, still working on the replacement.
Re:Angular 2 is terrible
by FrancoDiaz on Thursday December 01, 2016 @07:39PM
(#13085002)
Silent failures was why I left Aurelia too. It's probably the best of breed of those types of MVM frameworks, but it suffers the same problem.
Just let me use JavaScript.
Re:Angular 2 is terrible
by resonantjacket5 on Thursday December 01, 2016 @08:00PM
(#13085114)
Theyve made it better recently where if it crashes it shows the error
Debugging is just a cold dark hell where very very few resources can help you find what went wrong, you basically just need to litter everything with console logs (Except the template html syntax, which you can't just write JS log statements in since... it's not javascript, its it's own language.
I've become much more productive and comfortable in all the JS vdom frameworks which have no template language, just javascript.