Show HN: Trends – A GitHub trending PWA | Hacker News Reader

Show HN: Trends – A GitHub trending PWA

95 pointsjack_hanford33 comments

Over the past few weeks I've been working on a small application to view trending repos on GitHub. I built the PWA[1] with React, Next.js and GraphQL .. but what's interesting is the application is only using React server side, meaning the client side javascript is only a few lines code adding some event listeners and registering a service worker for offline capability. This helped me achieve a perfect google chrome performance audit

I learned a ton working on it and would love to talk about it if anyone has any questions!

Application Link: https://trends.now.sh

Source code on Github: https://github.com/hanford/trends

[1]: https://developers.google.com/web/progressive-web-apps/

View on HN

I'm super intrigued by the client-side/server-side rendering question. When I discovered single page apps I thought I'd seen the future - servers were just things that hosted web services, and all the presentation was a bundled, minimized blob served up by a static CDN. So simple, so clean, such clear separation of concerns. But now I'm seeing reports of faster first page rendering with React server than React client, and here I'm seeing a clearly very smart person articulating a completely different class of benefit of server-side rendering. Clearly I shouldn't be walking away from old style server side rendering so casually. My question is how do you think about that choice, now that we have the freedom to go either direction?

It's certainly interesting. This kind of development has gone full circle where the methodologies are back to where it was years ago.

The issues that really large JS bundles can cause are really hard to solve (bloated sizes, but also parse time of the bundles). There are a lot of tools to help mitigate those like code splitting, but it's really challenging once things get big.

When I wanted to achieve a 100 in my chrome performance audit, I simply couldn't include React.

I think React adds a tremendous amount of value from the ecosystem, the constant improvements and updates .. and the mindset that developers have when building out react applications. (component model, etc)

I think for any really large application with lots of client side interactions or async data / data management, my solution would become unwieldy.

But for smaller applications that maybe don't need to do as much, (in the above case we're simply registering some event listeners to submit a form) or landing pages or the like .. the above solution would work very well.

The community has done a "full circle" but we came out on top a thousand times better.

We can now do server side rendering while also booting up a complex JS app on top of it.

It is definitely the foreseeable future.

The page load speed is seriously impressive, congrats!

There's something weird going on with the styling of the dropdowns, though: https://i.imgur.com/WQ3m52X.gif

I'm on Windows 10 & Chrome

> The page load speed is seriously impressive, congrats!

I happened to see this before I clicked the link, and I have to agree the page load speed lives up to your hype!

I'm not experiencing your issue on OS X, Chrome.

On a similar note, it'd be nice if there were an arrow indicating it was a dropdown in the first place.

just rolled out a fix for this on firefox for mac, i don't have a windows computer to test the fix on...

if you do a hard refresh this issue may be resolved! ¯\_(ツ)_/¯

Dropdown arrow still does not show in Windows 10 with Chrome v. 68.0.3440.75 [1]

Same with Microsoft Edge 42.17134.1.0

Works OK on Firefox 61.0.1 (64-bit) [2]

[1] https://imgur.com/a/e9pw5Ii [2] https://screenshots.firefox.com/iv6SFyfw29zh91WG/trends.now....

Yep, works well now.

I'm having the same issue in OSX firefox.

May need to do a hard refresh because of the aggressive caching, but this should be fixed now!