Live data from Hacker News

The Return of the 90s Web

mxb.dev

1–10 of 357 posts

Re: The Return of the 90s Web

#3
Preloading on button-down, nice detail optimization. It's possible that you have to abort that request, but it will be the rare exception. It's my favorite thing I learned today.

Re: The Return of the 90s Web

#4
post #2

Webflow is touted as "the new Dreamweaver". Of course, it's "software as a service", about 3x as expensive as basic web hosting.

> about 3x as expensive as basic web hosting.

Good, that's a bargain IMO. I get way more than 3x the value out of webflow than I do "basic web hosting".

Re: The Return of the 90s Web

#5
I recently watched the "Helvetica" documentary that was posted here a few days ago [0], where they briefly mention "Grunge Typography" [1], a seemingly dead-end branch of typography that, for some strange reason, became pretty popular for a short period of time.

After some years however, consensus amongst designers formed that what they've created was a pile of illegible garbage, and realized that there was no other way than completely dismiss that branch, go back to the roots, and evolve from a few steps back.

I feel the same kind of consensus is slowly forming around ideas like SPAs, client-side rendering and things like CSS-in-JS.

We saw the same happen with NoSQL and many other ideas before that.

We recently deployed an entire SaaS only using server-side rendering and htmx [2] to give it an SPA-like feel and immediate interactivity where needed. It was a pleasure to develop, it's snappy and we could actually rely on the Browser doing the heavy lifting for things like history, middle click, and not break stuff. I personally highly recommend it and see myself using this approach in many upcoming projects.

[0] https://www.hustwit.com/helvetica/

[1] https://www.theawl.com/2012/08/the-rise-and-fall-of-grunge-t...

[2] https://htmx.org/ (formerly "Intercooler")

Re: The Return of the 90s Web

#8
I really like the turbolinks approach - you simply write HTML and then include the script in your head tags. However, I'm still hooked on Markdown. So I am still prerendering HTML - and then doing the routing with Hyperapp. (See https://href.cool/Tapes/Africa for an example - you get a prerendered static HTML page, but it uses JavaScript from there to render the other pages.)

The ultimate approach is Beaker Browser though. You can actually just write your whole site in Markdown (/index.md, /posts/batman-review.md, /posts/covid-resources.md) and then write a nice wrapper for them at /.ui/ui.html. This means you can edit posts with the built-in editor - and people can 'view source' to see your original Markdown! It's like going beyond the 90s on an alternate timeline.

(A sample of this is this wiki: hyper://1c6d8c9e2bca71b63f5219d668b0886e4ee2814a818ad1ea179632f419ed29c4/. Hit the 'Editor' button to see the Markdown source.)

Re: The Return of the 90s Web

#9
Maybe I'm missing something, the article isn't very clear. One of the reasons why we have front end apps pulling from an API is because it allows for interoperability.

The same API that serves data to the web browser can serve that data to mobile apps and to third parties as well.

The idea of bringing HTML rendering back on to the server just doesn't seem useful to me.

Re: The Return of the 90s Web

#10

I recently watched the "Helvetica" documentary that was posted here a few days ago [0], where they briefly mention "Grunge Typography" [1], a seemingly dead-end branch of typography that, for some strange reason, became pretty popular for a short period of time. After some years however, consensus amongst designers formed that what they've created was a pile of illegible garbage, and realized that there was no other…

I have fond memories of creating images with Grunge fonts in some pirated copy of Photoshop and then positioning them with HTML tables and Dreamweaver.
Post reply on HN