11–20 of 131 posts
Because the rest of the commentors in this thread seem to not be reading the article, there's a performance issue in Firefox due to the following unresolved bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1190398
> Unfortunately, Mozilla still hasn't fixed the performance bug 1190398 around ShadowBlur, filled for BLCK4777 5 years ago
> Therefore you need to use a Chromium or Webkit browser to enjoy MONOSPACE live
It was hard to get to a working demo and here it is: http://www.p01.org/MONOSPACE/monospace-compatible.htm
I expected the video to explain what it was but alas no. The video is just the demo running. The demo was brilliant, but, the video of the demo, although practically the same had me wondering quite negative thoughts. I wasn't thinking 'how do they do that', I was thinking 'this is a bit pretentious'. It is amazing the difference context makes.
Because the rest of the commentors in this thread seem to not be reading the article, there's a performance issue in Firefox due to the following unresolved bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1190398
The link to the demo comes before the warning to firefox, don't shame commenters who chose to see the content at discussion first before reading below the fold.
It was hard to get to a working demo and here it is: http://www.p01.org/MONOSPACE/monospace-compatible.htm
Even as a Firefox-user, I would recommend running this in Chrome. It's clearly optimized for that target, and it's getting a much higher FPS in Chrome than Firefox.
It completely locked up Firefox on Ubuntu 20.04, rendering a frame and making a single beep sound about once per second. Had to close the browser and force kill some processes to get the TTS to stop.