https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • a
    just saw this at a training at work 😭
  • r
    Hello friends, are there examples of large projects implemented with htmx that I can share with my team?
  • g
    :>
  • a
    they mention the right source (Roy Fielding's dissertation), but follow the industry standard of stopping at level 2
  • a
    just resource naming and verbs usage
  • m
    the entire htmx discord rn (rn)
  • m
  • m
  • m
    We need to collect more
  • m
    JetBrains is sponsoring the project, if that helps
  • m
    🙂
  • a
    oh, hey, at least the are including hyperlinks on the response
  • r
    thank you!
  • m
    I sense the use of this meme in your future
  • a
    The course has a discussion forum... tempted to drop it there
  • a
    re the reaction of all this on reddit and other communities, think that to some people this might come as "these folks are proposing an architecture that would made all my time and effort to learn X SPA framework(s) go puff" So no surprise many get horrified about it and react against it.
  • m
    🙂
  • m
    There are a lot of interesting aspects of how REST has turned out, mostly non-technical.
  • m
    "The comedy of man survives the tragedy of man"
  • a
    it's something I'm already thinking about, for all the frontend only developers on my team. Just saying "well, now stick to HTML/CSS/minimum JS, the backend will do the heavy lifting" might sound rough.
  • a
    unless you can convert them to do also backend development
  • l
    I almost posted about this in here a while back, but I have a small Vue app in production right now. Part of me wants to make v3 of that app (currently in the queue) be all htmx - but another part of me thinks it may be wise to have a foot in both worlds. FWIW, Vue is my absolute favorite of any of the SPA frameworks I've tried (and I've tried a bunch); hated the idea of v3, then moved my app to it and now can't believe they didn't do it that way from the beginning. Still, though, it's really overkill for what that site does.
  • m
    there is no shame in using vue or react, that's where the money is
  • m
    you aren't going to pay rent with being right about HATEOAS
  • l
    Let them develop the front end in the back end! LOL (that's the sentiment, in part, around which the Liquid template language was built)
  • l
    Unless the "proof-of-concept" I've mentioned in here is received favorably - in which case htmx will be used at a.... uh, major nation aviation-based defense agency. If that happens, I will quite literally be making my mortgage payment with a salary gained through using htmx. (Though I will have had to go through Ember 0.12 to get there... LOL)
  • a
    yeah, just need to be careful so that they don't feel like their impact/contribution to projects gets diminished
  • a
    that said, I have the honor of being paid to develop at least one app with htmx. Hopefully more to come.
  • l
    And yes, it's probably not wise to disrupt the course for which your employer has likely paid good money. At least it will give your team a shared understanding so you can contrast JSON-RPC with actual REST / htmx.
  • a
    my experience is that many of our apps (we develop internal apps) don't need to be SPAs
1...753754755...1146Latest