Hacker News Reader

Comment by ralmidani | Hacker News Reader

Build systems really help reduce the number of scripts (and stylesheets) loaded. I currently use Ember-CLI, and it's just a "vendor" script containing all your third-party scripts and another with your app-specific code.

The old-fashioned way of embedding scripts directly is really wasteful, I agree.

View on HN

I think you vastly underestimate how wasteful 3rd party JS API implementations work. Especially for advertising, analytics, and other injected widgets.

Build systems exist, but that doesn't mean they are used everywhere or that all features can be integrated into them. The same goes for static analysis tools, dynamic analysis tools, perf optimization tools, security vulnerability testing tools, unit testing, automated integration testing, etc. -- they exist, but their coverage is far less than 100%.

I understand build systems cannot solve every problem, and the mechanism described in the article is certainly useful. I was merely responding to the concern about third-party scripts with links copied-and-pasted mindlessly, and which would be better handled using a build system.

Sure, but adding GA to a page is what I meant by copy/paste, this still happens everywhere outside of the build process. Then of course marketing needs to add 10 other things and they can't figure out whatever hip new build tool someone set up and then suddenly things get really messy.

Yes this happened even at whatever company you think is a paragon of engineering best practices and modern development.

You need to spend some time browsing the web with your debugger opened to the "net" tab. It is, alas, not the "old" way.

Edited to say "old-fashioned" rather than "old".

HTTP2 greatly reduces the cost of requests though so what you really want is tree shaking to get rid of code you don't use and minification to reduce its size.

Reply on news.ycombinator.com