Live data from Hacker News

Websites have evolved back to static HTML/CSS/JS files

paramaggarwal.substack.com

61–70 of 313 posts

Re: Websites have evolved back to static HTML/CSS/JS files

#61
post #35

Earlier quoted context omitted.

> But Gmail showed us that web 'apps' are useful. Gmail is terrible. It's slow and most people prefer the static html version.

Somehow everyone I know is happy with GMail and find a full-featured email client incomprehensible. I can't stand GMail's slow UI.

I don’t understand how anybody can like gmail’s interface. It’s so convoluted and unintuitive.

Re: Websites have evolved back to static HTML/CSS/JS files

#63
We've been building Levels.fyi as a static website for the past 3 years! To create a new page, we simply hit new file on our text editor and start to fill the page. We have a simple build system + templating with Gulp and Nunjucks, but its really all we need.

Scaling a static site is incredibly nice & cheap too :P

Re: Websites have evolved back to static HTML/CSS/JS files

#64
post #38

Earlier quoted context omitted.

Would you pay their fee for generating the page on the server?

I do Netflix, Prime Video etc etc

That's paying for content, but isn't really what we're talking about.

Hacker News is a better example. It's generated entirely server-side. Why not pay YCombinator a few cents for every page load?

Re: Websites have evolved back to static HTML/CSS/JS files

#65
post #44

Earlier quoted context omitted.

It's better than everything else because people have never heard of it. When did software engineers become hipsters?

It seems like a lot of web devs are either stuck chasing novelty or constantly trying to bet on the next big thing. For example, what happened to CoffeeScript? https://trends.google.com/trends/explore?q=%2Fm%2F0hjc5m0&ge... What happened to Ember? https://trends.google.com/trends/explore?geo=US&q=%2Fm%2F0s8...

TypeScript ate coffeescript. That said it did inspire a lot of new features in both TypeScript and the ES standard.

Re: Websites have evolved back to static HTML/CSS/JS files

#66

No, the SPA hype has warn off and people realize that although these new technologies exist, they are not always needed. If you are building a web app, use React or similar. If you are building a web site, use plain HTML+CSS w/ supplemental JS. Sometimes your project can be split in half. Do the landing page, signup, login, privacy policy, etc. in plain HTML. Maybe don't embed all that stuff in your app and you would…

Preach. I teach a little "into to web dev" workshop that starts with a slide explaining that static sites, SSRs, and SPAs are all perfectly acceptable. They're different tools for different use cases.

Re: Websites have evolved back to static HTML/CSS/JS files

#67

This is something that I see espoused by "web traditionalists" for lack of a better term. Sure, there are a lot of web developers who are not optimising for performance but I think the difference is that it has simply shifted to the frontend where it's more noticeable. The kinds of people who care about performance in the backend are exactly like the kinds of people who care about performance in the frontend. There's…

SPAs being the darks ages is over-the-top, but being an SPA when other web architectures could better serve the user is a dark pattern . That tax app doesn't need to be an SPA. JavaScript powered interactions make the experience nicer for the user, but that doesn't mean it needs or is improved by being a single page.

"Single page" isn't the why it's the how. It enables you to take a JavaScript-first approach which in turn makes building complicated applications easier.

Re: Websites have evolved back to static HTML/CSS/JS files

#68
The leap from static HTML to PHP misses a big chunk of dynamic web site growth that started to produce a lot of the bad patterns that lived on.

As simple and nice as static HTML is, it's inefficient. The reason we care about this now is mostly:

A) A lot of people just hate Javascript. And a lot of that hate is understandable. B) People still worry about the crawlability of their SPAs

JS has a lot of problems but it's also fixing some of these by growing really fast (paradoxically, also one of its problems).

Bots will get more comprehensively better at rendering client-side only apps.

Re: Websites have evolved back to static HTML/CSS/JS files

#70

> The Dark Age - Somewhere on this path to render pages on the fly (SSR) and render pages on the client (SPA) we forgot about the performance of our webpages. We were trying to build apps. But the web is about presenting content first and foremost! Pfff - That's completely wrong. SPAs are all about performance. If you want to built a highly-interactive site, it makes sense to do the computing where it's consumed -- i…

> But Gmail showed us that web 'apps' are useful. Gmail is terrible. It's slow and most people prefer the static html version.

You've clearly not had to work in a corporate environment on an old PC with a locked down copy of Outlook...

Gawd.. now that's terrible.

But yeah... I don't agree Gmail is terrible, but I'd like it to be better.

Ive been on a few months after it launched, and got a service that's been reliable and stable for that long, I have to give it a lot of credit!

Post reply on HN