https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • f
    Oh yeah I love ajax 😂

    https://cdn.discordapp.com/attachments/725789747212976259/1111223893823344640/image.pngâ–¾

  • t
    It took htmx for me to understand what went wrong in web development over the last 15+ years. The thing that was communicated from the server to the client was moved to the client at cost of having to make more requests to the server. The last column doesn't exist yet (I hope!), but that's the meme part of it.

    https://cdn.discordapp.com/attachments/725789747212976259/1111242142598299648/image.pngâ–¾

  • s
    It is kinda hard for security reasons.
  • s
    Not a good idea to store sensitive data on the client side.
  • s
    This is why of you do SPA with a frontend framework you usually get duplication of code for data validation.
  • t
    yeah, but consider storing a user's sensitive data in 
    localStorage
    only and have the Server only temporarily holding on to data for manual syncronization of clients. It could be a DailyWTF, but it would also satisfy EUs GDPR.
  • s
    The more you put things on the client side the harder you make development.
  • s
    The more you keep them on the server the easier it gets. Of course there are no ideal states but...
  • b
    Last column: PouchDB
  • t
    They should have named it OuchDB. smh
  • t
    So, now that everything can be on the client, you can compile it and ship it as an .exe file. Right? (Electron enters the rooms)
  • s
    Mmmyea . And you are back to Desktop apps from the 90's I guess
  • s
    But with limited access to the os
  • b
    PouchDB is a good option if you need offline-first.
  • b
    I think the issue is keeping client and server in sync. Fat-server or fat-client are both okay
  • b
    But React-to-JSON is not fat-client. That’s straddling the fence, which gets painful before long
  • t
    which would be beautiful. Maybe we get full circle once languages like zig and odin get more popular and fewer people learn programming with javascript because they are scared of C/C++.
  • s
    "Beauty is in the eye of the beholder"... there's a ton of extra complexity with versioning and debugging apps that run on a machine that's not yours
  • s
    I am biased of course... I prefer web apps.
  • s
    There is a clear problem with webapps for me tho.. you can't own a copy of a webapp. That part is tragic. You can still install a virtualized copy on windows 98 and play your favorite game from a CD image.. but you cannot run a website you visited in 1999 because you can't have a copy of it.... kinda sad and frustrating at the same time
  • a
    https://htmx.org/essays/when-to-use-hypermedia/#hypermedia-not-a-good-fit-if is this essay based on individual components of the page rather than as usage of it part of a stack to actually develop an application?
  • a
    i can't actually imagine a full application running on this approach with most tasks.. some client-side is almost always there. For the best experience of course.
  • b
    Lmao
  • b
    Well, I will be wearing it with pride.
  • a
    the manner the essay is presenting hypermedia i cant help but be left utterly confused in regards to the upsides and negatives. and another question i'd have is there an example of a application that does mix approaches w/ transitional style
  • w
    The docs are a little unclear on this, but am I correct that it's okay to only set 
    hx-preserve
    on the response HTML? (e.g., the attribute isn't required on both the existing element and the response element that shares an 
    id
    with the existing element) Doc line in question: "The response requires an element with the same id, but its type and other attributes are ignored."
  • a
    i can't unfortunately imagine a clean way of mixing both despite the advantages, i really would love to see an example or perhaps a reliable solution one can leverage
  • s
    How to embed htmx into react? For example react needs to open a modal, but modal is written in htmx.
  • r
    I imagine, one would call htmx.processNode() from within react component. As long as htmx doesn't swap into elements, controlled by react VDOM, it would probably work fine. Although I would rather have small, self-contained react components inside htmx-powered page instead of embedding htmx into react
  • g
    although the suggestion was originally to keep them separate, i.e. htmx for most things and islands of React where you need high level of client-side interactivity
1...114011411142...1146Latest