kllrnohj

I have seen a significant number of excellent engineers just seemingly turn their brain off entirely and resort to just spitting out "but AI said <blah>" or "AI reported <foo> which I found surprising but I didn't analyze or dig into that result whatsoever". So anecdotally, yes, this absolutely matches my experience.

As a percentage of websites, though, Java is far from ubiquitous. It's probably not even double digit percentages. PHP, meanwhile, is some 70% of websites. So in terms of exploit targets, this is 10x that of Log4J, maybe.

> While Go/Node have grown much more than PHP, PHP is definitely alive.

PHP still powers approximately 70% of websites

> xhtml was just a bad idea creating tons of problems and solving none.

Well an XHTML parser (and serializer) is a lot simpler, which is a pretty meaningful problem to solve.

What problems does xhtml create?

The thrusters are primarily pointed rearward and to the ground. It's not capable of doing much at all for a flat spin, the typical scenario of a car spinning out

I don't have a MacOS comparison point, but steam for me is pretty equivalent to the numbers in the article. ~10 seconds for a cold start, half a second for a warm start. Unless you have a very different definition of "take forever"? What are you seeing on MacOS?

> The Steam client is terrible

Things nobody has said since like 2005? A faster startup is certainly appreciated, but steam's 10 second cold launch time is hardly a big deal. Especially when everyone just leaves it running anyway. There's far more significant aspects like memory usage, game library, and general features.

> as long as password-based login remains as an option.

which they have to be, right? since passkeys are "temporary" in that they are easily lost/destroyed/temporarily unavailable, and sites are supposed to support multiple of them?

I don't see anything in those criticisms that are remotely unique to C++.

Linux also built up inefficient abstractions in C that are used simply because they are easy to use. Linked lists being a go-to default choice being an obvious example.

> Fair, but I just wasn't willing to put up with Android TV.

When I bought my Shield TV's I actually liked Android TV. Very nearly every update since then has just slowly made it worse and worse.

Now it's absolutely disgusting as it shows straight up advertisements (not "recommended shows", like literally ads for car insurance or whatever).

So I guess there's really just not much to choose between regardless. It's spyware + adware regardless of price vs. Apple's lack of local backup support :/

The appeal of the Shield Pro is you don't have to deal with custom flashing a "no-name" device and you don't have to dual box to keep streaming services happy.

It's frustrating that nobody else seems to care about attempting to be the all-in-one box given how much Shield is showing its age now. It's really sluggish

I don't get why Apple just refuses to allow audio pass through or DV Profile 7. They're clearly on board with DV in general and don't hesitate to play Dolby's branding games, so why not profile 7 support???

You have that backwards. HEIF is the container format. HEIC is a HEIF file using HEVC.

HEIF is a container not a codec. HEIC is HEIF + HEVC.

AVIF and HEIC both use HEIF

RIFF itself is fine, but in the context of webp it's pointless. WebP doesn't make any use of being in a riff container. Like it still internally has its own chunk system anyway. So you end up with a single RIFF chunk for the webp file that itself then can contain multiple, non-RIFF chunks

well that depends on the size of the image. But a modern cell phone is shooting 50mp+, and at that size you're talking 50-200ms for a jpeg vs. a couple seconds for HEIC. Which is borderline instant-feeling vs. extremely not instant.