Timeline for Is obtrusive JavaScript required to support a feature of AngularJS?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2019 at 14:58 | comment | added | Zachary Scott | How do you do unobtrusive Angular? We are ready to roll out Angular and found a serious design flaw. We have a 50 person HTML design team and a two person development team. Designers change HTML without adding non-html. Two developers cannot keep up with 50 designers if we had to adjust every template created every day even after websites are posted. It also seems silly to compile whole html templates into JavaScript code like Webpack when you could automate that function on the server to gather, compress, and cache html by page scope in a zip file with the same client download efficiency. | |
| Aug 1, 2015 at 4:17 | comment | added | Aaron Greenwald | @bryanbraun you are correct. Point taken. | |
| Jul 31, 2015 at 2:39 | comment | added | bryanbraun | Good explanation, but I'm wary of your statement "not doing Progressive Enhancement." Progressive enhancement is way more than falling back to noJS. It's providing retina images and SVGs with fallbacks for those without retina devices. It's adding subtle animations to browsers that support them. It's reducing streaming video quality on low bandwidth devices (like youtube does). It's responsive design. You may not need noJS fallbacks for your web application, but don't abandon progressive enhancement. | |
| May 7, 2015 at 22:12 | vote | accept | Kevin | ||
| May 6, 2015 at 20:46 | history | answered | Aaron Greenwald | CC BY-SA 3.0 |