taylortbb

Fair, it does touch on that issue towards the end. But I think it deserves more than a couple sentences acknowledging (but proposing no solutions to) the issue in the last paragraph, given IMO it's basically the entire issue with their proposal.

> There is no 'wages go up 20%'. That's not how the economy works. Wages are renegotiated on an annual basis and most people have to job hop to get anything close to a 20% raise.

The example was not meant to be a single year. Over the 2020-2024 timeframe we did see movements around that size (though the gap between average wages and inflation was smaller than my example, where I rounded the numbers).

> They should lift incomes, not suppress prices

I think this misses the psychology of inflation.

If wages go up 20%, and prices go up 15%, everyone is better off and got a 5% raise, right?

Go poll people that experienced that and they won't tell you they're celebrating being 5% richer, they'll tell you they're outraged about the 15% inflation.

Psychologically they'll believe they earned that 20% raise through hard work. Putting in extra hours to get that promotion. But then the inflation robbed them of their 20% raise, and turned it into a measly 5% raise. They'll be outraged.

Politicians get this. No one will credit politicians for raising average wages, people will believe they earned their raise themselves. But there's lots of votes available for lowering prices.

The transcoding isn't just about bandwidth, it's about compatibility. I store most media in H.265 because that's the most space efficient, and most things can play it, but a decent number of devices still need H.264. I also have older content with DTS soundtracks, which isn't supported by a bunch of new devices.

Plex/Emby/Jellyfin will handle that compatibility by converting on the fly.

Plus, when using a Fire Stick, or Google TV Streamer, or old Chromecast it just isn't easy/possible to browse a SMB share.

> Honestly, at this point, having natural disasters with destruction and death is probably the only way to make people care

We already have them. People just claim they're chance effects with no connection to climate change.

The problem with refuting it is that they are chance events, there's no way to definitively say "this was caused by climate change", because it's always possible it would have happened anyways. It's the upwards trend in frequency and severity that we can definitively point and say "that's caused by climate change", but that's too abstract for most people to understand.

At least for Waymo, the remote control is not nearly that direct. The human operators suggest a route through a confusing scene, but the self driving remains in control for executing that suggested route, and may reject it.

A remote operator driving directly, via a racing sim setup or an Xbox controller, just isn't safe. Too much latency, lack of visibility, and connection unreliability.

Doesn't MTP require plugging in a USB cable? KDE Connect works wirelessly as long as your phone and computer are on the same network.

But then you risk tariff policy changing, and suddenly you're undercut by foreign factories again, and you lose all your investment in the American factory. It still needs certainty that the tariffs are staying.

The uncertainty only works to return manufacturing where America is cost-competitive without tariffs, and that's a tiny slice of manufacturing.

> I guess I was assuming almost $20k a year back then would have been livable back then, like it was for much of the US excluding a handful of cities like NYC or SF at the time.

You're excluding the reasonable comparables. London is the UK's equivalent of NYC or SF.

They're a pharmacy, they get directly reimbursed by customer's drug insurance plans and only charge customers for the uninsured amount. They need to submit prescriptions to insurance, and find out how much insurance is covering, before filling prescriptions.

> it won't (logistically can't) work when you have literally run out.

While I believe you're correct for the iPhone, that it won't work, it's actually not as impossible as you suggest. The NFC-capable BlackBerrys that supported the very early tap-to-pay with a phone had the concept of a default card, which could be programmed onto the secure element and would work even if the phone was totally dead (even if the battery was removed). The NFC field was enough power to boot up the secure element, just like it's enough power to run the chip in your bank card when you tap it.

Later phones dropped this support, as it took a bunch of engineering effort and customers largely didn't care. But if customers ever start demanding it, so they can totally stop carrying a bank/credit card, it is possible.

> Why are you including only US airlines for comparing a plane model's safety? That seems very convenient

737 MAXs are not identical worldwide. There's a number of optional add-ons, which even discount US airlines will pay for, but emerging market discount airlines will not.

Specifically for the 737 MAX crashes, it was from a faulty AoA sensor. Neither of the crashed planes had the AoA disagree alert option, but all US airlines paid extra for it. It's not something you're supposed to need, hence being an optional extra, but for obvious reasons budgets aren't as tight at North American airlines as discount airlines in emerging markets.

This isn't to say we're guaranteed that an AoA disagree alert would have avoided the problem, it was undeniably a faulty design, but it probably provides an additional layer of safety. There's a reason that when the MAX returned to service it became standard equipment for all MAXs sold.

So, it's not entirely correct to totally exclude planes from other countries. But there is a fair point in putting more weight on similarly configured planes.

> Chrome/Chromium was developed for quite a while using Webkit. Chromium was created in 2008 and only after Google had already captured a third of the browser market share (according to Statista) did they fork it (April 2013).

I think you missed the point, there's two forks in the history of Blink (Chromium). Yes, Blink is a fork of WebKit, but WebKit is a fork of KHTML. So it's not like it originated at Apple either, it originated at KDE.

The point is that they're not really comparable. Mint/Ubuntu/etc all ship the same Linux kernel, that's why they're called distros. They're different distributions (distros) of the same software (Linux kernel, etc).

The different BSDs aren't distros, they are different kernels that are developed in parallel. Obviously there's shared history there, and some shared userspace, but FreeBSD and OpenBSD aren't just two different BSD distros of largely the same software.

The post says the phone was in airplane mode, and was found by chance as someone walked past it.