I think it is why they have gone with AssemblyScript as the main supported language. Since it is similar to Typescript, Web developers will likely have a easier time learning it.

It’s mainly about the runtime (lack of it) that language brings, ie. garbage collected language brings garbage collector runtime with it that has to be included with every binary. Even rust and c have (relatively thin) runtimes. AssemblyScript has optional/controllable very thin runtime.

What their decision means in practice is that you can execute any language if you want but they won’t expose any specific runtimes to thin your binary. They will also actively support workflows based on AssemblyScript.

Yes but then you have to buy cartridges from the manufacturer who has the control to say there are empty when in fact they are not. It is a completely closed ecosystem. I believe customers deserve better alternatives.

For many brands you can easily buy off-brand cartridges, and nowadays quite a few sell printers that work of ink tanks and don't even have cartridges.

Just ask your local refill shop what printer to buy so you don't have to go through this. That's what I did when I last bought a printer.

There's a very lively market of refilled / aftermarket cartriges which lowers the incentive to fix these issues.

I think this is mostly to give teams with smaller budgets a fighting chance against teams like say Mercedes who have an astronomical budget and could finance R&D all year long.

Have you heard about Weld[1] ?

It is an ongoing effort to built an intermediary representation that numerical library could share to produce an optimized instructions tree.

[1] https://github.com/weld-project/weld

I use it on mobile. Almost the same experience as chrome but with ad-blocking and anti-tracking enabled. However, i still use Firefox on PC.