3 ms·
The word 'huge' looks suspicious to me. Also, if it is progressive why couldn't you still AOT the client side? You could be completely right, but your comment
by mattmanser 10y ago
The word 'huge' looks suspicious to me.
Also, if it is progressive why couldn't you still AOT the client side?
You could be completely right, but your comment smells dodgy.
Note that as it's typescript it will be transformed to JavaScript anyway, all the comments stripped, etc. so very much doubt it will be huge. And minification is becoming ever more irrelevant in the modern age because of http2.
- hazza1 10y agoHuge in the context is a few hundred kb, not great for a simple webpage. https://blog.nrwl.io/angular-is-aot-worth-it-8fa02eaf64d4 https://blog.nrwl.io/angular-is-aot-worth-it-8fa02eaf64d4 You could and should AOT the client side, my point was this quickstart project doesn't. Typescript isn't the problem here Angular is, without AOT it includes an in browser compiler. Minification doesn't change with http2, you are probably thinking of concatenation/bundling.
- aussieguy1234 10y agoOne thing to remember is that it is a quick start rather than a full production setup, so minification/uglification etc could be added as desired by whoever clones the repo as a base for their own up.
- aussieguy1234 10y agoHttp2 is what I was thinking. Progressive web apps are cutting edge, browsers that support them will also support Http2. It will load a large number of assets over a single connection, more efficiently than using concatenation. It dones struggle on bad network connections more than Http 1.1, but the service worker should account for that.