30 ms·
What the author discovered is really shitty defaults for Angular. Most software is like that. Don't blame the developers using the software, blame the Angular d
by joesmo 10y ago
What the author discovered is really shitty defaults for Angular. Most software is like that. Don't blame the developers using the software, blame the Angular developers for choosing shitty defaults. Instead of choosing production ready defaults, they chose development ready defaults, creating more work for everyone.
- yoran 10y agoMy experience is that Ember.js does a good job in that area. Through ember-cli they provide sane defaults when deploying for production vs a local development environment.
- recursive 10y agoI think it would create much more work to optimize the defaults for production than development. I'd guess fewer than 1% of all debugged angular apps ever go into "production", and even fewer in situation where the performance gained by this would be meaningful.
- enraged_camel 10y ago>>Don't blame the developers using the software, blame the Angular developers for choosing shitty defaults. I like to blame developers who don't read the friggin documentation on the software they are using. This particular suggestion is literally the very first one in the developer guide for running Angular in production: https://docs.angularjs.org/guide/production https://docs.angularjs.org/guide/production
- joesmo 10y agoOh please. There are thousands of Angular guides out there. Some people don't use the official documentation, especially when it's as shitty as Angular's is.