4 ms·

For my "fun" projects I never minify the CSS or JS because I miss the days when you could View Source on a website and easily dig into how it works. If you're a

by grose 3y ago

For my "fun" projects I never minify the CSS or JS because I miss the days when you could View Source on a website and easily dig into how it works. If you're a NoScript user, go ahead and read the source and decide for yourself if you want to allow it. Much easier to maintain without all the moving parts of the JS build ecosystem as well.

mbork_pl 3y ago
I'll be starting a completely serious side project in a few days where I'm going to not minify anything (especially JS) so that user will be able to hit C-u and check for themselves nothing nefarious is going on privacy-wise. Also, no cookies at all, and the whole site will be just a bunch of static html files, two fonts, one css file, one small vanilla JS file and some images where appropriate. I hope to get load times well below one second (especially once the assets are cached).
catlifeonmars 3y ago
FWIW if you ship source maps, then you can have the best of both worlds.
- kevingadd 3y ago
  Do those work in View Source? Don't you have to load the site and inspect it in a debugger for source maps to kick in, which doesn't happen in the noscript scenario?
  - zamadatix 3y ago
    I don't think view source will load source maps but you can still open the f12 debugger and load source maps (even automatically) with noscript enabled. The debugger isn't treated as a normal webpage, rather part of the browser itself.
    - WorldMaker 3y ago
      It's mostly just kind of funny that "View Source" diverged so much from the F12 debugger. For most of its history Spartan Edge had caught and fixed that mistake and View Source just dropped you into the F12 debugger. It's almost sad that Chromium Edge again shows you a different unrelated view. Firefox has also seemed to wander back and forth between View Source just reuses the full Dev Tools and View Source is a disconnected view from Dev Tools for whatever reason. At the moment the big difference flag seems to be if you install/use Firefox Developer or not. (Allegedly, one of the reasons is that some non-technical users have strange reasons that they View Source from time to time and they get upset if it opens Dev Tools because Dev Tools is just too confusing. Mac Safari has that interesting dance to ask it to opt in to showing Dev Tools. I seem to recall IE11 did something similar that if you ever opened Dev Tools for more than a few minutes it then took over for View Source, but otherwise used the older and simpler View Source from ancient IE history. I'm surprised that if the reason is "it confuses non-technical reasons" there isn't an opt-in flag in Chrome or Chromium Edge. The "Firefox Developer Edition" is a separate SKU is also an interesting way to approach that.)
- quic5 3y ago
  But there aren’t any guarantees that the file the source map points to is actually the source, right?

by grose 3y ago

mbork_pl 3y ago

I'll be starting a completely serious side project in a few days where I'm going to not minify anything (especially JS) so that user will be able to hit C-u and check for themselves nothing nefarious is going on privacy-wise. Also, no cookies at all, and the whole site will be just a bunch of static html files, two fonts, one css file, one small vanilla JS file and some images where appropriate. I hope to get load times well below one second (especially once the assets are cached).

catlifeonmars 3y ago

FWIW if you ship source maps, then you can have the best of both worlds.

kevingadd 3y ago
Do those work in View Source? Don't you have to load the site and inspect it in a debugger for source maps to kick in, which doesn't happen in the noscript scenario?
- zamadatix 3y ago
  I don't think view source will load source maps but you can still open the f12 debugger and load source maps (even automatically) with noscript enabled. The debugger isn't treated as a normal webpage, rather part of the browser itself.
  - WorldMaker 3y ago
    It's mostly just kind of funny that "View Source" diverged so much from the F12 debugger. For most of its history Spartan Edge had caught and fixed that mistake and View Source just dropped you into the F12 debugger. It's almost sad that Chromium Edge again shows you a different unrelated view. Firefox has also seemed to wander back and forth between View Source just reuses the full Dev Tools and View Source is a disconnected view from Dev Tools for whatever reason. At the moment the big difference flag seems to be if you install/use Firefox Developer or not. (Allegedly, one of the reasons is that some non-technical users have strange reasons that they View Source from time to time and they get upset if it opens Dev Tools because Dev Tools is just too confusing. Mac Safari has that interesting dance to ask it to opt in to showing Dev Tools. I seem to recall IE11 did something similar that if you ever opened Dev Tools for more than a few minutes it then took over for View Source, but otherwise used the older and simpler View Source from ancient IE history. I'm surprised that if the reason is "it confuses non-technical reasons" there isn't an opt-in flag in Chrome or Chromium Edge. The "Firefox Developer Edition" is a separate SKU is also an interesting way to approach that.)
quic5 3y ago
But there aren’t any guarantees that the file the source map points to is actually the source, right?