News for hackers. Stuff that matters.
Re:Chrome intends to remove XSLT from the HTML spec by _ache_ on Tuesday August 19, 2025 @12:09PM (#44953180)
I get the point a minimal browser and WASM, but Java bytecode ?! Why not Python bytecode ? Seems unreasonable to me to add any specific bytecode support. By layout rules you mean get rid of CSS ? Sounds also unreasonable IMHO.

And no WebAudio and Canvas couldn't be implemented in client WASM without big security implication. If by module you mean inside the browser, them, what is the point of WASM here ?

Re:Chrome intends to remove XSLT from the HTML spec by codedokode on Tuesday August 19, 2025 @12:21PM (#44953308)
What WebAudio needs to provide is only means to get or push buffers from/to audio devices and run code in high priority thread. There is no need for browser to provide implementation of low-pass filters, audio proccessing graphs and similar primitives.
Re:Chrome intends to remove XSLT from the HTML spec by bigstrat2003 on Tuesday August 19, 2025 @12:39PM (#44953488)
Honestly, even WASM makes it not very minimal in my book. A minimal browser should be HTML and perhaps a subset of CSS, that's it.