Hey there! For complicated reasons, some of which I will explain later, I'm in the middle of dong a pretty gigantic revamp to the Motte codebase. Right now, this means "fix a bunch of small bugs". Later, other things will be happening.
The immediate goal of this is not to massively transform the site or do a Digg v4/New Reddit thing. Frankly, if the site remained exactly the same (but with fewer bugs) I would be happy.
The long-term goal isn't going to be quite that static, though. The long-term goal is to set things up to allow more subcommunities, similar to how subreddits work. This will be a larger set of changes. These changes will not obsolete The Motte itself; I am absolutely aiming for a site that can comfortably keep holding The Motte. I've talked about this before if you want to go read about it - this is still the same plan, for what it's worth, it's just now being (slowly) executed.
I will be posting more, and asking questions about next steps, when actual site behavioral changes are in the queue. This just isn't that! This is infrastructure work.
tl;dr: The site backend may be a little wonky for a bit, sorry about that, please report any bugs.
(and mods, feel free to unsticky this in a few days if I forget)
Jump in the discussion.
No email address required.
Notes -
I have yet to see a website where it would matter. I mean, there are many workloads where pure bit shuffling speed matters. A lot of them run in real world on JVM which has GC, and it doesn't present a significant barrier (note that not having GC does not mean you just get free speedup - some code still needs to do memory management, and maybe your personal homebrew code is more efficient than decades of dedicated work by people writing VMs. Or maybe not). But these workloads tend not to be websites. For the website, it's network speed, I/O latency, memory, caching. But very rarely having GC is any serious consideration.
More options
Context Copy link