5 ms·
On a side note, if your fan started spinning up when you opened this, it's because of the particle simulation in the header. I know because I reviewed this lib
by mediumdeviation 9y ago
On a side note, if your fan started spinning up when you opened this, it's because of the particle simulation in the header.
I know because I reviewed this library (https://github.com/VincentGarreau/particles.js https://github.com/VincentGarreau/particles.js) when a colleague wanted to add something similar to our site. The problem is it uses a naive O(n^2) algorithm for linking up particles when they get near each other, which wastes a lot of CPU cycles.
Running this script with a large number of particles and auto-linking on is ill-advised - but fortunately you can delete the <canvas> element quite easily to stop the script.
- dave5104 9y agoI also noticed they have some janky Javascript playing with the scrolling on the page, which also prevents me from using swipes to go back in my browser. Very annoying when sites mess with that. Give me my usual scrolling inertia!
- balgan 9y agoThanks for this info, I've asked the guys to try and fix this! Apologies in advance!
- fny 9y agoWow... I was about to use this on a landing page I'm building. Thanks for the tip!
- nikkettt 9y agoI just did! Annoying the I had to reduce the number of particles significantly in order not to force CPU to spark. Does anyone have suggestions for an alternative library? (I really don't want to have to write something like this myself for a landing page, talk about overkill)