There's colloquialisms for a half: pot, or middy, mostly. Hobart will call a half pint a ten, because it's 10oz, but they also know what you're talking about when you ask for a pot or a half pint.

Then there's South Australia, which will serve you a pint at 425ml, a schooner at 285ml, no one there outside of specialty craft beer bars have any idea what a half pint is, and if you want a proper pint you need to ask for an imperial pint. I have never seen an 'imperial pint' advertised in Hobart - it's just called a pint there.

Source: I have pretty extensive drinking experience in pretty much all of the Australian capital cities, except Perth.

You have probably fallen asleep on something patterned or folded and have it leave an impression on your skin before: This is no different.

Other places it happens: Watches that are slightly too tight or have ridden up an arm. Glasses arms pressing against your temple or behind the ear. Tight socks after a day wearing them.

It's not a medical problem. It's just general physics.

That, of course, is one of the pain points that the article addresses: Training yourself to do so is additional cognitive load that never should have been necessary in the first place.

I flip between macOS and Linux and, occasionally, Windows. On one of my laptops, insert is also a Fn switch away, so I have to either remember that this machine needs Ctrl-Fn-F11 specifically when I'm copying from terminal.

On another keyboard I have the same problem, but insert is mapped to a different key entirely, so it is ctrl-fn-equals, and fn is on the opposite side of the keyboard from ctrl.

Contort my fingers in which way on which keyboard? Mental load and annoyance I don't need.

* Caddy's complexity (especially when it comes to TLS) is not arbitrary, it's to meet the needs of auto-renewal and ... y'know, hosting sites on TLS.

* Caddy's SDLC is not, as far as I understand it, especially rapid.

* Implying that "military grade" is some level of encryption beyond the minimum level of encryption you would ever want to use is silly.

* The Manjaro website is not "the equivalent of a poster", and in fact hosts operating system downloads. Operating system integrity is kinda important.

You may have reasonable arguments for sites that are display only, do not out-link, and do not provide downloads, but this is not one of those circumstances.

The temperature inside is not at all indicative of the temperature outside, the sun being out doesn't mean it is warm, and I don't really have any useful indicators of wind, unless the windows are rattling, but that doesn't let me know if there's a stiff breeze.

I could walk over and open up my balcony door and experience it all personally, but checking my phone or watch is faster and more accurate, and also gives me the forecast at the same time.

FTA.

The problem here is requiring hardware-attested DRM: Widevine L1 on Edge on Windows, and Apple FairPlay on Safari on MacOS. The only way to get hardware attested DRM is via browser specific (i.e.: native code) support that interfaces with the OS & GPU drivers. You can't get there through an extension.

It appears to only be useful on Edge on Windows.

I understand it spoofs all of the checks it can, but the only Chromium browser that supports Widevine L1 (a requirement for 4K) is Edge, so even if all of the check spoofing works, it still won't do 4K.

There's even a table in the README that describes this exact scenario.

It doesn't work on Firefox. It appears not to work on Chrome. The suggestion is to use Edge, which on Windows already gets 4K support in Netflix anyway.

To go further into detail about the whole thing: "You're holding it wrong" is perfectly valid criticism in many, many different ways and fields. It's a strong criticism in some, and weak in others, but almost always the advice is still useful.

Anyone complaining about getting hurt by holding a knife by the blade, for example, is the strongest example of the advice being perfect. The tool is working as designed, cutting the thing with pressure on the blade, which happens to be their hand.

Left-handers using right-handed scissors provides a reasonable example: I know a bunch of left-handers who can cut properly with right-handed scissors and not with left-handed scissors. Me included, if I don't consciously adjust my behaviour. Why? Because they have been trained to hold scissors wrong (by positioning the hand to create opposite push/pull forces to natural), so that they can use the poor tool given to them. When you give them left-handed scissors and they try to use the same reversed push/pull, the scissors won't cut well because their blades are being separated. There is no good solution to this, and I sympathise with people stuck on either side of this gap. Still, learn to hold scissors differently.

And, of course, the weakest, and the case where the snark is deserved: if you're holding your iPhone 4 with the pad of your palm bridging the antenna, holding it differently still resolves your immediate problem. The phone should have been designed such that it didn't have this problem, but it does, and that sucks, and Apple is at fault here. (Although I personally think it was blown out of proportion, which is neither here nor there.)

In the case of LLMs, the language of the prompt is the primary interface -- if you want to learn to use the tool better, you need to learn to prompt it better. You need to learn how to hold it better. Someone who knows how to prompt it well, reading the kind of prompts the author used, is well within their rights to point out that the author is prompting it wrong, and anyone attempting to subvert that entire line of argument with a trite little four-sentence bit of snark in whatever the total opposite of intellectual curiosity is deserves the downvotes they get.

Prices for who? The prices that are being paid by the big movers in the AI space, for hardware, aren't sticker price and never were.

The example you use in your comment, RAM, won't work: It's not 3x the price for OpenAI, since they already bought it all.

Also, what big words? 'Proliferation'? 'Incoherent'? The whole article is written at a high school reading level. There's some embedded clauses in longer sentences, but we're not exactly slogging our way through Proust, here.

They wanted to push a feature, and they said they would if they didn't see any major regressions. Then they did see a major regression, so they pulled the feature.

Exact version numbers, timelines, and builds are pretty irrelevant to that process. Or are you actually saying you would prefer they had just left their product broken for a significant portion of users, just to keep aligned with the version numbers they mentioned in a blog post?

It isn't without its flaws: I wouldn't ever use the pre-installed version of Windows (the one that doesn't allow you to open services.msc or Task Manager), because I totally distrust it. The fact that the panel is natively 50hz portrait on an inherently landscape device is painful. The default hysteresis settings on the trackpad are awful, the RAM speed by default is stuck at 4000MT/s...

But after an hour or two of hacking Arch into an acceptable shape and solving all of those niggles, it does absolutely everything I need in a portable machine, and is small enough to fit in a tiny sling bag along with everything else I carry around on the daily. It "only" gets about 6 hours on battery, but that's the biggest downside. And 6 hours is plenty of time to cook.

With a full-screen terminal and a keyboard that is very acceptable for the 10" form-factor, I can hack on anything I want wherever I want. Niri as a WM is an absolute dream on this thing. I basically don't bother carrying around my personal M4 macbook pro anymore, and it has been relegated to sitting on a desk and never moving from home.

If you think acknowledging that fact (and the fact that there’s really not a great way to make LLMs more efficient) is “apologetics”, I cannot engage with you in good faith.