3 ms·

I'm so sick of people complaning about "reinventing the wheel". Even for the literal wheel, I can think of at least 3 times off the top of my head that it was u

I'm so sick of people complaning about "reinventing the wheel". Even for the literal wheel, I can think of at least 3 times off the top of my head that it was usefully reinvented in just the last 20 years. There is nothing that is perfect for all use cases. People who say "don't reinvent the wheel" should come up with something new to say. But they can't, because they hate innovation so much.

nsonha 3y ago
You are right and I was wrong, reinventing the wheel is the least harmful thing of the like of htmlx. The actual dumb thing is that they cling on to a fundamentally wrong abstraction to build apps (form method), simply because that’s the web they’re familiar with.
- basique 3y ago
  Why is it a wrong abstraction?
  - nsonha 3y ago
    It assumes a lot of things: - Submitting a form results in an immediate network request (offline-first apps, hello?) - The network event is HTTP-based - The network event is REST - The payload is contained within the... markup (like why?) - What about network requests that are not CRUD? If your API is designed propperly, that should be most of the endpoints. Do you make dummy forms for them? How?
    - basique 3y ago
      The point of htmx is to be able to do the interactivity on the server, so using it with your existing, general API isn't really the point - the backend (or, well, frontend backend?) just serves the needed data directly in the markup. This isn't really ideal if you think of your site as a separate frontend/backend, but it makes sense if you already have a backend and don't want to make an API just to then write JS that consumes the API and shows you stuff. Granted, this doesn't really work well with offline-first apps, but it's nice if you need to actually poke the server whenever you need to do something.

3 ms·

I'm so sick of people complaning about "reinventing the wheel". Even for the literal wheel, I can think of at least 3 times off the top of my head that it was u

by moron4hire 3y ago

nsonha 3y ago
You are right and I was wrong, reinventing the wheel is the least harmful thing of the like of htmlx. The actual dumb thing is that they cling on to a fundamentally wrong abstraction to build apps (form method), simply because that’s the web they’re familiar with.
- basique 3y ago
  Why is it a wrong abstraction?
  - nsonha 3y ago
    It assumes a lot of things: - Submitting a form results in an immediate network request (offline-first apps, hello?) - The network event is HTTP-based - The network event is REST - The payload is contained within the... markup (like why?) - What about network requests that are not CRUD? If your API is designed propperly, that should be most of the endpoints. Do you make dummy forms for them? How?
    - basique 3y ago
      The point of htmx is to be able to do the interactivity on the server, so using it with your existing, general API isn't really the point - the backend (or, well, frontend backend?) just serves the needed data directly in the markup. This isn't really ideal if you think of your site as a separate frontend/backend, but it makes sense if you already have a backend and don't want to make an API just to then write JS that consumes the API and shows you stuff. Granted, this doesn't really work well with offline-first apps, but it's nice if you need to actually poke the server whenever you need to do something.