4 ms·

I had not previously heard of Htmx but this looks neat. My favorite part about Vue is it’s templating system so it feels just like supercharged html. Htmx remin

I had not previously heard of Htmx but this looks neat. My favorite part about Vue is it’s templating system so it feels just like supercharged html. Htmx reminds me of that, but seems to be nice combined with some other templating system like ERB. I’d love to try this out in a rails app to see how I like it compared to a separate JavaScript front and and rails in api mode!

lordgroff 6y ago
Web dev is not my daily job but I maintain my wife's e-commerce store on the side. I've brushed up enough with react and vue to know their idioms, and I agree with you, and this is why I tend to reach for vue if I can use it. It reminds me of the "old" template system, but better because components are much nicer than the spaghetti you could find yourself in with template inheritance. The state tracking is also simple, and while I understand many find this aspect of vue "simplistic" I have never hit a serious limitation for my limited use cases. So what about htmx? Well, I've tried to like it, but the thing is I could not figure out how to track state server side without quickly devolving into jquery like spaghetti of "this has to update, but also this if that but not if also this, and I need to trigger X if Y". I might be missing the correct pattern in using it, but in the mean time I've gone back to Laravel blade templates (which I rather like for its component system, taking in the best idea from front end) together with vue inspired Alpine JS.
- e67f70028a46fba 6y ago
  It’s a mindset change. With htmx you should start with the entire body updating and then scale down to achieve the ux you want, rather than thinking in terms of individual components updating. The htmx merge algorithm is pretty good and you often don’t need to target small parts of the ui.
- mritchie712 6y ago
  Curious, why doesn't she use Shopify?
  - lordgroff 6y ago
    Because it's very expensive, she requires a fair amount of customization due to the type of business that would put the price really through the roof, and she has free labour in the form of her husband :)
    - whycombagator 6y ago
      How expensive would it be? Unless your wife's store is incredibly low volume or has a thin profit margin I don't see how Shopify would be too expensive to justify given the benefit it would bring over a home-grown solution. And honestly, as I consumer I vastly prefer ordering direct from merchants who use Shopify or a similar platform. The entire experience is just extremely polished. That being said, did you build the entire thing yourself or are you using one of the many open source options out there like WooCommerce/Prestashop/Nopcommerce/Magento?
      - lordgroff 6y ago
        I'm using woocommerce with a bunch of home built extras. As for the expense: there's no comparison, we crunched the numbers. The problem is also there's a bunch of custom functionality needed and Shopify plugins do not cut it. Neither do woocommerce ones, for that matter, but I can code them up easily enough.

lordgroff 6y ago

Web dev is not my daily job but I maintain my wife's e-commerce store on the side. I've brushed up enough with react and vue to know their idioms, and I agree with you, and this is why I tend to reach for vue if I can use it. It reminds me of the "old" template system, but better because components are much nicer than the spaghetti you could find yourself in with template inheritance. The state tracking is also simple, and while I understand many find this aspect of vue "simplistic" I have never hit a serious limitation for my limited use cases. So what about htmx? Well, I've tried to like it, but the thing is I could not figure out how to track state server side without quickly devolving into jquery like spaghetti of "this has to update, but also this if that but not if also this, and I need to trigger X if Y". I might be missing the correct pattern in using it, but in the mean time I've gone back to Laravel blade templates (which I rather like for its component system, taking in the best idea from front end) together with vue inspired Alpine JS.

e67f70028a46fba 6y ago
It’s a mindset change. With htmx you should start with the entire body updating and then scale down to achieve the ux you want, rather than thinking in terms of individual components updating. The htmx merge algorithm is pretty good and you often don’t need to target small parts of the ui.
mritchie712 6y ago
Curious, why doesn't she use Shopify?
- lordgroff 6y ago
  Because it's very expensive, she requires a fair amount of customization due to the type of business that would put the price really through the roof, and she has free labour in the form of her husband :)
  - whycombagator 6y ago
    How expensive would it be? Unless your wife's store is incredibly low volume or has a thin profit margin I don't see how Shopify would be too expensive to justify given the benefit it would bring over a home-grown solution. And honestly, as I consumer I vastly prefer ordering direct from merchants who use Shopify or a similar platform. The entire experience is just extremely polished. That being said, did you build the entire thing yourself or are you using one of the many open source options out there like WooCommerce/Prestashop/Nopcommerce/Magento?
    - lordgroff 6y ago
      I'm using woocommerce with a bunch of home built extras. As for the expense: there's no comparison, we crunched the numbers. The problem is also there's a bunch of custom functionality needed and Shopify plugins do not cut it. Neither do woocommerce ones, for that matter, but I can code them up easily enough.