geckoview VS caniuse

Warning, I don't really know what I am talking about on this subject. But that said! I believe the replacement is GeckoView

I stand by what I said - their code is a convulated mess by design. It's 25 years and they still haven't modularised their code that anyone can use the Gecko engine on the desktop and creating competing browsers. All anyone can do is create a clone of Firefox, which ofcourse, cannot really compete with Firefox or other desktop browser as it will still have all the flaws of Firefox. And this is what Mozilla wants.

They may have started with altruistic reasons, but after tasting Google's money, their greed corrupted them.

Mobile is a good example. Mozilla realised it was in a precarious position on the mobile platform, which is dominated by Chrome, Opera and Safari. And so they have now been forced to release the Gecko rendering engine for mobile ( https://github.com/mozilla/geckoview ) and are encouraging others to create mobile browsers, in the hopes that this may provide a fillip to Mobile Firefox. Desperation drove them to this move as the money is now in mobile platform (Google paying 15 billion dollars to Apple / Safari highlights this).

If they can do this for the mobile platform, why can't they do it for the Desktop platform too?

This kind of deliberate convulated code mess is like a "dark pattern" where in you know the developer isn't really interested in supporting the open source movement. Yes, there are many other open source projects that have poor code or lack documentation, but unlike the Firefox project, none of them has 100's of millions of dollars at their disposal - it's a travesty how they have wasted all that money!

Can I X, is a question about the readiness/compliance of a certain thing at time = now. Can I use CSS version X was the iconic early meme.

https://caniuse.com/?search=css3

For a generalized example, if you wanted to know if the basketball courts were ready for you to “ball it up” in a certain city, it’d be caniball.com

If you want to know if you can use a certain frontend technology, the idea is like: canwefigma?

It’s a glorified feature matrix, and usually a project of a passionate community. I approve, even if some of the memes are a bit dank.

https://caniuse.com/ is a popular tool to check what web features are working across different browsers - "can you use this and assume that it will work for others".

The article uses custom css @properties which are awesome and have 88% browser support [1].

One thing to watch out for is differences in how browsers handle setting the fallback initial-value. Chrome will use initial-value if CSS variable is undefined OR set to an invalid value. Firefox will only use initial-value if the variable is undefined. For most projects, this won't be an issue, but for a recent project, I ended up needing to use javascript to set default values in Firefox to iron out the inconsistency between browser implementations.

[1] https://caniuse.com/?search=%40property

Safari is the only browser that doesn't support extending HTML element

https://caniuse.com/?search=Custom%20Elements

You forgot to mention (Web)Workers. This is explicit creation, management, and communication with additional threads within JavaScript. What's more, they've been around in JavaScript longer than the V8 engine has even existed!

https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers...

https://caniuse.com/?search=webworkers

Do you happen to know where can I check out the cutoff version for each browser? https://caniuse.com/?search=wasm doesn't have it (or other things like WasmGC for that matter)

(https://caniuse.com/) A handy tool for checking the browser compatibility of HTML, CSS, and JavaScript features. Can I Use provides up-to-date support tables for various web technologies across different browsers.

Caniuse