The information is well thought out and relevant but I have mixed feelings about the envelope its delivered in.
https://projectbluefin.io scrolls in a really really janky way specifically on mobile firefox. It seems to work correctly on desktop firefox, and mobile chrome. It probably performs poorly in other low resource environments as well.
Even on a desktop browser its easy to stimulate noticeable CPU usage merely by scrolling and almost 400MB of RAM usage explicitly and only for this tab.
Using the 3G profile in firefox dev tools it takes over 40 seconds to load. What is remarkable is how long it took to actually load while only in fact transferring 5MB which is much slower than one would expect even when throttled to 750Kbps.
Even at the DSL profile (2Mbps) its a fairly shockingly slow 16s to load.
Incidentally 2.6 of the 5 is just a png file that could easily be reduced to ~900k without noticeable degradation.
Compare that to the linked blog post which scrolls normally without noticeable CPU usage, loads almost instantly while progressively loading the images and uses about 80MB of RAM.
I must say I love how it looks but it is a triumph of form over function that probably works only if most prospective users are viewing this on fast devices with a fast connection. Bounce rate for websites goes up enormously as one goes over 3-4 seconds.
If your website needs a loading screen and its not a desktop app running in a browser window stop whatever you are doing and throw it away and rethink it.
One could argue that the information page you're profiling is designed for maximum attention grabbing, and is for an OS that is based on containers, development, and a combination of the two. If you're primarily a kuberbetes dev interested in working and reproducing locally, you probably have the resources on your machine to render this smoothly and properly. And have a fast enough connection to make the bandwidth claims negligible.
In that way, I guess it's good gatekeeping for who and what should run Bluefin. I recently learned this myself after installing Bluefin DX on both a low resource machine and my main dev box.
Protip: probably should be used only on your main dev box at the moment
It's a web page. It's not even a web app its just scrollable text interspersed with video and links. You don't really have to "optimize" it to not hit the CPU on a 6 core desktop computer, use 400MB of RAM, or lag on a phone. It's not a technical trade off its just 5 minute job that probably should have been a 15 minute job.
Comments
The information is well thought out and relevant but I have mixed feelings about the envelope its delivered in.
https://projectbluefin.io scrolls in a really really janky way specifically on mobile firefox. It seems to work correctly on desktop firefox, and mobile chrome. It probably performs poorly in other low resource environments as well.
Even on a desktop browser its easy to stimulate noticeable CPU usage merely by scrolling and almost 400MB of RAM usage explicitly and only for this tab.
Using the 3G profile in firefox dev tools it takes over 40 seconds to load. What is remarkable is how long it took to actually load while only in fact transferring 5MB which is much slower than one would expect even when throttled to 750Kbps.
Even at the DSL profile (2Mbps) its a fairly shockingly slow 16s to load.
Incidentally 2.6 of the 5 is just a png file that could easily be reduced to ~900k without noticeable degradation.
Compare that to the linked blog post which scrolls normally without noticeable CPU usage, loads almost instantly while progressively loading the images and uses about 80MB of RAM.
I must say I love how it looks but it is a triumph of form over function that probably works only if most prospective users are viewing this on fast devices with a fast connection. Bounce rate for websites goes up enormously as one goes over 3-4 seconds.
If your website needs a loading screen and its not a desktop app running in a browser window stop whatever you are doing and throw it away and rethink it.
One could argue that the information page you're profiling is designed for maximum attention grabbing, and is for an OS that is based on containers, development, and a combination of the two. If you're primarily a kuberbetes dev interested in working and reproducing locally, you probably have the resources on your machine to render this smoothly and properly. And have a fast enough connection to make the bandwidth claims negligible. In that way, I guess it's good gatekeeping for who and what should run Bluefin. I recently learned this myself after installing Bluefin DX on both a low resource machine and my main dev box. Protip: probably should be used only on your main dev box at the moment
It's a web page. It's not even a web app its just scrollable text interspersed with video and links. You don't really have to "optimize" it to not hit the CPU on a 6 core desktop computer, use 400MB of RAM, or lag on a phone. It's not a technical trade off its just 5 minute job that probably should have been a 15 minute job.