It's hilarious that atm I see "Moltbook" at the top of HN. And it is actually not Moltbot anymore? But I have to admit that OpenClaw sounds much better.
Singularity of AI project names, projects change their names so fast we have no idea what they are called anymore. Soon, openclaw will change its name faster than humans can respond and only other AI will be able to talk about it.
I went to install "moltbot" yesterday, and the binary was still "clawdbot" after installation. Wonder if they'll use Moltbot to manage the rename to OpenClaw.
Playing Metal Gear Solid 2 was one of my fondest memories I cherish. I could play it only at Taekwondo gym I was attending to. I couldn't finish it because I only had a couple of hours at the gym and I could play only during break time. Oh and I was always waiting for the break time!
I enjoyed writing git commit messages. I value good commit messages. But at work I recently created a slash command (for those who don’t know, it’s like a snippet for anything) that writes a git commit for staged changes with optional jira tags. Although I always end up amending it, it is so convenient. Does it mean I don’t value good git commit messages? I don’t know… I try my best to review every commit at least.
I didn't know about WoW64 mode. I remember when trying to install an old windows program I had to install a bunch of 32-bit translation library for audio and stuff. This WoW64 means that I can just simply use 64-bit arch. This is fabulous.
I remember I was using Gentoo when I first tried WoW64. I tried it because I didn't feel like compiling all those 32bit libraries. And it turned out that Wine's WoW64 mode worked just fine. It was really handy.
It's a bit different. WoW64 is the technology used to run 32-bit applications on 64-bit Windows. Wine has support WoW64 for a long time. The difference is the "old" wine WoW64 mode required 32-bit libraries on the host side, whereas this "new" WoW64 mode doesn't.
It's a bit different. WOW64 is a compatibility layer that intercepts calls into system libraries from 32-bit apps and translates them into calls to 64-bit libraries. macOS shipped both 32-bit and 64-bit versions of all system libraries, no translation involved.
I’m not very familiar with the Windows side, but it sounds harder to create but easier to maintain. Once the 32->64 translation shims are implemented, you’re done. They’ll keep working. If you’re not adding new 32-bit APIs then there’s no more work to be done. Maintaining a parallel set of libraries means each change has to work on both targets.
To me, Apple's ML business was all about federated learning. I know this concept was pre-transformer era, I conjectured one of the reasons Apple didn't adopt LLM right away was that Apple couldn't find a reasonable way to do federated learning with LLMs. I wonder Apple will give up this idea. And I would like to see how it could be done with current AI systems.
reply