Matestack: Rapidly create interactive UIs in Ruby
matestack.org
Matestack: Rapidly create interactive UIs in Ruby
1–10 of 42 posts
Re: Matestack: Rapidly create interactive UIs in Ruby
#2I don't really understand what are they fixing here. They point that current web development has shifted to "REST backend" and "SPA frontend", which (according to them) is not a good thing (why?). Their solution is to make you write (again) a "full" MVC-backend that also serves the UI (frontend), and additionally, extend it with another frontend layer (Vue).
IMHO that is not fixing the initial problem they are stating that exists, but making it worse, because now you have to write UI-related code in two languages (ruby and js) instead of the 1 that is currently needed (REST + SPA).
Re: Matestack: Rapidly create interactive UIs in Ruby
#3An API backend + UI front-end consuming it is the perfect solution, it is the only sane thing I ever came across. Stop trying so hard to shoehorn old bullshit over it. It took us decades to settle on this, please leave it be and focus on more pressing issues. World hunger or something.
Re: Matestack: Rapidly create interactive UIs in Ruby
#4Reminds me of inertia.js!
Re: Matestack: Rapidly create interactive UIs in Ruby
#5Core contributor here: Happy we made it to HN, maybe a notch too early :)
Right now there's only two not very supporting comments here. Glad the authors have solutions that work for them, but Rest + SPA is overly complicated for most small/mid sized projects in our opion.
Everyone else: Feel free to join our Gitter if you like what you see!
Re: Matestack: Rapidly create interactive UIs in Ruby
#6An API backend + UI front-end consuming it is the perfect solution, it is the only sane thing I ever came across. Stop trying so hard to shoehorn old bullshit over it. It took us decades to settle on this, please leave it be and focus on more pressing issues. World hunger or something.
It is completely unclear to me whether you are agreeing what Matestack does or not. It could be read as: "Yes exactly, this is what we need, not this other tech." or "What you have built is nonsense, please spend your time differently"
Also, it is completely unclear to me what 'old bullshit' is in your story. Is an API backend with UI front-end old or new? It could be read as that or as "API backend with JS front-end is the best, stop trying to push server-side rendered HTML on us."
Re: Matestack: Rapidly create interactive UIs in Ruby
#7Core contributor here: Happy we made it to HN, maybe a notch too early :) Right now there's only two not very supporting comments here. Glad the authors have solutions that work for them, but Rest + SPA is overly complicated for most small/mid sized projects in our opion. Everyone else: Feel free to join our Gitter if you like what you see!
Do I understand correctly in that you are generating Vue.js components from Ruby? If so, how is that less complicated and not like an SPA than simply rendering HTML with erb or slim?
Re: Matestack: Rapidly create interactive UIs in Ruby
#8An API backend + UI front-end consuming it is the perfect solution, it is the only sane thing I ever came across. Stop trying so hard to shoehorn old bullshit over it. It took us decades to settle on this, please leave it be and focus on more pressing issues. World hunger or something.
> An API backend + UI front-end consuming it is the perfect solution
I call shenanigans.
It is perfect only if you hand-wave away the math and consequences.
You've doubled your surface area, number of apps, stacks, dependency issues, deployment targets, bugs, uptime dependencies, hiring language/framework requirements and attack vectors.
It is the right tool for some jobs. I'd encourage you to stop assuming any of this is done. People thought that when XML and Soap were the thing.
Re: Matestack: Rapidly create interactive UIs in Ruby
#9Core contributor here: Happy we made it to HN, maybe a notch too early :) Right now there's only two not very supporting comments here. Glad the authors have solutions that work for them, but Rest + SPA is overly complicated for most small/mid sized projects in our opion. Everyone else: Feel free to join our Gitter if you like what you see!
This looks great. Slightly disappointed that it's not generically "in Ruby" but more specifically "in Rails", but the principle is really good and maybe there are a few bits that those of us who don't use Rails can extract.
Re: Matestack: Rapidly create interactive UIs in Ruby
#10Core contributor here: Happy we made it to HN, maybe a notch too early :) Right now there's only two not very supporting comments here. Glad the authors have solutions that work for them, but Rest + SPA is overly complicated for most small/mid sized projects in our opion. Everyone else: Feel free to join our Gitter if you like what you see!
This looks great. Slightly disappointed that it's not generically "in Ruby" but more specifically "in Rails", but the principle is really good and maybe there are a few bits that those of us who don't use Rails can extract.
I feel you and yes, there's plans to make it more into a PORO core and Rails/Hanami/Sinatra/personal flavor adapters. But we're a small team and Rails has the biggest market share & ecosystem, so it's the focus right now.
Feel free to reach out if you want to help! :)