Narishma

I don't know. Mine only has "Normal" and "Touch".

The closest modern thing to it is probably the Raspberry Pi GPIO header.

There is no compact mode anymore, they removed it years ago.

But are mostly forgotten while emacs keybindings are still popular and found in all kinds of places you wouldn't expect, like MacOS textboxes.

And those who still use 32-bit machines, as Linux is in the process of killing support for them.

All modern browsers are the same in this regard.

> but because they are trying to maximize screen space

If that was the case they wouldn't put giant margins around every UI element and dead space everywhere.

What other OSS rebuilds?

You missed the biggest reason the newer consoles couldn't reach PS2 numbers: Sony managed to bring its price all the way down to $99. PS3 and PS4 only went down to $299. PS5 instead has had multiple price increases and is now way more expensive than it was at launch.

Why are so many comments talking about Sony? The case was brought by beIN Sports.

beIN, not Sony.

At that point you may as well go for a RISC-V or ARM microcontroller.

> Software rendered games never supported texture filtering

Unreal did. Or maybe Unreal 2, I don't remember which.

Unless you were playing on a TV CRT, I don't think so. PC monitors of the time were pretty sharp already.

That's a workaround, not a solution. And a partial one at that since it only affects your own vehicle; you'll still be in danger from other people's connected vehicles.

> also I don't see why target WebGL 1.0 in the days of WebGPU, WebGL 2.0 yes, because WebGPU isn't yet widely available.

Because not every hardware capable of running PS2 level games supports the newer APIs.

> Also OpenGL 3.3 is from 2010, whereas OpenGL 2.1 was designed for 2006 hardware, how back you want to get?

Doesn't matter how old it is, what matters is if it has the required features or not. For the use case being discussed, GL 2.1 is sufficient so there's no good reason to not target it. That's my philosophy at least. When I write code, I always use the oldest library or API that has the stuff I need. I don't just go automatically for the latest one.

It's not an "and". GL 2.1 has all the features necessary for PS2 games and is still supported on modern systems. Older APIs may be slightly more verbose than newer APIs but that shouldn't matter to an AI.

But we're talking about AI generated code here, it shouldn't have any difficulty supporting the older API if it has the necessary features. For PS2 games I think GL 2.1 (or GL ES 2.0 or WebGL 1 which are all more or less the same thing) is largely sufficient.

What do you mean by token costs? Does it cost more to support an older graphics API than a newer one?

GL 2.1 supports shaders.

Ah yes, you're right. The base PS5 seems to still be available for now.

More of a hello world than a kernel.

It's sold out basically everywhere.

These kinds of browser recreations of old native apps always fails at text rendering.

You can use a web browser.

Because they don't make money from the hardware. If you don't buy games for it, there's no point in selling you a console, from their perspective.

I don't think Sony is interested in customers like you.

> Someone at Nintendo had the genius idea of charging you a subscription fee for internet access.

Microsoft had that 'genius' idea with the original Xbox. The others saw that people will indeed pay for such a thing and copied the idea with the PS4 and Switch.

For me it's less the verbose syntax but more the weirdness and inconsistency of it. Like making a distinction between a procedure and a function, or returning data from a function by assigning it to a magical variable. It feels like a cobbled-together language rather than a properly designed one.

Microsoft and Google are the same.