Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rurban
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
361.
▲
by
rurban
6mo ago
That's bad for him, because he already had a cheap plan. Now he wont get it back that easy. Pro is gone. OpenAI plans are more expensive. He can only buy a Kimi plan, which is at least better than Sonnet. But frontier for cheap is gone
362.
▲
by
rurban
6mo ago
Do I have to do osdev language research for you now? I'm certainly missing some, but out of my head: Mesa/Cedar, Concurrent Pascal, Smalltalk, Lisp, ADA, C#/M# for Midori/Singularity, Oberon, ...
363.
▲
by
rurban
6mo ago
Yes, Rust is a good systems programming language. Just not safe. Safer than most others, yes. Good enough, yes. But there exist safe systems programming languages. Safe systems were done in these languages. Just nobody cared, so they died o
364.
▲
by
rurban
6mo ago
sure, but when the tide switches to a far-left government they might use it against them.
365.
▲
by
rurban
6mo ago
In my calculation a good opus developer can do 10x more, not just 50%. Got all my tickets from the last two years fixed on a few days. And implemented all the ideas which came to my head.
366.
▲
by
rurban
6mo ago
My company has Github Business, which provides all major models. Claude runs out of tokens usually in the middle of the month. I can use it with opencode. Then one extra Claude Pro. Then also: Codex business for a test month. gpt-5.4 was e
367.
▲
by
rurban
6mo ago
They do have the death penalty now in Israel. So it might get interesting for those bosses
368.
▲
by
rurban
6mo ago
Sure, that's why safe languages forbid users to use unsafe things. "C programmers think memory management is too important to be left to the computer. Lisp programmers think memory management is too important to be left to the use
369.
▲
by
rurban
6mo ago
Non-blocking IO is only one part to provide concurrency safety. Process locks are even worse. All locks are forbidden to avoid dead-locks.
370.
▲
by
rurban
6mo ago
Ha, I did maintain two safe languages. How many did you?
371.
▲
by
rurban
6mo ago
The perfectly safe ideal does exist and is called safe. Calling unsafe safe is not even Sophism, it is mere lying
372.
▲
by
rurban
6mo ago
So you are fine in calling a language "safe", when it has unsafe blocks, which the compiler skips to check? You have to that manually, and then you are back in C++ land. That's hilarious. You can call it somewhat safe, or mos
373.
▲
by
rurban
6mo ago
I don't do Javascript, but any self-respecting language which calls itself safe is actually safe. I worked for decades in actually memory and type safe languages, and never ever heard of a memory or type safety bug. Just not the cheate
374.
▲
by
rurban
6mo ago
Have you ever seen a GC system with memory unsafeties? I cannot remember any
375.
▲
by
rurban
6mo ago
Sure, but then they shout all over how safe they are. They got rid of the safeties pretty late, when they ripped out their GC, but kept their false promises all over. No, that's common knowledge. I fixed concurrency safety by forbiddin
376.
▲
by
rurban
6mo ago
Sure, besides those bugs, read the specs. unsafe blocks. Loud and clear. worse than in Java where the unsafeties were just in a hidden sun class.
377.
▲
by
rurban
6mo ago
But why do have all these Intel ME, AMD PSP and ARM TrustZone / Secure Bootloader backdoors in all but RISC-V CPU's now, when they have to reboot poor stupid Jupiter, Cisco, Fortinet, and MikroTik devices? Oh, that's for the
378.
▲
by
rurban
6mo ago
That's my auto-correction, because I'm doing too much embedded (Firmware-over-the-air updates). Frontier it should be called.
379.
▲
by
rurban
6mo ago
The language design contract is unsafe by default. In memory, types and concurrency. What are you talking about? There are unsafe blocks all over the stdlib. And concurrency safety would need to get rid of their blocking IO, which they have
380.
▲
by
rurban
6mo ago
Oh oh, who would have thought. A memory-safe rust at last. With no unsafe allowed, even type safe. Unless you forget about their type bugs: https://github.com/Speykious/cve-rs . So maybe eliminate type and concurrency
381.
▲
by
rurban
6mo ago
Well, my python and typescript folks are also happy with the simplier local models. But I'm using more advanced stuff, C/C++ embedded real-time, vision AI, and compilers.
382.
▲
by
rurban
6mo ago
For training our AI model of course. Inference is for the cheaper machines.
383.
▲
by
rurban
6mo ago
I do exactly that also, like ten thousand of other emacs users. We can customize our editor with a proper language, no need for forks.
384.
▲
by
rurban
6mo ago
Local models are not comparable to the FOTA models at all. I know what I'm saying because I do have 4 local H100's in my server, and could run the very best local models. It's night and day. They are unusable and stupid.
385.
▲
by
rurban
6mo ago
They reproduced the bug finding, but they did not come with the reproducers! Only that's why it is so dangerous. Anybody can come up CVE's, but easy reproducers enable hacking to everybody, not just experts.
386.
▲
by
rurban
6mo ago
But on emacs I prefer the opencode integration. Everything is open, and mostly works better than in claude or codex.
387.
▲
by
rurban
6mo ago
Big companies are exposing customer data all the time, and they are doing all fine. The more criminal negligence, the richer.
388.
▲
by
rurban
6mo ago
Instead of Lisp in Small Pieces I'd recommend SICP instead. No continuation passing, but much better written.
389.
▲
by
rurban
6mo ago
You'd need Mythos to free your iPhone, SamsungTV, SmartWatches or such. Maybe even printer drivers.
390.
▲
by
rurban
6mo ago
Because it was good until January 2026, then it detoriated into a opus-3.1. Probably given much less context windows or ram.
More ›