Hacker News new | ask | show | jobs
by iuvcaw 525 days ago
Right… I think HTMX is cool and would like to try it. But the argument that “we need to go back to when things were simpler” just falls so flat to me. I remember the Web 20 years ago. It was pretty bad and ugly and slow and clunky and unintuitive.

We’ve made a lot of progress since then thanks in part to the powerful front-end state management and rendering solutions that are now standard. And if the argument is “we don’t need all that, I prefer simpler web pages…” then I just think you may have a totally different preference set from the average user. Normal non-engineers like sleek modern interfaces, not Web 1.0 forms and links and reloads

2 comments

20 years ago we were using the likes of PHP4 or Classic ASP or perhaps Perl for server-side languages. Possibly the early days of VB.NET (ASP.NET) being a thing.

Some sites created 20 years ago were still not making use of AJAX, either. If they were, in very specific ways. It is more likely to be using IFRAMEs back then to achieve partial refresh.

Today, the difference is that we still apply "the old ways" building websites but with modern languages + htmx. This is the difference.

When I look at websites I have created or inherited, all I see if bloat crossing between code written on the server-side... and code on the client-side. The further back in time I go the more it was server-side but, as mentioned, begin to lack the AJAX side of it.

Personally, I prefer to be back to the vast majority being server-side code. Sure, the amount of Views (and Partial Views) on my backend codebase is much higher than before but it is still organised code and testable without even using a browser. I then let htmx do the magic onto the webpage.

I have success stories but I also mock some things I did in the past but with htmx and it is very promising!

Sure I am still using Javascript but it is not ready about the data anymore - mostly additional libraries used for better drop down features or other cosmetics/UI things.

EDIT - ADDED: It is worth noting that the last 20 years, despite various javascript frameworks from React to Angular to knockout to jQuery to MooTools, etc..... we also had Flash and Silverlight and other things. We also have HTML5, CSS3, etc.

I have tried many things in the last 20 years. I also accept that htmx, while my goto choice for todays web development... is not going to be the best choice in my future.

Web Assembly (WASM) is going to get better and more popular. It will not be about HTML coding like today or even javascript in many ways. They will still be there, of course.

(Javascript will always be there but its use will get smaller and smaller)

As someone else wrote: we have apps and not websites now and if you look at what was named "HTML5" it is basically a software platform where you can run applications on. It really is client application development today, html is just the UI lanuage for historic reasons, but even that is no longer true in all cases (I'm thinking of Flutter or Compose). So, maybe even HTML is not that relevant in many cases.
> we have apps and not websites now

Is it too out there to say that we have both, and that's not a bad thing?