sleeping in the shadow of the empire state
Dec. 18th, 2025 07:56 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
musesfoolI am officially on vacation - I don't have to go back to work until January 5th! Now the bakepocalypse can begin! I've made more work for myself, but I think it will all work out - I've been planning it in my head, and this is how it goes (please take "run dishwasher" as a given at least once and probably twice each day):
( 6-day plan )
I think adding in the roast pork and the pork buns and the orange cranberry rolls might be kind of nuts? But also having that food on hand will let me eat breakfast/dinner without having to do any real cooking or ordering in. (I will also have some ham and cheese to make sandwiches if it comes to that, and some granola bars for snacks/breakfast if the orange cranberry rolls don't happen.) And I think I do have time before the cupcake baking begins in earnest.
What I'm considering now is whether I should make the frostings and immediately but them in piping bags (with specific tips in) for storing in the fridge instead of trying to do the transfers all at once on Christmas Eve morning the way I usually do. Filling the bags and then keeping them in tupperware might be easier? But I've also found that sometimes my "time-saving" plans end up making things worse, so idk.
Anyway, that's my plan for the next 6 or so days! It's a good thing I enjoy cooking. *g*
*
( 6-day plan )
I think adding in the roast pork and the pork buns and the orange cranberry rolls might be kind of nuts? But also having that food on hand will let me eat breakfast/dinner without having to do any real cooking or ordering in. (I will also have some ham and cheese to make sandwiches if it comes to that, and some granola bars for snacks/breakfast if the orange cranberry rolls don't happen.) And I think I do have time before the cupcake baking begins in earnest.
What I'm considering now is whether I should make the frostings and immediately but them in piping bags (with specific tips in) for storing in the fridge instead of trying to do the transfers all at once on Christmas Eve morning the way I usually do. Filling the bags and then keeping them in tupperware might be easier? But I've also found that sometimes my "time-saving" plans end up making things worse, so idk.
Anyway, that's my plan for the next 6 or so days! It's a good thing I enjoy cooking. *g*
*
![[syndicated profile]](https://www.dreamwidth.org/img/silk/identity/feed.png){kind=small}
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif){kind=small}
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif){kind=small}
I think there are many.
Some examples:
* The fastest code is the code you don't run.
Smaller = faster, and we all want faster. Moore's law is over, Dennard scaling isn't affordable any more, smaller feature sizes are getting absurdly difficult and therefore expensive to fab. So if we want our computers to keep getting faster as we've got used to over the last 40-50 years then the only way to keep delivering that will be to start ruthlessly optimising, shrinking, finding more efficient ways to implement what we've got used to.
Smaller systems are better for performance.
* The smaller the code, the less there is to go wrong.
Smaller doesn't just mean faster, it should mean simpler and cleaner too. Less to go wrong. Easier to debug. Wrappers and VMs and bytecodes and runtimes are bad: they make life easier but they are less efficient and make issues harder to troubleshoot. Part of the Unix philosophy is to embed the KISS principle.
So that's performance and troubleshooting. We aren't done.
* The less you run, the smaller the attack surface.
Smaller code and less code means fewer APIs, fewer interfaces, less points of failure. Look at djb's decades-long policy of offering rewards to people who find holes in qmail or djbdns. Look at OpenBSD. We all need better more secure code. Smaller simpler systems built from fewer layers means more security, less attack surface, less to audit.
Higher performance, and easier troubleshooting, and better security. There's 3 reasons.
Practical examples...
The Atom editor spawned an entire class of app: Electron apps, Javascript on Node, bundled with Chromium. Slack, Discord, VSCode: there are multiple apps used by tens to hundreds of millions of people now. Look at how vast they are. Balena Etcher is a, what, nearly 100 MB download to write an image to USB? Native apps like Rufus do it in a few megabytes. Smaller ones like USBimager do it in hundreds of kilobytes. A dd command in under 100 bytes.
Now some of the people behind Atom wrote Zed.
It's 10% of the size and 10x the speed, in part because it's a native Rust app.
The COSMIC desktop looks like GNOME, works like GNOME Shell, but it's smaller and faster and more customisable because it's native Rust code.
GNOME Shell is Javascript running on an embedded copy of Mozilla's Javascript runtime.
Just like dotcoms wanted to dis-intermediate business, remove middlemen and distributors for faster sales, we could use disintermediation in our software. Fewer runtimes, better smarter compiled languages so we can trap more errors and have faster and safer compiled native code.
Smaller, simpler, cleaner, fewer layers, less abstractions: these are all goods things which are desirable.
Dennis Ritchie and Ken Thompson knew this. That's why Research Unix evolved into Plan 9, which puts way more stuff through the filesystem to remove whole types of API. Everything's in a container all the time, the filesystem abstracts the network and the GUI and more. Under 10% of the syscalls of Linux, the kernel is 5MB of source, and yet it has much of Kubernetes in there.
Then they went further, replaced C too, made a simpler safer language, embedded its runtime right into the kernel, and made binaries CPU-independent, and turned the entire network-aware OS into a runtime to compete with the JVM, so it could run as a browser plugin as well as a bare-metal OS. Now we have ubiquitous virtualisation so lean into it: separate domains. If your user-facing OS only runs in a VM then it doesn't need a filesystem or hardware drivers, because it won't see hardware, only virtualised facilities, so rip all that stuff out. Your container host doesn't need to have a console or manage disks.
This is what we should be doing. This is what we need to do. Hack away at the code complexity. Don't add functionality, remove it. Simplify it. Enforce standards by putting them in the kernel and removing dozens of overlapping implementations. Make codebases that are smaller and readable by humans.
Leave the vast bloated stuff to commercial companies and proprietary software where nobody gets to read it except LLM bots anyway.