-
Posts
-
By Fleet Command · Posted
Yeah, right! /s They've been saying that for two centuries now. Look up "China's final warning" on Wikipedia. -
By Fleet Command · Posted
It already has. Look up Codename Monaco. -
By +TRS-80 · Posted
I have not verified if any of the fixes mentioned on the below article actually work. Why Claude Code Eats All Your RAM (And How to Fix It) There are at least four separate things that can eat your RAM, and only one of them is your fault. The Four Culprits 1. Bloated Session Logs (The Silent Killer). For 2-4 and more inluding the suggested fixes, see link https://marceloretana.com/blog...aude-code-eats-all-your-ram -
By Nas · Posted
One of my PC's is Windows 11 Home Edition... and guess what? it supports Hyper-V Disks and Containers, as well as WSL2... which these desktop tools leverage on an as-needed basis. It does not need to be enabled system-wide; it merely needs to exist. Furthermore, I tried something yesterday with Hermes Desktop and their "installer" actually builds everything from source as part of its installer toolchain! The installer (and updater as it were) both go through a roughly 19-step process to prep the system for the tool to be used -- and connectivity to local/remote models, local/remote agent configs, and other steps are not included as part of this process (those are all user config steps post-install). ALSO, the "bug wasn't confirmed to exist" is the weakest argument against a bug. That's literally every flawed product's knee-jerk reaction! Even politicians, lawmakers, murderers, and other violent criminals start with that defense... "I deny everything I'm accused of." The bug is the (shared) experience. Whether it's truly Claude Code's fault, or user error, or some other software package being the ultimate culprit, is not the point. They are experiencing unpleasant side effects and don't like that. -
By +TRS-80 · Posted
Each generaton has its exciting times and I was fortunate enough to be right there at the beginning of the PC industry. I don't think any of us at that time realized how large it would become I still remember working on a TRS-80 with a green screen monitor that kept overheating and dying. Also used some TRS-80 PCs with tape cartridge memory. They worked but boy were they slow with everything being a very slow sequential read or write. But heh, they worked though it wasn't long before they were repaced by the HDD.
-
-
Recent Achievements
-
Sopa flores earned a badge
One Month Later
-
StaticMatrix earned a badge
First Post
-
StaticMatrix earned a badge
Week One Done
-
lamborghiniv10 went up a rank
Rookie
-
pinnclepd earned a badge
One Month Later
-
-
Popular Contributors
-
Tell a friend
.thumb.png.b7089ebbdf00d96b3b92dddbd04bac02.png)
Recommended Posts