Comment Hurry before they savage a great browser! (Score 1) 77
Quick, stop Firefox auto-updating before they crack the AI into it, turning it into a useless product.
1) Firefox handles memory better than ANY other browser. Try putting 4000 rows by 200 columns into https://jacobsm.com/browtest3.... and see if your browser can handle it.
2) Firefox can loop WAV files perfectly using its HTML5 AUDIO tag. Check out some of the loops at the top of https://jacobsm.com/mjmidi.htm . All other browsers have a gap at the loop point, whereas only Firefox is seamless.
Both the desktop and the Android versions of the Firefox browser can do the 2 points above. That's why it needs to be preserved - it's unique in the field. It's not perfect - look at how they handle HTML INPUT LISTs, but it's the best of the bunch overall, IMO.
BTW, the large table came about from a real world example where we have to produce a vast data dump every day for one of our clients - as they crept past 2000 records, we started getting problems with Chrome producing the file. I found the memory problem, reported it to the brick wall known at the Chromium bug report facility, and have heard nothing since. Switched to Firefox and no more memory problems.
1) Firefox handles memory better than ANY other browser. Try putting 4000 rows by 200 columns into https://jacobsm.com/browtest3.... and see if your browser can handle it.
2) Firefox can loop WAV files perfectly using its HTML5 AUDIO tag. Check out some of the loops at the top of https://jacobsm.com/mjmidi.htm . All other browsers have a gap at the loop point, whereas only Firefox is seamless.
Both the desktop and the Android versions of the Firefox browser can do the 2 points above. That's why it needs to be preserved - it's unique in the field. It's not perfect - look at how they handle HTML INPUT LISTs, but it's the best of the bunch overall, IMO.
BTW, the large table came about from a real world example where we have to produce a vast data dump every day for one of our clients - as they crept past 2000 records, we started getting problems with Chrome producing the file. I found the memory problem, reported it to the brick wall known at the Chromium bug report facility, and have heard nothing since. Switched to Firefox and no more memory problems.