Man… you guys are ruthless. The dude provides a free tool to use, and used a cute named, have opinions about code, and used the most common used photo on his webpage, and suddenly he gets insulted on a public forum by strangers. He's not perfect. Nobody is. He has opinions, and might not even know about Lenna.
I've created an iCloud account for my llm.
On my Mac, I created another user account, not an admin, just regular. Linked to the iCloud account. Installed Bluebubble.
And now I can chat with my AI via iMessage, via my Apple watch, or my homepods. It works beautifully.
When I speak to an agent, siri, or whatnot, I am always worried that they will assume I'm done talking when I'm thinking. Sometimes I need a many-seconds pause. Even maybe a minute… For Sire and such, I want to ask something simple "Hey Siri, remind me to call dad tomorrow". Easy. But for Claude and such, I want to go on a long monolog (20s, a minute, multi-minutes).
To me, be the best solution would be semantic + keyword + silence.
All I can tell you with certainty is that the people who designed and funded webgl/asmjs/llvm efforts at Mozilla (Alon, Vlad, Brendan, …) clearly understood that wasm was a needed companion alongside JS (and its DOM&co bindings). Not a replacement. I was part of these conversations.
I understand why people would think it was a JS killer, but that's a naive way of looking at it.
> The whole "it's not meant to replace JS" thing was just to reduce pushback from JS devs.
It was born at the same time as webgl, at the time of Jit optimisation for js engines. As a subset of js first, then as wasm as we know it. It was originally for games and performance on the web.
At no point there was a conversation about "replacing js", but more like, "js can't do these stuff. let's have something else".
You have the wrong understanding about wasm. It's absolutely not supposed to be replacing HTML, CSS or JS.
And yes wasm is used wildly. On the web for expensive computation (Google earth, figma, autocad, unity games) or server side for portability and sandboxing (Cloudflare workers, fastly, …)
I'd very curious to know how they managed to deal with this then. There's always the option of embedding quickjs-vm within the addon (as a wasm module), but that would not allow the executed code to access the document.
- focus 100% on Firefox Desktop & Mobile
- just a fast solid minimalist browser (no AI, no BS)
- other features should be addons
- privacy centric
- builtin, first-class, adblocker
- run on donations
- partner with Kagi
- layoff 80% of the non-tech employees
I worked for them for many years, I guarantee you that Mozilla will be fine without all the non-sense people, just put engineers in charge.