miki_oomiri
Joined 2 years ago
Joined 2 years ago
Use that script as a super linter.
That’s the only way I found to strictly enforce some rules, like the no comments rule, without enforcing them against my own changes or old code.
It can be mitigated, a bit, but I don't see how browsers can win that battle.
Finger printing is a lost battle in my opinion, unless we drastically reduce what a web engine can do (like Tor does).
You people are gross.
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.
To me, be the best solution would be semantic + keyword + silence.
Hey Agent, blablablabla, thank you.
Hey Agent, blablablabla, please.
Hey Agent, blablablabla, oops cancel.
Openclaw is so so so much more.
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.
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".
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, …)
Don't gatekeep.