4 ms·

Core 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 s

by pdoub 7y ago

Core 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!

mosselman 7y ago
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?
- pdoub 7y ago
  Basically, you're right. In a JS-free world this would be probably overblown (or a niche thing for Ruby fanatics). Where Matestack shines is when it comes to very generic JS behaviour that you don't want to recreate for the 100st time in a project - just wrap it into Matestack component and tell it what to do. I suggest watching my co-founder and Matestack creater Jonas introduce the concepts behind it: https://www.youtube.com/watch?v=OY5AeGhgK7I https://www.youtube.com/watch?v=OY5AeGhgK7I
- pdoub 7y ago
  Technical clarification: We don't "generate" Vue.js components. Matestack generates HTML that contains component tags. Those tags reference existing Vue.js components and hand over some configuration. This enables us/you to define interactive UI behavior by just configuring predefined Vue.js components in pure Ruby. If one needs custom UI behavior here and there, just add your own Vue.js components (write some lines of JavaScript) and then add and controll them like you do with the predefined dynamic (=Vue.js) core components. this approach is much easier than creating a standalone JS frontend app. You might end up writing 90-99% Ruby and just some lines of JS while getting an interactive, dynamic UI (or even a PWA if you add some meta information).
Doctor_Fegg 7y ago
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.
- pdoub 7y ago
  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! :)
onli 7y ago
I for one think that this looks incredibly impressive. A solution to reduce what needs to be written while giving ruby developers a powerful way to build a modern frontend, making it possible to stick with pretty much Ruby. And the website explains the concept very well. It's pretty much contrary to the route I took for my current project (and Rails instead of Ruby :( ), but something to bookmark and consider next time. Excited to see whether that concepts works as well in practice. That's a win in my book. One question though: In your diagram you are saying Infrastructure 1, 2, 3 for the classical/current approach going into one API vs Matestack sitting on top of one infrastructure, right? Why? If there is an API sitting between backend and the UI there should not be a need for three backend infrastructures. I feel like you mean something else there, and the text also does not fit to the diagram as I understand it. Maybe something to double check. The comment below how Matestack maps to native apps is warranted though. You are planning alternative renderers to web/vue, targeting native apps?
miccah 7y ago
This looks very cool! I noticed some typos on the home page that should be corrected: > Beeing a small dev team > suffer less cognetive load
gremlinsinc 7y ago
I have a habit of 'perusing' github for cool oss projects. I'm the one who submitted this and while I haven't touch rails code since 2012, makes me almost want to give it a go again on my next project. That and I was reading that demand is higher than supply because a lot of people have jumped from rails, so employment prospects are good for at least awhile. So I was looking at ways to make ui easier on rails. Edit: I'm normally a vue/laravel dev. So I was actually searching rails + vue on github w/ more than 5 stars and updated in the past year. Because most rails tools/projects to seem to gear towards react, but I'm not a fan react/redux. I like SFC's in vue much better.

by pdoub 7y ago

mosselman 7y ago

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?

pdoub 7y ago
Basically, you're right. In a JS-free world this would be probably overblown (or a niche thing for Ruby fanatics). Where Matestack shines is when it comes to very generic JS behaviour that you don't want to recreate for the 100st time in a project - just wrap it into Matestack component and tell it what to do. I suggest watching my co-founder and Matestack creater Jonas introduce the concepts behind it: https://www.youtube.com/watch?v=OY5AeGhgK7I https://www.youtube.com/watch?v=OY5AeGhgK7I
pdoub 7y ago
Technical clarification: We don't "generate" Vue.js components. Matestack generates HTML that contains component tags. Those tags reference existing Vue.js components and hand over some configuration. This enables us/you to define interactive UI behavior by just configuring predefined Vue.js components in pure Ruby. If one needs custom UI behavior here and there, just add your own Vue.js components (write some lines of JavaScript) and then add and controll them like you do with the predefined dynamic (=Vue.js) core components. this approach is much easier than creating a standalone JS frontend app. You might end up writing 90-99% Ruby and just some lines of JS while getting an interactive, dynamic UI (or even a PWA if you add some meta information).

Doctor_Fegg 7y ago

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.

pdoub 7y ago
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! :)

onli 7y ago

I for one think that this looks incredibly impressive. A solution to reduce what needs to be written while giving ruby developers a powerful way to build a modern frontend, making it possible to stick with pretty much Ruby. And the website explains the concept very well. It's pretty much contrary to the route I took for my current project (and Rails instead of Ruby :( ), but something to bookmark and consider next time. Excited to see whether that concepts works as well in practice. That's a win in my book. One question though: In your diagram you are saying Infrastructure 1, 2, 3 for the classical/current approach going into one API vs Matestack sitting on top of one infrastructure, right? Why? If there is an API sitting between backend and the UI there should not be a need for three backend infrastructures. I feel like you mean something else there, and the text also does not fit to the diagram as I understand it. Maybe something to double check. The comment below how Matestack maps to native apps is warranted though. You are planning alternative renderers to web/vue, targeting native apps?

miccah 7y ago

This looks very cool! I noticed some typos on the home page that should be corrected: > Beeing a small dev team > suffer less cognetive load

gremlinsinc 7y ago

I have a habit of 'perusing' github for cool oss projects. I'm the one who submitted this and while I haven't touch rails code since 2012, makes me almost want to give it a go again on my next project. That and I was reading that demand is higher than supply because a lot of people have jumped from rails, so employment prospects are good for at least awhile. So I was looking at ways to make ui easier on rails. Edit: I'm normally a vue/laravel dev. So I was actually searching rails + vue on github w/ more than 5 stars and updated in the past year. Because most rails tools/projects to seem to gear towards react, but I'm not a fan react/redux. I like SFC's in vue much better.