I also think the process explanation was very enjoyable.
In the end, it was a static page that handled an incredible amount of traffic.
It works - i can pop out sites that work in a mall amount of time. They will never be istheshipstillstuck.com-famous or cnn.com-loaded, or never be used in some countries where loading 10 MB of JS is a problem.
they are used by me, on my 1000/400 Mbps connection, or by my children on a LAN.
So having a hammer that works-sort-of-always-but-not-optimal is better than having a stupendous ultra-refined tool that is the exact fit for the work - but requires 100 hours to learn and 430 pages of docs translated by Google from Swahili to French.
The web platform itself is a framework that consumes static HTML and CSS and calls into your JS. Preferring a higher-level framework for web apps when that is available is no different than preferring a higher level language even though ASM is available for local apps.
cd hello
quasar dev
→ I have a page and a dev server
After adding a few lines I have the components all in the right place.
quasar build
→ I have my static page
One line changed, I have a PWA
I will not do a PhD in development, I need to have simple reactive apps quickly.
Of course I could have use HTML/CSS/JS and write everything from scratch (been there, done that). Of course they will load 2 x faster, so I will not have to wait the 200 ms I do now.
Development today is so much easier. When I started 30 years ago it was truly an adventure. Today my children are coding simple stuff after one afternoon of showing them.
So yay to the frameworks, modules and others things that help people who just wish to build something fast.
Have you ever bought furniture or do you start by taking your axe and visiting the nearest forest?
In no way am I saying the only reason for learning is business—there's plenty of intrinsic value. But all that learning has to subsidized with something...
From a business perspective, there's a good chance there's more than a handful of earning opportunities right under each of our very noses every day. The key is to find the ones that align with our strengths, personalities, skillsets, etc...
Using code to generate static sites is not new or particularly interesting. We have been caching PHP and Perl sites so that they are "static" since the dawn of the web. CDNs are really really old now. It feels like a new batch of developers don't know that caching is a thing and "static" is a hot buzzword.
> In my day job, we use Next.js for almost everything we build. It’s a framework built on top of React that just strips out almost all the complexity of building fairly complicated websites. Obviously, this wasn’t a complicated website, but I went with what I’m most familiar with.
When you have a hammer, everything looks like a nail :D
Edit to say that I think it's an amazing little wholesome project and the author's very funny. Didn't want my comment to sound too harsh. :)