This has me thinking of Python's NoGIL movement.
Bun has an open PR adding shared-memory threads to JavaScriptCore
91–100 of 330 posts
Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#92Earlier quoted context omitted.
Just stop caring about quality. It makes it 10x easier to produce slop with AI if you never bother to check
It is sad. This is a new reality. No one reads code, it is agents all the way down. It has been long enough now that I can safely say AI has not sped up project delivery nor improved quality when it did ship. Is it the AI or the people using it? Idk
It is sad. This is a new reality. No one reads machine code, it is compilers all the way down. It has been long enough now that I can safely say C has not sped up project delivery nor improved quality when it did ship.
Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#93Earlier quoted context omitted.
Yeah I don’t get that either It’s a super successful language
I think with ES6 and newer things really cleaned up and now we’re left with avoidable ugly parts, of which every language has. Before when you didn’t even have strict equality checking, for example, you were forced to know about implicit type casting. Getting on the same page with modules also helped a lot. Typescript directly in Node is great. Look mom, no build system!! I’m just hoping one day browsers will accept…
You still need a compiler for TSX, though. There's also a tiny bit of non-erasable Typescript (enums).
Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#94I knew it was possible :-) https://webkit.org/blog/7846/concurrent-javascript-it-can-wo...
It’s certainly possible, but I worry that weird things can happen when doing something as “simple” as defining a property if another thread is messing with the prototype chain. Even thread safe property maps can’t entirely save you because operations that need to go up the prototype chain are not and cannot be atomic.
This won’t work well without a few other things, like structs
Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#95Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#96Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#97For what it's worth: this isn't a PR on mainline WebKit. The PR is on bun's own fork of WebKit (and JSC), which already has a bunch of their own changes.
Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#98Earlier quoted context omitted.
I think with ES6 and newer things really cleaned up and now we’re left with avoidable ugly parts, of which every language has. Before when you didn’t even have strict equality checking, for example, you were forced to know about implicit type casting. Getting on the same page with modules also helped a lot. Typescript directly in Node is great. Look mom, no build system!! I’m just hoping one day browsers will accept…
You still need a compiler for TSX, though. There's also a tiny bit of non-erasable Typescript (enums).
There’s a mode to pretend those features don’t exist and not allow them. Meaning it gets far simpler to just type elide rather than any actual compilation effort. I think this idea is getting more popular and it would be kinda nice if TS committed to not adding any more features like that.
Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#99Earlier quoted context omitted.
I think it's also worth distinguishing _problem complexity_ and _solution complexity_. The problem might be really really hard (and it very obviously is in the case of adding multi-threading to JavaScript). But it does not mean that the solution has to be hard to understand. It doesn't mean that any average PHP developer (I can say that, I started with PHP) should be able to verify the correctness of the patch, but f…
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
I think you're underselling your own level of intelligence Fil. If even you would be confused by an implementation (and you're the author of the concept) what chances do you think this PR has to actually work correctly?
Re: Bun has an open PR adding shared-memory threads to JavaScriptCore
#100I wonder if I'm the only one for whom the bun project vanished completely. In software code is only part of the package. Stability and trust are big part of it, too. And for me 1800 files change PRs created by Anthropic overseen by one person is not necessarily adding to the package. Even it that'd be the best code and design in the world, I won't use it. I don't trust it.
Yeah, I have prepared our company software for migration back to node.
I would like to read the promised Jarred's blog post (if it ever comes out) before pulling the plug though.