xen-orchestra VS bad-apple-css

I am working on xen orchestra https://github.com/vatesfr/xen-orchestra and some of the task are pretty intensive We try to offload the worst one to background process ,or at least cut it in chunk to avoid hogging the event loop

Feature: Have a dark theme for the UI · Issue #5335 · vatesfr/xen-orchestra · GitHub

Code

The full Bad Apple!! PV in about 232MB of pure CSS without any JavaScript and almost no HTML. Uses JavaScript and builds upon the awesome open-source projects FFmpeg, node-potrace, node-worker-threads-pool, their dependencies and btoa (see the attribution.txt in the repository for details). Inspired by Junferno's "Bad Apple!! played with pure CSS in high quality". Compared to his approach, this one is pure CSS, has cleaner edges, no flicker, character shadow color, which is closer to the original, and is responsive to page resizes. (Please correct me, if Junferno's is, too.) However, I might have had an advantage being able to load larger stylesheets and my version has issues with rendering the first second after the inital page load and sometimes stutters briefly. (I wanted to see whether someone can come up with something smarter to solve the loading issue than just adding a few seconds of a blank screen in the beginning, so I left this low hanging fruit in.) Also I think that Junfero's approach is more interesting than basically just applying Potracer. Source code is here: https://github.com/luisscholl/bad-apple-css