I'm running multiple services such as Forgejo, Audiobookshelf, Castopod and they all need no more than roughly 100 MB RAM.
There is one exception though. Open WebUI with a whopping 960 MB. It's literally a ChatGPT interface. I'm only using external API providers. No local models running.
Meanwhile my website that runs via my own Wordpress-like software written in Rust [1] requires only a few MB of RAM, so it's possible.
Is this an inevitable future? The amount of people ready to cede their computational resources, thinking, digital sovereignty, to centralised platforms, all in the name of progress, is truly shocking to me, especially in the current political moment.
The main reason I do not prioritise AI usage in my own life is to retain my skills and mental acuity. All of the forms of computing and opportunities that I value do not require AI to achieve. I can understand why people feel differently from me, though, because AI and AI-adjacent things are where all of the money is right now.
No, clearly not. First, future is never inevitable, and second, I was being ironic. Though the fact is that thin vs rich clients is one of the major fashion cycles in the IT industry.
You know what is the sad part. I don't think software developers or LLMs know how or want anymore to make low resource consumption software that runs on a thin client. It will be some browser based thing capping to whatever memory is available on the system.
Even if the AI bubble bursts, having successfully cornered the compute market they can just go rent seeking instead by renting out cloud workstations, given that they've made the hardware to build a workstation yourself unaffordable.
Could be done, but nothing is EVER simple regarding IPv6. :) What about EUI-64? Any special cases regarding TEREDO, ORCHID2, 6to4 addressing scheme (NOT the same as NAT64!), etc...?
Nevertheless, something like this could be an option.
The 20% ISON adds:
- Multiple named tables in one doc
- Cross-table references
- No escaping hell (quoted strings handled cleanly)
- Schema validation (ISONantic)
If you're stuffing one flat table into context, CSV works fine. When you have users + orders + products with relationships, ISON saves you from JSON's bracket tax.
Look, YEC are notorious for lying and cherry picking, almost as bad as flat earthers. The "Gish Gallop" technique is named after a creationist. ChatGPT is not know for giving the same answer twice. These aren't perfect heuristics, but it would seem rational to view the combination of both as logical poison.
I am not going to defend every YEC. But you are using too broad a brush. Read the book and decide for yourself. We did not use chatgpt to write the book; it was part of the editing process and we checked everything from chatgpt, because, as you said, it is not known for watertight reliability.
L’évolution des technologies de virtualisation sur architecture x86 représente l’un des aspects les plus significatifs de l’informatique moderne. Son histoire illustre comment les contraintes architecturales du processeur x86 ont conduit au développement de nouvelles solutions, puis de nouveaux paradigmes. Les quatre technologies abordées ici — Xen, VMware, KVM et QEMU - ont chacune apporté des approches distinctes pour résoudre les problèmes fondamentaux de la virtualisation x86. L’aboutissement actuel étant l’informatique par l’approche du nuage.
Yes, AI is nice, but I also like to be able to buy some RAM and drives…
reply