Nicalis and Take-Two have both gone after decompilation projects, also. In particular, Nicalis has gone after a decompilation of Cave Story, but not a black box reimplementation of the same, while Take-Two ended up suing a decompilation developer (albeit settled out of court). However, in some jurisdictions, even clean reimplementations have failed - see Tetris v. Xio.

(I am not a lawyer either, etc etc, but that's my understanding)

The comment about "burning bridges" is not a statement of intent, but of observation: if I publicly call someone out on the Internet, and we fail to reach a common agreement or understanding, that bridge inevitably becomes burned - even if I'm correct, even if most people agree with me! It was based on my understanding of how other people reacted to the controversy as it was brewing in community spaces, but I understand now how it could have been interpreted as a threat in its own right.

The reason I made a comment below the post (now deleted as per the game author's wishes) is because I saw him accusing the gbdev community of "censorship" - as such, I wanted to provide full transparency and accountability with regards to my role in the dispute. That was the extent of what I could do at the time, as someone who was never involved in the organization of gbcompo23 or any other gbdev community event and thus had no decision-making powers. I realized later that my stance led to harm. I regret getting involved in this at all, and I regret the things I said.

I'm not so sure about that. More specifically, I wonder if there are more or fewer Steam Decks in the wild than jailbroken Nintendo Switch units.

Couldn't, not at the time. HBC has been open-sourced some time ago, sans DRM, as the Wii has long lost commercial relevance beyond enthusiast communities. This open-source re-release is what the repository is.

Writing

    to = append(to, ctrl)

In fact, it seems that any placeholder value should work - as it is always overwritten by the final value of ctrl for a given set of bytes at the end; however, the checker rejects this.

Therefore, for the Linux kernel specifically, I think the only concern is whether or not GCC remains supported in addition to LLVM - as GCC and Clang are, as far as I know, the only two compilers which actually can be used to build the kernel as we speak. There's work being done on both gcc-rs and rustc_codegen_gcc to allow using GCC as a Rust backend, meaning that all platforms currently supported by the Linux kernel should be eventually capable of being supported without porting a compiler backend.

> thanks to the tremendous shared code in Mesa, a basic OpenGL driver is doable by a single person. I’m optimistic that we’ll have native OpenGL 2.1 in Asahi Linux by the end of the year.

It's likely that even a bare-bones OpenGL driver will probably run better than llvmpipe, which is especially important in a laptop context due to the resulting power use improvements.

1. It's a kind of code golf - or rather, it's about seeing how much one can squeeze out of a highly limited and fixed platform. Writing this, I think of things like Mahoney's Cubase64 ( https://www.youtube.com/watch?v=PTGkf21UpJ8 ), which uses a combination of skilled coding and creative (mis)use of hardware functionality to perform real-time effects on sampled audio data on the Commodore 64. As the demonstration itself states: "You need 32-bit, 2000MHz, 1GB at least; what if... 8-bit, 1MHz, 64KB is enough?".

2. Creating a game which can stand its own to the platform's contemporaries on an 8-bit ecosystem can be reasonably achieved by a bedroom coder in their spare time. To do so for modern consoles or machines, one typically needs a higher budget and multiple people.

For this point alone, though, there are arguably easier ways to accomplish this. PICO-8, the herald of the "fantasy computer" phenomenon, created a system inspired by 8-bit limitations in graphics and sound, but offering a modified Lua interpreter in place of coding assembly by hand, in an attempt to balance the stack more towards creativity and away from complexity. (And, of course, nobody is stopping anyone from simply making a retro-styled game with modern tools. Many indie games do exacly that. There's two separate "notable" Game Boy jams on Itch.io - one enforces games actually targetting the real platform, the other cares more about matching the look/feel.)

3. The ability to reason about every component of the system down to bare metal is a welcome retreat from writing complex, object-oriented code running on top of stacks on top of libraries on top of runtimes...

In the end, it's a novelty which tickles a particular part of my brain, I suppose. So long as I enjoy it...

Ultimately, follow-ups are rare because they don't sell - the benchmarks which get referenced are the ones which spread the widest, which are the ones closest to release, which is when usually the most people are interested in a given product.

Not even Windows 1.0x, 2.0x, or 3.x got open-sourced. In terms of complete operating systems, we got source code dumps of MS-DOS 1.25 and 2.0, and that was that.

I don't think it's going to happen.

https://github.com/kud/jpegrescan