3 ms·
rails, postgres, PORO, and htmx is a monstrously productive stack
by arkis22 4y ago
rails, postgres, PORO, and htmx is a monstrously productive stack
- iamgopal 4y agoAny examples?
- arkis22 4y agoyou're looking for what? my personal million dollar website or my billion dollar startup?
- boredtofears 4y agojust any evidence to back up your argument
- arkis22 4y agojust my years of experience, sorry
- ithrow 4y agoIf you are one Rails, why not the hotwire stuff?
- arkis22 4y agohttps://github.com/hotwired/hotwire-rails https://github.com/hotwired/hotwire-rails deprecated. they use stimulus and its worse obfuscated JS than htmx IMO
- Lio 4y agoPersonal opinion, if I was going to use htmx with a PORO backend I'd probably go for Roda[1] and Sequel[2]. If it was going to be read heavy I think I'd also pair that with SQLite for low latency and cheaper deployments. If I didn't know exactly how requirements are likely to change over time I'd probably go with with Rails, Postgres[2], Redis and Hotwire. You can go a long way with that and a small team. 1. https://roda.jeremyevans.net/index.html https://roda.jeremyevans.net/index.html 2. https://sequel.jeremyevans.net/ https://sequel.jeremyevans.net/
- aaron_m04 4y agoWhat is PORO?
- arkis22 4y agoplain old ruby object. basically you take your truth from the database and you plug it into an object that takes the data and functionally produces a data output that you feed to your view.