This just proves that you can cram pretty much anything into the client/server dichotomy if you just define "client", "server" and "request" broad enough. Similarly, I remember how desperately people tried to argue that Emacs follows the "Unix philosophy" as long as your LISP functions are doing just one thing, and do them well.
I don't know what you would gain from these things. Emacs follows the idea of LISP machines, I think that much anybody can agree on. From there, Emacs can be or do pretty much whatever you want. It's excellent in communicating with CLI tools - you can call that client/server if you want, but I wouldn't know what you'd gain from that definition. The reality is that Emacs has gone through a lot of fads and hypes over its decades of existence, and each time, it has taken something along the way. Heck, there's a whole semantic parsing engine buried within (CEDET), which nowadays is pretty much unused, because then LSPs came along, and now we have agents (which Emacs btw is a pretty decent frontend for).
> Anyone with physical access. I think it is understandable from the phrase.
Sorry, I'm probably dense, I still don't get it. You steal a laptop, you open it, the screen is locked with a password/fingerprint whatever. How do you read out the RAM from that laptop?
> Except that, for more than two years, the encryption key remained resident in memory across suspend, leaving it there for the taking by anyone who seized the still-powered laptop.
I don't get it. Obviously, the laptop is locked when it resumes, how is that key "for the taking by anyone"? I'm not saying it is impossible to read out RAM from a locked laptop, but surely not by "anyone".
Well, when they announced it (7 months ago) I got laughed out of the room when I said this will be at least 1k$ because of the RAM crisis, and people quoted famous Youtuber "Moores Law is Dead" that this thing has a 300$ BOM and will be 600$ max, probably just 450$...
I can understand the joy of running things yourself, and can also see the privacy aspect. However, I pay ~3$ per 1M/tokens for that model on Openrouter, and it's not even quantized. A refurbished 3090 and a 5080 will set you back well over 2k, not to mention the electricity to run them...
That engineer went on to create Brave, a browser that pays you Monopoly money for watching ads, injected affiliate links, installed their commercial VPN without asking, and leaked DNS traffic when using Tor in its "privacy" mode. I'd say Mozilla dodged a bullet there.
I wouldn't say these are "basic bugs". The first is specific to using 'rrsync', and the second is when using the rsync daemon, and I can't remember when I last saw a system using that one (yes, I'm aware there are still use cases for using the rsync protocol, but I would consider it pretty obscure nowadays).
You could argue that he should've bumped the version more and should've done a longer beta test, but on the other hand, these were mostly security fixes, and I can understand he wanted to get them out there rather sooner than later (also "doing a beta test" is easier said than done - how do you get people to run a test version of rsync?).
These servers had no fan control whatsoever, they always ran full blast. That's not untypical for rack servers, because as written: they are designed for server rooms, and you're supposed to wear ear protection there anyway... Yes, I could've modified them, but I ditched them because running them simply made no sense (especially the high idle power consumption was ridiculous).
OK, then you're in luck. I had a bunch of old 1U rack servers and even in the next room it was too annoying to run them (they had a bunch of 40mm fans which always ran at full speed, because in a server room, no one can hear you scream).
Nice post and technically impressive work. I agree we need to understand the build pipeline and be able to do things locally. However, depending on your electricity cost, it might not make sense financially. These old servers are not energy efficient at all (I'm guessing that old Xeon server will easily pull 200W on load), and that model is currently at 0.1$/0.3$ per 1M tokens (with 76 tps and 262k context) in Openrouter (also, these servers are LOUD).
EDIT: I stand corrected, 200W is apparently way too high of an estimate. I used to run a bunch of old Xeon servers and they slurped watts like crazy, but I can't remember which ones exactly those were.
Well, if Apple killed it, Lenovo killed it even more. I recently was looking for a laptop for a student. The Lenovo E14 Gen7 is 800 Euros here in Germany (where prices are always higher, the MacBook Neo is 700 Euros), it has 16GB of RAM, 1TB SSD, a 2.8k IPS display, a Intel Ultra5 12core CPU, and it has a repairability score of 9/10 from ifixit. Framework doesn't even come close to that package.
Looking at all the unmerged pull requests in ripgrep, you can see what's going on. I will not link him here, but for instance, there's a "Senior Software Engineer at Microsoft", whose agent created 260 PRs in 211 repos with trivial typo fixes in code comments(!). Almost all of them are rejected (including those in ripgrep), but of course, a few get merged and he now boasts he "contributed" to sqlalchemy, Nim and others... What a time to be alive.
So you consider calling something "ironic" an extreme position? On a more general note, you will find that many people are uncomfortable with the idea that AI will replace human work, especially when it relates to art, which this project in question references.
I think we can agree that this is not something anybody will actually use, but rather an homage to "They Live", and IMHO, letting this be done by AI is in contrast to the basic premise of the movie.
So telling someone to make a table for you is more human than making it yourself, because you're using natural language instead of saws and hand planes?