The same way it's done now with current generation consoles: the manufacturer would provide you with SDKs and development hardware once you paid them a decent chunk of money and signed an NDA. Prior to the fifth generation it was common for the SDK to be just an assembler, debugger and register-level hardware documentation, leaving the implementation of a kernel and game engine up to the game developer.
Sony however decided to provide a full C toolchain based on GCC as well as a set of very high level libraries that abstracted away basically all aspects of the PS1 [1], all the way up to implementing a ready-to-go 3D engine and MIDI sequencer. This was an unpopular move as the libraries were slow, inefficient and most game developers were used to having full control over the hardware, but it also allowed inexperienced devs to get started quickly (as proven by the thousands of low budget PS1 titles that used the high level APIs) and eventually contributed to the popularity of the console over its peers with worse tooling.
Sony would eventually go on to release some slightly lower level documentation for certain aspects of the console as well as APIs that better mapped to how the hardware actually worked under the hood. It wasn't however until years later that the hardware would be fully reverse engineered at the register level [2], and it took even longer for most homebrew to move away from the official SDK (which only really started happening a few years ago as accurate emulators and homebrew SDKs started popping up).
It may actually be helpful to emulation. There's a technique called High-Level Emulation, where instead of emulating the hardware registers that are twiddled by the SDK function, you recognize the call to the SDK function itself and emulate the whole function in one go. This can provide a massive speedup over low-level emulation, but relies on the game primarily using the SDK. This was also used to emulate the N64 on Windows 95.
They had stuff, but it was all proprietary. The N64 was a stripped-down implementation of the technology used on (high-end) SGI graphics workstations of the time. SGI certainly had all the required tools.
Recompilation projects aren't bit perfect, only decomps. They use a recompiled version of the compilers for Linux so that they don't need to emulated with QEMU like they used to, though.
I think the "nothing I can do will change anything" is actually a predominant theme that's emerged over the past decade. I don't know if you've watched any of Adam Curtis' documentaries, but his documentary HyperNormalisation explores this in great detail (most of this documentaries have a similar theme I've found).
Edit: Apologies, I think I mean his documentary: Can't Get You Out of My Head. Essentially it asserts that all revolutions fail, because the people who attempt to overthrow simply become the new guard.
> People on the side of The People always ended up disappointed, in any case. They found that The People tended not to be grateful or appreciative or forward-thinking or obedient. The People tended to be small-minded and conservative and not very clever and were even distrustful of cleverness. And so the children of the revolution were faced with the age-old problem: it wasn't that you had the wrong kind of government, which was obvious, but that you had the wrong kind of people.
Additional context: The city is being (mis-)ruled by a paranoid dictator, whose brutal secret police don't care too much about if you're innocent. The cynical protagonist is frustrated that some of the resistance is also extremist or at least overly-optimistic about what's going to happen next.
Adam Curtis docs are wonderful. I've grown so accustomed to when people suggest a doc, its some youtuber that posts a doc once a week and utilizes the youtube documentary style to disguise how poorly executed it is. Adam Curtis is certainly not that, for anyone considering this suggestion.
When I was a lot younger I built a very big and complex platform with Phoenix. Although it was a technical marvel, it's one of my big regrets as far as the tech stack I went with, because it's now useless for my actual work now a decade later.
Do you mean because you can’t use Elixir/Phoenix for work? Because I don’t quite understand, doing a big project and learning/using a particular tech stack should have many transferable skills.
alldebrid. their 4.0/4.1 api has all the stuff to decode magnets and browse their files. filter mkv,mp4,etc. i made a little database of imdb tt values to assist autosuggest for searching and a nsfw filter for the few friends and family using the app.
have thought about extending it to realdebrid/torbox/etc but it's just been kinda set and forget. every once in a while will add a feature... most recently i think was seeing if there was a matching srt file and feeding that along with the video file to vlc so you get subtitle support if it's not baked into the video file
Most of Japan doesn't have excellent public transport.
Car ownership is less common in most of the places in Japan with excellent public transport.
But I do like that each car legally requires its own parking spot. It is tricky to go to people's homes, because often extra parking is extremely limited or non-existent. It requires specific planning.
