5 ms·

It's great that these examples have been collected in one place, but it's an incredible leap to call this a spiritual successor to TodoMVC. Fundamentally, ever

It's great that these examples have been collected in one place, but it's an incredible leap to call this a spiritual successor to TodoMVC. Fundamentally, every implementation is different at a UI level. They all have different designs, some have custom fonts. Some go directly to the Firebase source, whilst others go via an intermediate API. The scores that are being listed are affected by too many variables beyond the UI library for them to mean anything at all. In addition, a spiritual successor to TodoMVC is going to have to reflect actual upcoming patterns in user interfaces. Things like shared element transitions, sound effects, perhaps some 3D effects, and numerous other things. Most HN clones don't even allow write operations, even TodoMVC has that.

danabramov 9y ago
Not only that, but they are also served differently. For example, the React example has an "F" grade for static caching, whereas some other examples have "A". Doesn't sound like something a JavaScript library can influence. Why is it that way? Because these are just sample projects from different people created at different points in time, served on different hosts, but suddenly brought under a single umbrella as if it was an organized project from the beginning. There are big differences in build systems, e.g. some examples are optimized by hand to inline critical CSS at the build level, others aren't. There's nothing that prevents applying the same strategies to all examples, but the fact is some example authors had time to do it, and others didn't. Wouldn't it make sense to at least use the same build system for Preact and React examples? I appreciate the effort by Addy and other folks from Google to highlight performance issues in web apps, but as it stands right now I consider the website to be rather misleading.
thekingshorses 9y ago
Exactly. They are not comparing apples to apples. Firebase API has gotten slower over the years. That affects Interactive time and lighthouse score. Preact HN uses their own servers, and React HN uses the Firebase API. Also, some passes site is progressively enhanced check because some elements are rendered without JS. Which results in higher score. Preact HN loads offline but without content. Lighthouse assumes that app works offline, but in reality app is useless without actual stories. I use Firebase API in my web app (https://hn.premii.com/ https://hn.premii.com/) and scrap YC in my downloadable app (https://hn.premii.com/about/ https://hn.premii.com/about/). Both has different actual and perceived performance. Write operations are not possible with HN clones as there are no YC apis. They should build reddit clone. I have build reddit clone https://reddit.premii.com/ https://reddit.premii.com/ using their official APIs.

danabramov 9y ago

Not only that, but they are also served differently. For example, the React example has an "F" grade for static caching, whereas some other examples have "A". Doesn't sound like something a JavaScript library can influence. Why is it that way? Because these are just sample projects from different people created at different points in time, served on different hosts, but suddenly brought under a single umbrella as if it was an organized project from the beginning. There are big differences in build systems, e.g. some examples are optimized by hand to inline critical CSS at the build level, others aren't. There's nothing that prevents applying the same strategies to all examples, but the fact is some example authors had time to do it, and others didn't. Wouldn't it make sense to at least use the same build system for Preact and React examples? I appreciate the effort by Addy and other folks from Google to highlight performance issues in web apps, but as it stands right now I consider the website to be rather misleading.

thekingshorses 9y ago

Exactly. They are not comparing apples to apples. Firebase API has gotten slower over the years. That affects Interactive time and lighthouse score. Preact HN uses their own servers, and React HN uses the Firebase API. Also, some passes site is progressively enhanced check because some elements are rendered without JS. Which results in higher score. Preact HN loads offline but without content. Lighthouse assumes that app works offline, but in reality app is useless without actual stories. I use Firebase API in my web app (https://hn.premii.com/ https://hn.premii.com/) and scrap YC in my downloadable app (https://hn.premii.com/about/ https://hn.premii.com/about/). Both has different actual and perceived performance. Write operations are not possible with HN clones as there are no YC apis. They should build reddit clone. I have build reddit clone https://reddit.premii.com/ https://reddit.premii.com/ using their official APIs.