https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • f
    No framework is literally the most natural feeling, but because of the nature of our projects there has to be some sort of abstraction layer with templating.
  • f
    Isolated processes 🙏
  • r
    The only serious drawback with PHP that I'm experiencing - if your processes go over 0.1, 0.5 or even 1 second, you start running into scaling. Gotta keep latency low.
  • r
    But if you do, shit, PHP is fast now.
  • f
    Ironically, I've been maintaining and updating a homebrew legacy PHP4 framework (by ex dev) to 8.1 over time and it's one of the fastest things imagineable because it's so extremely close
  • f
    But it becomes an unmaintainable mess, hence the attempt
  • r
    Yeah. No other language or framework has had life like that. Dude, PHP is a sleeper language honestly.
  • r
    I have sites from 2010 that I still run thanks to PHP
  • f
    If anyone has suggestions for a PHP + HTMX framework approach I'm open for suggestions 😄
  • f
    oh well that's what #939530480636809227 is for
  • r
    Also PHP has had file based endpoints forever, as recently adopted by Next.js. Lol.
  • r
    People are realising it was more productive
  • r
    I mean it is what it is. I barely have to do maintenance on my PHP servers, yet my node, python, etc. projects all require intervention once in awhile.
  • r
    It's that process isolation dude, nothing kills it.
  • f
    die();
    does 😂
  • h
    I run an agency - keeping barrier to entry low is important, but assuming you're around for the long haul you are going to get a lot of opportunities to work with the same tooling in different situations which will lead to a lot of growth if you have a consistent team
  • h
    which will help with your ability to create templating/consistency across projects
  • h
    do you do mostly sass? CMS projects? brochureware?
  • f
    From enterprise-level web apps (international sample order system working with live API to multiple regional distributors) to simple questionnaire forms. We use CMS for specific requests like company brand websites. Sulu and Wordpress (😩) for example. Sulu is Symfony and works well in an agency context, however its scope most of the time is either over- or underqualified
  • a
    one of the best side effects of using htmx (and I would say also hyperscript) it that when looking how to do something you spend time on MDN reading about the HTML and HTTP standards instead of on some specific JS library documentation/forum that might be phased out in a few years
  • a
    that feels much better knowledge to solidify on the long term
  • g
    i think ive just discovered a bug in the 
    head-support
    extension but im having a hard time figuring out exactly im seeing...
    m
    • 2
    • 13
  • f
    You can always add more knowledge to the stack through additional technology if the project requires it, but the basics for a PHP+htmx approach would be "Do you know PHP? HTML? CSS? Alright you're hired."
  • r
    PHP never dies. htmx / intercooler never dies.
  • r
    That's a big factor I've been considering too lately. Pretty much the only rule about PHP is never block- and if you need to block, make it invoked by cron.
  • r
    PHP is dead easy to onboard compared to anything.
  • f
    Yes. Plus for example, we run an enterprise level web app that is entirely PHP + HTML + vanilla JS doing ajax calls to PHP + cron, it runs since 2011 and it still just works, the PHP upgrade process was so laughingly small (strict typing was the biggest issue here but nothing that couldn't be solved easily) and the app is just so much faster and responsive now.
  • r
    I will admit too, the most fun and rapid experience I've ever had in a dev job was a zero framework PHP stack. Deployments didn't even require rebooting a daemon or anything, git pull or copy the new scripts in. PHP will just hotload the new stuff in.
  • r
    It's been awhile, but I do remember it fondly.
  • f
    😌
1...910911912...1146Latest