3 ms·
HTML templating belongs on the server-end? Well, that's... debatable. I like Angular. It is backed by Google so it's less likely to be abandoned because of bor
by IgorPartola 12y ago
HTML templating belongs on the server-end? Well, that's... debatable.
I like Angular. It is backed by Google so it's less likely to be abandoned because of boredom. It ibolides the batteries; I don't have to learn about dozens of independent libraries just to get something simple together. It is fast enough. Lastly, Ionic is pretty neat.
That is not to say it doesn't have it's bad parts. I don't care for some of the boilerplate it has and how badly it fails if you screw any of it up. I am not a fan of the built in $http service. The state service and URL routing are also too confusing and often do not work correctly when doing slightly more advanced things (intercepting transitions, rewriting history). But overall, I like it better than, say, Backbone.
- beobab 12y agoI'm not familiar with the word "ibolides", and a google search didn't turn up anything I could fit as something you could do to batteries. Could I convince you to explain what it means?
- dnissley 12y agoI'm guessing they meant "includes".
- IgorPartola 12y agoYes, indeed. Typing on a mobile device is a pain, sorry.
- jffry 12y agoI'm curious - what don't you like about $http?
- IgorPartola 12y agoLack of PATCH method out of the box. No easy way to provide error reporting to the user for some but not all requests. For example, when a user submits a form and it fails, show them a dialog, but when the app makes a background request to refresh some data, and it fails, don't bother the user about it. It's not a huge problem, I just end up creating my own wrapper around it that provides all the necessary methods, but it could be built in.