3 ms·
>sign in was broken on Firefox, but worked on Chrome-like browsers I've seen that, but it was related to hardware keys. If Firefox cannot be bothered to suppor
by panny 5y ago
>sign in was broken on Firefox, but worked on Chrome-like browsers
I've seen that, but it was related to hardware keys. If Firefox cannot be bothered to support keys, why should anyone be bothered by using it?
More importantly though, it seems like the whole world is in this mess, because browser developers develop monoliths. If the browsers were split into small reusable parts, any developer could assemble one, and there could be lots of competing parts. The number of available browsers would explode to infinity. Why is everything lumped under a single massive code base known as "Browser engine" like gecko or blink or whatever? Why do they keep making monoliths? There could be parser engine, css layout engine, svg render engine, etc etc etc. But there isn't, there's one giant lump, browser engine.
If anyone made a focused attempt at a new browser ecosystem, it seems like it should attack the glue layer between these disparate parts.