On my past iPhones, the compass always got screwed up over time somehow. Sometimes recalibrating fixed it, but only for a minute.

Yep - exactly what I’ve experienced. Calibrate the compass and at least it’s within a right angle of being correct. But the problem returns.

Was it serviced? In some models they used to have a non-ferrous screw put next to the compass, if a tech puts the wrong one in it will not calibrate.

I've always wondered how the resolution mechanism can be trusted. Won't someone with enough money rig that? It's not like PoW or PoS where a cheater with huge resources would ruin their own stolen money.

“Priced in”.

Probably upset that the high-end video game "hobby" costs more than it used to. Used to be $1-2K for the very best gaming GPU of the time.

I mean, yes. Very much so. People should be upset about a relatively affordable hobby getting to this point.

It's also gotten cheaper nominally. I just got a new base MBA for $750. Kinda surprised, like there has to be some catch.

I feel bad for their competitors. We need good competition in the long run but over the last few years it's made less and less sense to get something other than an Apple laptop for most use cases.

I don't. They're being weighed down by Windows and to a lesser extent, x86. If they want to excel in the market, make a change. Use what Valve is doing as an example.

Also, the MBA vs MBP lineup is different now. MBP was the default choice before even for students, so MacBooks sorta started at $1300. Now the MBA is decent, and the MBP is really only for pros who need extra power and features.

json columns pretty much obviated the need for ORMs. It used to be that you'd sometimes have a deep nested thing you really only ever query all at once rather than in pieces, so you'd use an ORM to automate that, but now you can just shove it into json. And then use regular SQL for the relations you actually care about.

Doesn't sound very cursed, standard normalized relations for things that need it and jsonb for the big bags of attributes you don't care to split apart

You only need gin if you want to index the entire jsonb. For a specific attribute, you can use the default (btree) which I'm guessing is faster.

Yes, as far as indices go, GIN indices are very expensive especially on modification. They're worthwhile in cases where you want to do arbitrary querying on JSON data, but you definitely don't want to overuse them.

If you can get away with a regular index on either a generated column or an expression, then you absolutely should.

HN has some built-in ways to reduce this, like not allowing everyone to downvote everything.

You can't change it for other users, only for yourself, which is what the original comment about the extension said.

Not totally enforceable, but there are not a whole lot of people with connections in other countries willing to host VPNs for them. Most people don't even know what a VPN really is.