pouët.net

Go to bottom

PNG packed js demos don't work now on chrome

category: general [glöplog]
12 years to break or 12 years to notice? :)
added on the 2022-02-23 16:38:14 by Gargaj Gargaj
That is a deeply philosophical question.
added on the 2022-02-23 16:41:30 by sagacity sagacity
If it is broken, but nobody notices, is it then broken?
added on the 2022-02-23 17:18:49 by Moerder Moerder
makes u think
added on the 2022-02-24 11:25:55 by sagacity sagacity
This optimization has been known as "name mangling" in the js world (see jsexe --mangling).
It is really an extreme optimization, because at compression time, you have to choose the exact list of existing browser versions which will be supported.
The reason is that each browser canvas implementation (webGL or 2D) has its own list of methods, in different order, which potentially cause different hash collisions.
I think it is even OS specific, i.e. the same browser version can have different canvas interfaces on two different OS.
As said, not really recommended to build timeproof demos...
added on the 2022-03-02 09:07:32 by cb cb
This is somthing that I have been discussing with some chums today. The typical competition criteria values rank: that prioritizes instaneous presentation over all else. YouTube allows us to relive that instant.

The software engineer in me is uncomfortable with this optimization criteria. I am happy to grind that persona into the dirt as I work on our next prod.
added on the 2023-08-18 02:21:54 by ig0r ig0r
Fixed my 704.2 1k
Used the webgl function directly when collisions occurred, the problem was to get back that extra used space... works now :)
https://www.backtothepixel.com/demos/js/webgl/704webgl1k.html works here. Using Chrome Ver 126.0.6478.127 (64-bit) (its a bit older version). 128MB Intel UHD Graphics 770 GPU.
added on the 2025-11-17 19:39:39 by rudi rudi
What Moerder said ... I think that was proven in QI once
added on the 2025-11-19 15:38:13 by Steel Steel

login

Go to top