Interesting perspective. Lot of good points.
I'm about done for the night and ready to settle down. One thing I did was download the source code for both 'higan', 'bsnes' and 'ares'. DL the 'master' version if you don't DL anything else.
I got these from the link I posted earlier:
https://near.sh/
I realised why it was still up and why it won't be going down any time soon - it's got no personal info, and it's a respository for his magnum opus. Of course he will have one place that links to his 'Meisterwerks'.
There is a lot of similarity between them. ares, the first emulator he did, is a real labour of love.
From there he upgrades things and brings in more compatible frameworks. bsnes is a beast.
This is the one that is just about almost perfect, but it is more about speed and compatibility than raw cycle for cycle emulation. It's all that most people will need to run the games, and for most people it will be the best in most circumstances, but still for some, the quest for perfect emulation exists and this is why he built 'higan'.
higan is a multi-system emulator focused on accuracy and preservation. Its codebase is intended to be self-documenting as the the original design of the hardware that it supports.
higan employs a unique user interface with the goal of providing the most faithfully accurate emulation possible, but as such, has a somewhat higher learning curve compared to more traditional emulators.
I think I got that right. Don't shoot me if I'm wrong. I'm learning as I go here.
So among other stuff, I would say these are the 3 (very much related and share source code) main works of his life. They share common emulations to a lesser or greater degree.
ares claimed 1 out of 5 stars emulation capability for the Playstation. By the time higan came about it had dropped all support for that particular emulation.
What surprised me was that each of these 'engines' contained support for about a dozen or two dozen different formats. Game Boy's, Mega Drive's.
Near would have had nearly no sleep the last decades to accomplish this, apart from having to be a learn as you go near Genius as well, while he did. As I get to know the man more, I get the impression he just felt unappreciated, worse than that, unknown. Which he was till this little stunt.
Anyway I won't shit up the thread and ponder any more about this. The links are there for any one with rudimentary knowledge in this area to peruse. And by that I mean those that actually used these games, used these emulators. Please, let's here more from them again - they were around earlier in the thread and they really knew what they were talking about. They have more to offer than anyone.
===
So as I said, I downloaded the source code for each of these 'engines' of his: ares, bsnes and higan. They share a lot of similar code, of course, because he was building on his framework and you really don't want to reinvent the wheel when you got it perfect first time 'round.
He even knows which multiplication algorithms were used (see
https://en.wikipedia.org/wiki/Multiplication_algorithm) - and he works out it was Booth's algorithm:
https://en.wikipedia.org/wiki/Booth's_multiplication_algorithm
His source code is not commented at all. This is a hacker at work. In his own domain.
He was both a cracker and a hacker, in the truest meanings of those words, that have been all but obsoleted now by overuse. (See 'fascist', see 'nazi', see 'communist').
The skills required for him to reverse engineer and crack the code both at the software and hardware level are something else. Each of those is a distinct and discrete process. But more than that again, this boy can code! He codes fucking beautifully. Even though he does not comment his code, his indentations are sublime. And it is consistent.
We are dealing with a rare kind of genius here.
To be a reverse engineer or cracker in software you need instinct as much as anything else. You don't need to be able to code or 'hack' but you do need to know assembly language to a more than rudimentary level. Coding helps, but is not requisite. All those languages boil down to the same machine code, the same assembly instructions when decompiled or disassembled.
And Near knew how to both break them down, and then build them back up again.
I've just been studying his C++ (.cpp) classes in the 'ruby' folder he has in common with all three of these 'engines': ares, bsnes, higan. It is very elegant. It is very clean. It shows a very lucid and disciplined mind. A beautiful mind. I studied the 'audio engines' in particular as I am more familiar with those. He probably didn't even need to comment it, because the structure he gave was so logical and so lucid, that it almost just commented itself, if that makes sense. This is a man with deep insight and proficiency with C++. Obviously it just worked.
And not a single comment in sight.
And he even talks about different audio interpolation methods. Figuring out and replicating the cubic spline interpolation methods of the OG when it came to time-stretching samples in audio.
This was a mind chomping at the bit and just spitting out everything needed in the most efficient fashion.
The fact he made it all open source as well so any idiot like me (who doesn't know what he's doing) can take a look at it, well, I think that speaks volumes as well. He wasn't a selfish person. He wanted to make the world a better place, to enhance it. But I really think he wanted to be noted for doing this, and in this hubris, was maybe his downfall.
Anyone can look at that code. I gave the links.
I could probably spend the next 10 years studying what he has done, not going outside, and then coming to the frightful realisation that Near and hundred other crackers/hackers did: Was it really worth it, to not touch grass, to only get the goodboi points from those fickle souls that would sell you down the river quicker than you could ever say 'sorry'.
I've lost scope and I'm just rambling.
Do you see how quickly this madness can take you over?
TL

R: Near was that most rarest of breeds, he was both a reverse engineer (a very specialised field) and also a programmer (a very specialised field).
For 'reverse engineer' see 'cracker'.
For 'programmer' see 'hacker'.
He was both.