Pretty wild that MAME has been under active development for over 28 years with the core concept unchanged and no serious forks. It must have a very committed dev community.
A C++ codebase with bonus non-C++ code that generates C++ code plus a build-process-that-generates-build processes all with maniacal inter-dependencies and a guy who insists on renaming everything and moving all the files around in git-destroying ways twice a year does indeed create a bit of a monks-in-the-caves vibe.
Afaik gurudumps is a total jerk, constantly being hostile for no reason to newcomers.
Haze is almost always in conflict with mame lead Cuavas when trying to upstream his code, but his anger mostly justified.
Cuavas is a huge micromanager, he won't accept your code even if you just missed a typo in a line comment.
I respect his commitment to hold the codebase to absolute standards, but sometimes he takes his micromanagement too far that just makes the whole process unproductive.
The personalities working on this project are so hostile, usually without the skill to warrant it, that it's one of the few cases where having a CoC wouldn't be a horrible idea.
This reminds me that Linus Torvalds quote that the point of open source isn't just the right to fork but also the right to merge, and that's what justify copyleft
Do you have the quote? I would think such "right to merge" would go against the notion that maintainers work for free and have no obligation to merge your work.
Edit: Found the quote. The Right to Merge is about the maintainers right to merge your fork/changes back to their branch. Not the other way where random dev have a right for their changes to be merged into the original project
There are actually a good numer of forks, but not sure if they qualify for your criteria of "serious" or not.
I also won't be naming any of them because those "committed" mame devs are very quick to inject themselves into any story about them, and harshly judge everything else that touches their code that didn't come from them.
Mame is the most comprehensive emulator you'll ever get. They emulate everything under the sun: from very obscure computers that you don't even find info on the internet to mechanical car rides (yes they even preserve the roms for those).
Yeah, it's absolutely amazing and noble, especially for us that are into those things (Personally, I have a vast collection of consoles and games, including full SNES library etc.). Wikipedia, Internet Archive + Common Crawl, Emulation scene with now MAME at the forefront - those are Alexandria of our times.
Just finished reading The Thinking Machine. Highly recommend it if you're interested in how Nvidia became the most valuable company on earth: https://amzn.to/42z8JPF
Can someone at Google explain why the company can’t end formal support for the thermostat but make the API open? It’s a thermostat. It has 3 real functions - cool, heat, fan. What could it possibly hurt to let owners access the endpoints without touching Google servers?
This assumes Google's servers are pushing to the thermostat. It seems more likely that the thermostats are pulling from Google's servers, so that they don't have to worry about firewalls.
With a big company like Google I'm sure lawyers are the ones preventing an open API and not the developers. The API is a liability for Google. It could infringe on patents or it could have a bug.
I was hoping that at least my Home Assistant integration would keep working. That sucks terribly. Lesson of the day: Avoid any IoT device that you can't use without an external service.
FWIW, I replaced my Nests with Centralite Pearls a few years ago, and have been extremely happy with them WRT Home Assistant. The Pearl doesn't seem to be widely available anymore, but any Zwave or Zigbee thermostat + a local hub gets you a thermostat that should work with Home Assistant and will be immune to being sunsetted like this.
reply