pizlonator

6 ms·

91.
by pizlonator 4mo ago
My blog post explains how to make prototype chain operations work in the presence of threads
92.
by pizlonator 4mo ago
Yeah I don’t get that either It’s a super successful language
93.
by pizlonator 4mo ago
I don’t understand the thread phobia Comparing it to nukes is a bit extreme, don’t you think?
94.
by pizlonator 4mo ago
The solution to concurrency in JS is hard to understand and I would expect even hardened JSVM folks (me included) to be super confused by it
95.
by pizlonator 4mo ago
Adding concurrency to JavaScript definitely falls in the "complex enough" category So does basically any feature or optimization in a JS runtime
96.
by pizlonator 4mo ago
Damn well trying to enforce an "obviously no bugs" rule in a language runtime would mean zero progress in language runtimes. We certainly wouldn't have gotten to where we are with runtime and compiler quality and performance
97.
by pizlonator 4mo ago
No language runtime is ever in a state of "obviously no bugs". Good luck demanding that of anything of JSC's or LLVM's complexity
98.
by pizlonator 4mo ago
It's substantially based on my design, read the blog post I wrote (linked in another comment here) It's a very complex thing, but not impossible. I'm very impressed that any LLM can do this
99.
by pizlonator 4mo ago
I knew it was possible :-) https://webkit.org/blog/7846/concurrent-javascript-it-can-wo...
100.
Memory Safe Inline Assembly(fil-c.org)
178 points by pizlonator 4mo ago|47 comments
101.
by pizlonator 4mo ago
Yes
102.
by pizlonator 4mo ago
I just had Kimi K2.7-code rebase my Fil-C OpenSSL patch from 3.3.1 to 3.5.7 with quite bare bones instructions and it seems to have worked. 177KB patch, so it's not a small change. The patch did not apply cleanly initially; the agent h
103.
by pizlonator 4mo ago
Yeah! Not being integrated can be an advantage because it gives you the freedom to think outside the box. Meanwhile an AI engineer embedded into an incumbent slide app team has to ask permission and get cross functional alignment for every
104.
by pizlonator 4mo ago
You can create threads in the zygote. It doesn't "break down", but sure, there's a bit more work. My trick for that is that the set of threads that I create pre fork have to be suspendable and resumable, preferably lazil
105.
by pizlonator 4mo ago
You're referring to something else, and maybe I'm using the term "zygote" incorrectly. In all uses of zygotes that I have seen, here's what's really happening: - `fork` is being used to reduce the cost of start
106.
by pizlonator 4mo ago
It ends up on the hot path of programs that use process isolation aggressively
107.
by pizlonator 4mo ago
Fork is marvelous for the zygote pattern Hard to come up with an optimization that is equally efficient and elegant
108.
by pizlonator 5mo ago
How do you know it’s actually memory safe?
109.
by pizlonator 5mo ago
I do this too. I especially love how making a nicely styled website these days is a matter of describing what it looks like and waiting 10-15 minutes. There are other examples But the OP is claiming 10x productivity improvements along some
110.
by pizlonator 5mo ago
Yeah, this is a good point. But the clock is ticking.
111.
by pizlonator 5mo ago
Then where is the big new non toy project created since vibe coding became a thing, that couldn’t have been created without ai?
112.
by pizlonator 5mo ago
Yeah. To play devils advocate, computers didn’t translate to massive productivity gains until long after businesses adopted them. There was that quote from ’87: "you can see the computer age everywhere but in the productivity statistic
113.
by pizlonator 5mo ago
That goes straight to my point: then why hasn’t the miracle of automated coding led to breakthroughs outside of automated coding? If the only breakthrough is automated coding with no outside consequence then it’s just masturbation
114.
by pizlonator 5mo ago
Some examples: - The first web browser - the first web browser with images - typescript - react - rust - Fil-C - doom - quake - the anamorphic VM, and its follow-ups like HotSpot, and even competitors/copycats like J9, V8, JSC, etc - F
115.
by pizlonator 5mo ago
What I can’t get over is that there have been exactly zero software breakthroughs since vibe coding started, other than vibe coding itself. Claude is amazing, that’s true. But if it was as amazing as this article implies, I’d expect some br
116.
by pizlonator 5mo ago
Only 500MB! you are confirming their point even as you contradict the specifics
117.
by pizlonator 5mo ago
I can’t help but read the logic as not being too far off from: “libfoo switched to being developed using emacs instead of vim so we can’t trust it anymore” It’s not the same obviously, but here’s why I can’t help but view it analogously: Th
118.
by pizlonator 5mo ago
This is true. But why I’m saying has always been true. What has changed is that the effective portability of C and C++ code has increased due to the reduction in number of compilers and arches
119.
by pizlonator 5mo ago
The problem is incorrectly assuming that the spec is meaningful in some kind of rigorous way. It’s not. All that matters is what C compilers actually do and what real C programs expect. This is a good thing. It creates a culture where the t
120.
by pizlonator 5mo ago
You’d have to teach rust about Fil-C pointers and their special rules. You’d also have to teach the rust compiler to play nice with the Fil-C GC. It would be a big change. Probably not backwards compatible with today’s rust.

More ›