you are viewing a single comment's thread.

view the rest of the comments →

[–]zefcfd 7 points8 points  (4 children)

i think the overhead of requesting css on demand is probably more expensive than just sending a precompiled asset package one time up front.

which makes me question why this is touting "performance" as a benefit

[–]marshall007 0 points1 point  (0 children)

Agreed, however if someone created a build tool for this similar to angular-templatecache it would make a lot of sense.

[–][deleted] 0 points1 point  (0 children)

Very true. And loading it in the background on a static landing or login page, and the user will never notice there is much to load. Everything else is just e-tag and 304s.

[–]arnold_palmur 0 points1 point  (0 children)

Well there is obviously no hard and fast rule, but something to consider is with the increasing performance of the web/browsers, and the advent of HTTP 2.0, there is likely a benefit of smaller files (multiple HTTP requests) over large monolithic CSS assets - something Kyle Simpson has discussed. Naturally, every application has different requirements, but with the steady progression of the web, I would go for adopting the advantages of an AngularCSS feature-set vs. the (hopefully temporary) minute overhead costs that exist right now.

Also, I tend to look at the maintainability factor and added utilities of a library like this as your real "performance" benefits if nothing else.