yeargun
Joined 3 years ago
Joined 3 years ago
I don't like Browsers to go CISC way. Simpler -> finer ?
Why?
Any feature that we add up indeed cause some extra CPU cycle. I am not a believer that we need an extra regex like this.
Of course, the overhead caused by this is minimal, so is the benefit. Also very tiny percent of web apps will use this anyways.
It could make the shipped css/js to some extent.
Overal I don't like this tradeoff. I dont want web to have more fanout
And overall one of the exciting part for me is, to be able to have composable & editable images, hopefuly generated by future genAI models.
And finally, I just realy wanted to rant over what a 'digital image' is
.hmml might be more hassle free then zip options for web apps. With zips, I think it will require more js bundle & processing to work.
meanwhile with .hmml, its already gzip/br compressed in cdns, and decoded natively by the browser
thats why .hmml is a packing strategy to mitigate that, single pack
1- html/css has more layout capabilities. 2- js 3- its a packing strategy. If you plan to serve images + svgs altogether, either you need to base64 encode or pack like hmml, binary