4 ms·
Lets be clear here. They were only tested on some developer's fast machine on Chrome. All the users are going to be using it on some bag of shit $300 laptop run
by wrldos 4y ago
Lets be clear here. They were only tested on some developer's fast machine on Chrome. All the users are going to be using it on some bag of shit $300 laptop running crapware infested Edge so they will be suffering like your Firefox users are.
The problem is the left hand side of the chain. Stop pulling in thousand layer garbage abstractions and making the user pay the penalty for it.
- cleanchit 4y agoAll web developers should be required by law to work on 4gb 3ghz laptops with a 3G mobile connection.
- madeofpalk 4y agoNo, Firefox just flat out has some worse JavaScript performance and bugs/incompatibility with other browsers. I’ve been/am currently burned by Firefox’s pretty poor IndexedDB support and performance. IDBObjectStore.getAll() fails with a cryptic exception if you store too much in IndexedDB (iirc 256mb is the limit), whereas Chrome and Safari have no problem with it. It also has terrible performance - about 4x slower than Chrome, with Safari having the best performance.
- wrldos 4y agoThat's a microscopic problem in a macroscopic ocean of shit.
- deleted 4y ago[deleted]