Earlier quoted context omitted.
It feels very different. It's all damn instant. Me happy.
That’s wonderful! I’ve made ultra-lightweight web apps of my own to replace bloated, slow, and poor UIs. It’s a night and day difference when the dependencies are few-to-none. And that’s on a fat browser stack. Your ASM desktop must zip!
A desktop made for one
71–80 of 281 posts
Re: A desktop made for one
#72Re: A desktop made for one
#73I (and I'm sure many others) have been thinking about this a lot over the last couple of months. I called it "Extremely Personal Software" in a blog post a few months ago ( https://redfloatplane.lol/blog/14-releasing-software-now/ ) but there are lots of names and concepts floating about for the same basic idea. I think it's possible the amount of new software that will be written for an audience of 1-10 will be grea…
Re: A desktop made for one
#74Earlier quoted context omitted.
I had the same reaction. We're headed into a period where you can shape your tools exactly as you like them; artisanal rather than factory-created workshops, essentially. I think the instinct that APIs, validation layers, and so on take on a much higher importance is right.. I have a few internal tools that made sense to make libraries out of, and once the first library is good, and a test suite is comprehensive, por…
"Everting"?
Re: A desktop made for one
#75This is very cool. I wonder how much time did it actually take, and how much did it cost, because Clause Code is very much not free [1] [2]. It's more like hiring a robotic contractor, very fast, but with a serious hourly rate. [1]: https://fortune.com/2026/04/28/nvidia-executive-cost-of-ai-i... [2]: https://www.briefs.co/news/uber-torches-entire-2026-ai-budge...
I'm on Claude Max, so it didn't cost me anything more than the subscription I already have. Had to use it for Something. As for time - for the full CHasm and Fe2O3 suite of sw, I started the work 2026-03-29 and have probably spent 60h or so of my time. But then again I have a very tailored CC setup that I have fine-tuned since last summer with more than 70 CC projects helping me get it the way I need it to be since t…
Re: A desktop made for one
#76Earlier quoted context omitted.
Luddism is when you don't bother reading what someone didn't bother to write.
Dictionaries on the second row down that aisle.
Re: A desktop made for one
#77Did you have to look or review any of the code produced, to get the performance/capabilities that you wanted, or were all interactions through CC? In other words, did you hit any walls with the pure agentic workflow?
I monitored the process very tightly. I have programmed my fair share of asm (and some 30 other programming languages), but for this I did not read any code. I hit lots of obstacles on this road, lots. In the process we also created a complete TTF rasterizer on par with what kitty gives me, and that was a true deep-dive.
Re: A desktop made for one
#78I (and I'm sure many others) have been thinking about this a lot over the last couple of months. I called it "Extremely Personal Software" in a blog post a few months ago ( https://redfloatplane.lol/blog/14-releasing-software-now/ ) but there are lots of names and concepts floating about for the same basic idea. I think it's possible the amount of new software that will be written for an audience of 1-10 will be grea…
Re: A desktop made for one
#79Earlier quoted context omitted.
Just to be contrarian, perhaps some measure of risk is reduced by the scale of one. Identifying a vulnerability that can be exploited against many thousands or millions of targets is perhaps more attractive than a single one of individually low value. This of course would assume that vulnerabilities are in fact unique (which is admittedly questionable).
I had the exact same thought. Pretty low probability that there's going to be a script-kiddie exploit for your custom tools. Pretty decent probability that there will be vulnerabilities present if someone cares enough to target you.
Re: A desktop made for one
#80Earlier quoted context omitted.
Just to be contrarian, perhaps some measure of risk is reduced by the scale of one. Identifying a vulnerability that can be exploited against many thousands or millions of targets is perhaps more attractive than a single one of individually low value. This of course would assume that vulnerabilities are in fact unique (which is admittedly questionable).
I had the exact same thought. Pretty low probability that there's going to be a script-kiddie exploit for your custom tools. Pretty decent probability that there will be vulnerabilities present if someone cares enough to target you.