ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Wednesday, April 8, 2026

  1. * nevet joined #primate
  2. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  3. * skillbot joined #primate
  4. bluedreamreal: I think you're misunderstanding something. htmx is just normal html that you serve alongside the htmx js. why should it hit SEO?
  5. blueyou haven't demonstrated what nextjs or primate gain you. my point is, nothing. have your static server (nginx or whatever) serve htmx views, interact with your api endpoint, and you get a MUCH cleaner architecture
  6. bluethis *is* literally the htmx use case -- it's why so much go projects use it, because they'd otherwise need to go through a JS server, which is what you're doing right now
  7. blueso many*
  8. blueone of the reasons I haven't bothered with a primate ui is I don't think it's the right solution for you. primate isn't a ui -- it's a full-stack framework that layering on top of spring is dumb
  9. * nevet joined #primate
  10. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  11. * nevet joined #primate
  12. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  13. * phaleth joined #primate
  14. * phaleth joined #primate
  15. bluehi phaleth
  16. phalethhi blue
  17. dreamrealphaleth: figured out the problem, for the record: it was docker misrepresenting the network addresses internally.
  18. bot<discord:phaleth> dreamreal: that's good
  19. dreamrealI may set up a test server here and work out podman deployment, to see if it's any different
  20. * blue joined #primate
  21. bluevps restarted... hm
  22. * jreicher joined #primate
  23. blueWB jreicher.
  24. jreicherAllo.