71–79 of 79 posts
I've been working on a framework for a while. It's a server side VDOM that streams updates to a small JS runtime. Components are written in Haml. https://github.com/mayu-live/framework
Been a few years since I tried Rails (I don't do much web development), but seriously considering giving it another try. I do wonder if a "Lite" version of Rails could happen somehow - DHH was talking about JSON APIs in his latest blog post, and indeed they are more no-ops than an SQL database. I have tried Ruby CGI but very barebones - no MVC. I haven't tried Sinatra, but someone at a Ruby web development company to…
I've used Sinatra plenty of times but only used as a backend api, no frontend rendering.
I've been working on a framework for a while. It's a server side VDOM that streams updates to a small JS runtime. Components are written in Haml. https://github.com/mayu-live/framework
That's so cool! Makes me happy seeing HTTP/2 being suppport as well.
Earlier quoted context omitted.
That's so cool! Makes me happy seeing HTTP/2 being suppport as well.
Thank you! HTTP/2 is great. It's really convenient to have one connection per client.
Turns out, Rails is a really good web framework! I tried building Sitepress on something “light weight”, Tilt and Rack, and it was a pain. I found myself constantly solving the same problems that were already solved in Rails. At some point it dawned on me that I could just build on top of a few parts of Rails, so I did. I wrote about it at https://fly.io/ruby-dispatch/single-file-rails-app/
I’m glad I did! Now I can plug all of the Rails template handlers, view components, and other Rails plugins into it and ride off that entire community’s docs.
If you find yourself thinking, “rails is too heavy”, consider shedding the parts of Rails that you don’t need. Then as your application grows in complexity and you find yourself needing more parts of Rails, bring it back in.
Earlier quoted context omitted.
Thank you! HTTP/2 is great. It's really convenient to have one connection per client.
Any thoughts or plans about HTTP/3 in Ruby? I've been searching around and it's dead silent within the community, only seen a presentation about implementing QUIC in Ruby using Ractors but nothing more.
I'm using the async-http gem for the HTTP/2 server and it works great for my use case.