I found that helpful for a question but the btw query seemed to go to a subagent that couldn't interrupt or direct the main one. So it really was just for informational questions, not "hey what if we did x instead of y?"
Yesterday it was showing a hint in the corner to use "/btw" but when I first tried it I got this same error. About ten minutes later (?) I noticed it was still showing the same hint in the corner, so I tried it again and it worked. Seemed to be treated as a one-off question which doesn't alter the course of whatever it was already working on.
It's not really the same use case. It's a smaller model, it doesn't have tools, it can't investigate, etc. The only thing it can do is answer questions about whatever is in the current context.
> The authors find that height cannot, in fact, be used to predict changes in GDP. However, GDP can be used to predict changes in height. In other words, the study finds that extreme height is driven by rapid economic growth, but that height cannot be used as an indicator of recessions
Now if they'd just release an update to 26.3.1 (23D8133) which PERMANENTLY broke Apple Carplay for me I'd be happy.
It's been getting steadily worse since iOS 26 was released.
Apple is rapidly becoming the new Microsoft. I mean, Microsoft has fallen so much further, so I guess that just opened up a new gap in the shitty technology spectrum for Apple to descend to.
The web part is the security model and the tradeoffs between security and performance. PNaCL was in browsers but not "web" for this reason.
Like the assembly part means low-level and meant as a compilation target, not CPU instructions.
So websssembly is an assembly language for the web, like webgl is opengl for the web and webgpu are gpu APIs for the web. And behold none of those can access DOM APIs
> So webassembly is an assembly language for the web.
But is isn't, at most WAT is (the WASM text format). WASM itself is a bytecode format. Nobody calls CPU machine code 'assembly' (nitpicking, I know, but the 'web' part of the name makes a lot more sense than the 'assembly' part).
At least the 'web' part makes more sense than the 'assembly' part ;)
WASM was designed as a successor to asm.js, and asm.js was purely a web thing. While non-web-platforms were considered as a potential use case (in the sense of "using WASM outside the web should be possible", it wasn't clear at the time what the successful usages outside browsers would even look like).
It definitly had to do everything with Web, it was the agreement between Mozila going with asm.js, Chrome pushing for PNaCL, Adobe with CrossBridge, Sun with Java, Microsoft with ActiveX,....
Then some folks rediscovered UNCOL from 1958, all the systems influenced by it, and started to sell the dream of the bytecode that was going to save the world.
This is retconning the history of WASM. While WASM was designed to be also be usable outside browsers, nobody could really predict at the time what this usage would look like exactly.
This brings back fond memories of my first job real job in IT, as the sysadmin for a small boutique mom-n-pop ISP. This was dialup/ISDN days though (back in the late 90's).
I appreciate the compliment. I wish this type of knowledge was more easily available for the general public since it represents an integral part of modern day internet. A comment on this thread mentioned other similar ongoing project which I'm very happy about and excited to explore.
Im fine with this, in 99.999% of cases anyway I'm way too lazy to type something into an LLM and ask it to clean it up and then copy and paste. You can tell this is true by the some of the stupider things I type in here sometimes.
Most "artisanal" coders that are complaining are working on the n-1000th text editor, todo list manager, toy programming language or web framework that nobody needs, not doing "true innovation".
reply