3 ms·

I agree. For example, the Dutch corona dashboard (coronadashboard.rijksoverheid.nl) is a statically rendered dashboard using Next that gets updated daily. No ba

by mmcnl 5y ago

I agree. For example, the Dutch corona dashboard (coronadashboard.rijksoverheid.nl) is a statically rendered dashboard using Next that gets updated daily. No backend and it's super fast. Maybe I'm not objective because I'm Dutch myself, but from both a user-facing and technical perspective I think the Dutch dashboard is by far the best corona dashboard in the world. It's very fast, has a lot of detailed visualizations, provides a lot of context and has fair amount of accessibility features.

xbar 5y ago
Is there a dashboard of dashboards somewhere?
codefined 5y ago
Looking at the Dutch site on my phone (Samsung S10) I noticed it took a little while to load compared to the nigh instant loading of the UK Gov variant. Looking at Page Insights [0] [1] tells a similar picture. Desktop time to interactive times of 0.4s Vs 3.5s and Mobile time to interactive times of 4.5s Vs 13.1s. The Dutch website seems to spend a lot of that time running the Next JS framework stuff, which the Gov.uk variant does not. It might work quickly on fast computers, but even on modern phones it seems to visibly pause.
- mmcnl 5y ago
  On my iPhone Xr, older than S10, it loads very fast. Also performance depends on which page you benchmark. Landing page is faster for UK, but the cases pages is about twice as fast for the NL dashboard (time to interactive 2.4s for NL vs 4.4s for UK). Also first meaningful paint is faster (0.5s vs 0.8s). This proves that you can get decent performance without an overly bloated costly architecture.
Accacin 5y ago
I'd say that using Next for a static site is just as over engineered, personally.
- mmcnl 5y ago
  I disagree. Expressing your frontend layout as code is not over engineering at all imo. It makes it easier to re-use code and is great for testability. Next is perfect for this use case. I actually think the code is quite elegant too. It's open source, so don't take my word for it, but have a look for yourself: https://github.com/minvws/nl-covid19-data-dashboard/tree/develop/packages/app https://github.com/minvws/nl-covid19-data-dashboard/tree/dev....
  - dwohnitmok 5y ago
    > Expressing your frontend layout as code is not over engineering at all imo What do you mean by this? Isn't all frontend layout expressed as code?
    - mmcnl 5y ago
      HTML is not code imo. With React (and thus Next) you can treat your frontend code as full-fledged functions and objects.
tinus_hn 5y ago
It looks really nice. Unfortunately it turns out the main feature, the data, is phony. https://dvhn.nl/groningen/Meer-ziekenhuispati%C3%ABnten-blijken-corona-te-hebben-27402652.html https://dvhn.nl/groningen/Meer-ziekenhuispati%C3%ABnten-blij... When the hospitals feel like it, they test patients that are already in the hospital for something else if they have COVID. And when they don’t feel like it, they don’t. Any patient found to have COVID, is added to the graph. So these numbers, and also derived numbers such as the R value, are statistically useless and vulnerable to manipulation.

by mmcnl 5y ago

xbar 5y ago

Is there a dashboard of dashboards somewhere?

codefined 5y ago

Looking at the Dutch site on my phone (Samsung S10) I noticed it took a little while to load compared to the nigh instant loading of the UK Gov variant. Looking at Page Insights [0] [1] tells a similar picture. Desktop time to interactive times of 0.4s Vs 3.5s and Mobile time to interactive times of 4.5s Vs 13.1s. The Dutch website seems to spend a lot of that time running the Next JS framework stuff, which the Gov.uk variant does not. It might work quickly on fast computers, but even on modern phones it seems to visibly pause.

mmcnl 5y ago
On my iPhone Xr, older than S10, it loads very fast. Also performance depends on which page you benchmark. Landing page is faster for UK, but the cases pages is about twice as fast for the NL dashboard (time to interactive 2.4s for NL vs 4.4s for UK). Also first meaningful paint is faster (0.5s vs 0.8s). This proves that you can get decent performance without an overly bloated costly architecture.

Accacin 5y ago

I'd say that using Next for a static site is just as over engineered, personally.

mmcnl 5y ago
I disagree. Expressing your frontend layout as code is not over engineering at all imo. It makes it easier to re-use code and is great for testability. Next is perfect for this use case. I actually think the code is quite elegant too. It's open source, so don't take my word for it, but have a look for yourself: https://github.com/minvws/nl-covid19-data-dashboard/tree/develop/packages/app https://github.com/minvws/nl-covid19-data-dashboard/tree/dev....
- dwohnitmok 5y ago
  > Expressing your frontend layout as code is not over engineering at all imo What do you mean by this? Isn't all frontend layout expressed as code?
  - mmcnl 5y ago
    HTML is not code imo. With React (and thus Next) you can treat your frontend code as full-fledged functions and objects.

tinus_hn 5y ago

It looks really nice. Unfortunately it turns out the main feature, the data, is phony. https://dvhn.nl/groningen/Meer-ziekenhuispati%C3%ABnten-blijken-corona-te-hebben-27402652.html https://dvhn.nl/groningen/Meer-ziekenhuispati%C3%ABnten-blij... When the hospitals feel like it, they test patients that are already in the hospital for something else if they have COVID. And when they don’t feel like it, they don’t. Any patient found to have COVID, is added to the graph. So these numbers, and also derived numbers such as the R value, are statistically useless and vulnerable to manipulation.