This was the major roadblock for WebGL2 acceptance of developpers looking to support all major browsers.
This was the major roadblock for WebGL2 acceptance of developpers looking to support all major browsers.
I once (4 years ago, sheesh) made a "Pure-JS, no-build-step-required Minecraft Thing": https://github.com/mrspeaker/webgl2-voxels
When I made it I needed to specify it "Requires ES6 modules and WebGL2 support." At the time I was sure WebGL2 was going to be widely available soon and that ES6 modules would probably never be supported!
For me, google.com is 1.47MB. It makes you wonder what they put inside.
Didn't you mean "an alternative to Google?"
Don't blame the tool for the (lack of) craftsmanship.
We are using a WebGl plugin and recently it broke on Safari, we had to detect this new Safari version and downgrade the users to a 2D mode (it was a third party plugin so I can't debug it)
Latest Safari cannot be used by users who cannot run the latest MacOS on their hardware, or have reasons not to (such as bricking risk with latest MacOS on old hardware.)
(I imagine it's similar with iOS but I'm not sure.)
https://en.wikipedia.org/wiki/Safari_(web_browser)#Safari_15
This is part of the problem with the world of computing today. When a software released not quite 2 years and 4 months ago is referred to with the phrase "all the way back". Don't get me wrong, I'm all for keeping things as up-to-date as is reasonable, but the industry has far too much churn in many areas.
(That version range still seems quite restrictive though.)
The iPhone 6s was released in 2015 yet can run the latest version of iOS released in 2021. It probably won't be able to run the 2022 version of iOS but at that point it will have been seven years. I'm sure Android can't be updated for that long, I don't know if a current browser for Android can be run on a seven year old version of Android.
EDIT: Chrome 98 also works on Android 6.
Yes it can - pretty sure my daughter's old Mac running Mojave got an update to the newest Safari a few days ago.
Does anyone know where these performance differences stem from?