Earlier quoted context omitted.
intel i9-9900 3.60GHz, 32GB DDR4 RAM, and a 6TB 7200RPM SATA HDD running manjaro
No SSD?
No
What will a Chromium-only Web look like?
351–356 of 356 posts
Re: What will a Chromium-only Web look like?
#352Earlier quoted context omitted.
QuickJS (and various others) demonstrates that small teams can create fast and efficient JavaScript engines that comply with standards. Even though v8 is faster, it spends an order of magnitude more engineering effort for that marginal benefit.
A Javascript engine is pretty far from a browser. It's too much work to write a browser even if you reuse the existing V8.
I agree. The context of this comment is the user asking if Web assembly will make that effort easier. I don't think it will since getting good JS is already reasonable.
Re: What will a Chromium-only Web look like?
#353Earlier quoted context omitted.
No it's not. The Atari isn't one year old. Come on man, from your logic you might as well say that a one year old car should be fed hay since it's practically a horse.
Debian stable is using components often several years old, not just a year.
Some parts of the system evolve faster than others. I am glad for Debian's relatively conservative policy for all my servers, but I want an evergreen browser on my desktop.
Re: What will a Chromium-only Web look like?
#354I’m a little surprised why Chinese firms aren’t coming in and competing? Maybe they think web is not important for their future anymore?
Why bother when you can simply rebrand Chromium?
Re: What will a Chromium-only Web look like?
#355Earlier quoted context omitted.
A Javascript engine is pretty far from a browser. It's too much work to write a browser even if you reuse the existing V8.
I agree. The context of this comment is the user asking if Web assembly will make that effort easier. I don't think it will since getting good JS is already reasonable.
Yeah, it won't be the wasm itself that makes anything possible.
What might happen is that it ushers in technically-unrelated fashions, such as standard WASI interfaces to something slightly less insane than DOM+Javascript.
Just Canvas-over-WASI isn't the answer because of accessibility, but something like it might happen.
Re: What will a Chromium-only Web look like?
#356Earlier quoted context omitted.
> The only reason they disallow Chromium and Mozilla is they want their users locked into their environment and they want to leverage that substantial locked-in user base to dictate terms That's one reason, but not the only reason. Security is another big one in that the WebKit process is running with privileges that Apple does not want to award to any other app process on the platform, much less a third-party one. T…
battery life is another stated reason I believe.
I can slip one line of code into a modern website that'll target a particular iphone model and run its battery to nothing in half an hour, and probably crash safari as well. Any language is susceptible to badly written or malicious code. At least with Flash it was in a box, in a virtual machine, and you had to approve it and could kill it at any time.