Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
WebCodecs is missing. They say it's "worth prototyping" [1] but I don't know whether they are working on it.
1: https://mozilla.github.io/standards-positions/
As I understand it, Web Codecs is quite a ways away from being a web standard - it is currently just a draft[1] for a recommendation for a possible future standard.
Just beware of any major API changes or any indication that it might be dropped in its entirety!
[1]:https://w3c.github.io/webcodecs/
> It almost always makes more sense to build for a single browser first, then figure out where the comparability issues are once you have an actual product.
I agree, and most places I've worked with has been the same. But I think only once, after following that process, have we ended up in "Damn, this works 100% in Chrome but is completely broken in Firefox". Sometimes something works faster/slower in Chrome/Firefox, but without requiring something like the Web MIDI API, most things just works the same across browsers, minus some minor things regarding CSS that has to be taken into consideration.
I guess what I'm looking for with my previous comment, is not so much of a general/philosophical answer of "Why you block Firefox but not Chrome?" but rather a specific answer to "What ended up being broken in Firefox but working in Chrome?"
Mostly helpful for my own curiosity, but in the strange case of finding things that works in Chrome but not Firefox, leaving a report at https://webcompat.com/ can be very helpful for the general health of the web as well.
LosslessCut is my go to for that sort of thing
https://github.com/mifi/lossless-cut
https://caniuse.com/?search=worker%20module
This is something I just personally bumped into in switching from webpack to vite (svelte app).
Not often that FF is the problem. Usually it's Safari but that is becoming less common.