Recently, RealLifeLore has been my to go channel to watch the current state of geopolitics thorough the world, I discovered them through the video of "How Rwanda is Conquering Their 100x Larger Neighbor" (https://www.youtube.com/watch?v=0N34UFbWpFk)
Chip8 is the rite of passage for many emulator devs due to its simplicity, it can be implemented on virtually every 1 cent microcontroller out there.
It should've had a more dedicated vibrant community if it weren't the many incompabilities among the different emulators implementations out there, all due to people using cowgod's chip-8 tecnical reference as the single source of truth[0], which itself is based on David Winter's original implementation which contained a few inaccuracies on some instructions behavior from the original COSMAC VIP interpreter.
It's rather disheartening to see new chip8-related projects which reference Octo, modern test ROMs written with Octo, and still see a citation for cowgod's egregiously incomplete and misleading documentation.
Damn Small Linux was one of the first distros I tried out as teenager with a LiveCD. It's sad it fell out due to his lead being rather an asshole with his contributors and overall incompetent.
BTW, one of former core contributors went to make their own distro called TinyCoreLinux.
It doesn't makes him less a hero rescuer if many others were still involved, in fact, every diver who volunteered on the rescue effort is a hero on my book.
> There were teams from 11 countries, Musk included.
What did Musk help exactly, other than coming up with an impractical solution, then calling the hero rescuer a "pedo guy" after getting his big ego bruised?
I know x86-64 zeroes the upper part of the register for backwards compability and improve instruction cache (no need for REX prefix), but AArch64 is unclear for me.
It's to break dependencies for register renaming. If you have an instruction like
mov w5, w6 // move low 32 bits of register 6 into low 32 bits of register 5
This instruction only depends on the value of register 6. If instead it of zeroing the upper half it left it unchanged, then it would depend on w6 and also the previous value of register 5. That would constrain the renamer and consequently out-of-order execution.
He has a pattern of taking any bit of criticism of his language on bad faith, and immediately goes all defensive accusing the criticizer of being a psyop working with a rival language.
If programming is just my hobby, then maybe. But would you, for example, quit your current job and look for another, just to change the programming language? I know I'm not that sort of person.
I think it's not as much "if this guy becomes the lead I'm immediately quitting my Ruby job to return to PHP" as much as "if this guy becomes the lead I'm probably going to return to PHP for my next job."
I have my doubts, even for this softer version. These are things where one might feel very strongly in a moment, or even for a longer time, but facing a real life decision, there are so many other factors.
Of course we will never know the outcome of this, it's just my two cents.
Commendable action! If feel like it's a different case though. Two points:
1. Working for someone, even through a large company, is a much more directly supportive relationship, than using someone's free project. Especially since the project has a lot of large contributors.
2. A company is interchangeable, a skill is much less so. You can do the same, or very similar thing at the next company, but moving to a different language involves a lot of learning, even though both are programming languages.
For these reasons, if talking about a lot of people, I can see many of them leaving a problematic company, and only some of them changing their primary language. I'm sure there's someone out there throwing away two decades of experience for an ideal, but I don't think it's realistic, especially not for 1 problematic blog entry.
It's an old legacy technology that needs to die out from all forms of distributions (looking at you GNU)
reply