wldlyinaccurate

It brings me genuine joy to use websites like HN or Rock Auto that haven't been React-ified. The lack of frustration I feel when using fast interfaces is noticeable.

I don't really get why so many websites are slow and bloated these days. There are tools like SpeedCurve which have been around for years yet hardly anyone I know uses them.

I think the parent comment means "commits" in the sense of the actual changeset; not just the message.

I deployed my first non-trivial Deno app to production in 2023. There were some teething issues with learning to keep the lock file in sync, especially in a repo with multiple entry points each with separate lock files. Some of the granular permissions stuff didn't work how I expected, to the point where I almost gave up and just allowed network to/from all hosts. But overall the experience was good, and I have positive feelings towards Deno. I look forward to seeing where they take it.

Can you clarify what you mean by "version control of branches"? Branches in Git are just labels of objects. Are you talking about having a history of which objects a branch has previously labelled, like the reflog?

The web is getting faster, yes. This manifests as a constant (albeit slow) downward trend in global aggregate metrics. We think this trend is mostly due to Google pushing performance metrics being linked to search rankings.

However the data presented in this post shows obvious step changes in performance that correlate with browser version rollout. It would be disingenuous not to attribute this to a concerted effort on performance improvements from the Firefox team.

Weird that in the process of "restoring free speech", Musk permabanned dozens of journalists who had ever been critical of his companies.

All vehicles in NZ pay road user charges; EVs have just been exempt to encourage uptake. There are RUC weight classes but they only exist to separate light (<3500kg) and heavy (>=3500kg) vehicles rather than distinguish between a Nissan Leaf (1600kg) and a Ford Ranger (2100kg).

Hopefully you realise how lucky you are, and that your situation is the exception in the USA rather than the standard.

I've had the opposite experience with Macbooks. WiFi randomly dropping out, battery dying overnight while the laptop is closed, external display settings not being persisted, randomly switching from my external microphone to the built-in one halfway through a call... Sometimes reading through these threads I feel like the only person in the world who has somehow had three faulty Macbooks in a row.

I've now had three generations of XPS 13 with Ubuntu. They're not perfect (the battery drains over 3 or 4 days instead of overnight) but overall my experience has been much better.

Google's interview process lends itself to finding people who really want to work at Google. Nobody would go through that process to work for a small unknown company, even for the same total compensation.

> If I was gonna bet, my money would be on the lockdowns not doing anything. The virus did what it did no matter how hard humans tried to control it

Tell that to New Zealand, who have had less than 3,000 cases in a population of 5 million. They did this with strict border controls (people on inbound flights must isolate for 2 weeks) and quick response to community transmission (several lockdowns totalling 40 days).

Whoa, I had no idea they'd fixed the inlining-by-size - thanks for pointing that out!

I can't tell if this is satire or not, but I'm assuming it's genuine.

Compression is not a replacement for minification. The client still needs to parse and run the uncompressed source code. Minification provides measurable performance gains for clients by reducing parse times and p̴o̴t̴e̴n̴t̴i̴a̴l̴l̴y̴ ̴e̴v̴e̴n̴ ̴a̴l̴l̴o̴w̴i̴n̴g̴ ̴f̴u̴n̴c̴t̴i̴o̴n̴s̴ ̴t̴o̴ ̴b̴e̴c̴o̴m̴e̴ ̴s̴m̴a̴l̴l̴ ̴e̴n̴o̴u̴g̴h̴ ̴t̴h̴a̴t̴ ̴t̴h̴e̴y̴ ̴c̴a̴n̴ ̴b̴e̴ ̴i̴n̴l̴i̴n̴e̴d̴ (the inclining part is not true anymore; see child comment).

Licence retention isn't a reason to skip minification either. Practically every modern minified retains licence comments.

And finally, your users can still read the original source code if you ship source maps.

Care about your users, please minify your JavaScript :)

Git commit hashes _are_ deterministic. Run `git cat-file -p <hash>` on your two hashes. The timestamp in the committer field will be different. That is why the hash changed.