Email or username:

Password:

Forgot your password?
Top-level
Michael T. Bacon, Ph.D.

@futurebird I've seen multiple projects/blogs/manifestos now that are ranting against the nearly enforced ubiquity of single page applications (SPA) that are super-javascript heavy, with an emphasis towards getting back to semantic markup and CSS. It's not 1990s (I mean I love me some HTML 1.0 but I'm pretty alone in that) but it's much lower bandwidth.

Also very easy to do drafting in Markdown, which once you get used to it (and that doesn't take long) is totally addictive.

4 comments
Michael T. Bacon, Ph.D.

@futurebird But again, my ideal web aesthetic is more retro than even the Geocities nostalgic want. I'm skeptical of background images!!!

Veronica Olsen 🏳️‍🌈🇳🇴🌻

@MichaelTBacon I wouldn't count myself as one of those ranting against single page apps nor dynamic websites in general, but I do host both a personal and a project website that are static. The former is a blog and the latter is documentation mainly, so they are text-heavy. Static pages are better suited for both, and significantly less work to maintain. It's a logical choice.

I used to make a living building dynamic websites, so it's nice to be able to use my outdated skills. 😁

@futurebird

Michael T. Bacon, Ph.D.

@veronica @futurebird

Yeah the anti-SPA folks aren't totalizing about it, there are some pages for which SPAs are absolutely the right choice. But there's been a push over the last decade-plus to make everything everywhere a React or similar SPA, and it's led to a very sluggish web overall.

SPA where they're good, static/CSS-driven pages where they're not, is the goal here.

Go Up