3 ms·
In all seriousness, is it really worth the effort and added complexity, when HTML is going to be compressed on the wire? What are you going to save, maybe a few
by GordonS 8y ago
In all seriousness, is it really worth the effort and added complexity, when HTML is going to be compressed on the wire? What are you going to save, maybe a few bytes?
- bobblywobbles 8y agoThe savings is marginal, but if you are able to set it up once and forget it, why not take advantage of a few % reduction in page size?
- fiddlerwoaroof 8y agoWell, for one thing, minification makes debugging production issues needlessly difficult.
- bobblywobbles 8y agoThat might be the case for javascript or css, however even if the HTML is sent down minified, the browser will not show this minified HTML if you and Inspect it. Was there a specific case you were referring to?
- GordonS 8y agoBecause it adds complexity to the build process, for very little benefit. And I don't like complexity. To illustrate the point, let's take the current Hacker News front page: +=================+========+ | Description | Bytes | +=================+========+ | Original | 43,595 | +-----------------+--------+ | Minified | 41,368 | +-----------------+--------+ | Original (GZIP) | 7,350 | +-----------------+--------+ | Minified (GZIP) | 7,247 | +-----------------+--------+ You've saved 103 bytes, or ~1.4%.
- bobblywobbles 8y agoThat's true, but if you need that extra benefit then it's worth the cost. As long as the process is invisible for you once you set it up, would you justify the complexity for extra gain?
- GordonS 8y agoPersonally, not for such a tiny saving - and it's only invisible until it stops working "because NPM", and needs tinkering with to get working.
- eksemplar 8y agoI'm not sure anyone who truly cares about effort uses .net core. :p I mean, it's a cheap shot, but it's frankly so unproductive compared to Django it's basically a running joke. Not that .net core doesn't see a lot of usage, much like angular it's very popular in the european public sector, but it's just such a waste of resources. By resources I mean, man hours by the way, because it's really effective technically, it's just that, all that you can pay for around a million years of AWS/Azure time for the extra wage-hours you need to pay programmers when you use .net instead of something useful. And in two years it'll be obsolete anyway, because by then Microsoft will have completely changed their direction, again. I say this, as as someone who's running Azure and 365 as our cloud provider for the majority of our services, as someone who's genuinely happy with the services Microsoft provides and having had a great 25 year long business relationship with them, but as far as development goes, .net is just too crazy to be worth it these years.
- elboru 8y ago> And in two years it'll be obsolete anyway, because by then Microsoft will have completely changed their direction, again. You could say the same about the whole industry, also I don't think "obsolete" is a good term, maybe some technologies are not the "new shining thing" out there, but well written systems with "old" and "uncool" technologies are still working perfectly fine and they will keep working fine in the future.
- zamalek 8y ago> frankly so unproductive compared to Django Django is at a completely different abstraction layer.
- GordonS 8y agoI actually love working with .NET Core, and I'm really productive with C#. For some background, I'm pretty much a polyglot; while C# is where I spend most of my time, I also regularly work with JavaScript and Typescript, and occasionally with Java, PHP and C. I also find it preposterous that .NET Core will be obsolete in 2 years, and I'm not sure what you mean about Microsoft changing direction "again" - the .NET Framework was released almost 2 decades ago, and I find the recent move to a cross-platform runtime to make for exciting times!