Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby on Rails in a week

simplethread.com

Post reply on HN
Print view View original

171–176 of 176 posts

Re: Ruby on Rails in a week

#171

Post by jonnymoe »

czbond wrote: post #156
pdoub wrote: post #25

Anyone doing/thinking about Rails in 2020 should give matestack a try :) reactive user interfaces in pure Ruby (and Vue.js under the hood!) https://github.com/matestack/matestack-ui-core

@pdoub - can you elaborate on the Vue under the hood? I love ruby, and like Vue a lot. Does Matestack do a translation layer from Ruby -> Vue in JS? Eg: transpile, etc.

Matestack's reactive core components are built on pure Vue.js components. When a reactive component is rendered, Matestack renders a HTML component tag, passing in configuration via props and ships that to the browser. Vue.js on the browser then detects these component tags and mounts the appropriate Vue.js component, which reads the configuration coming from the props and perform the desired (configured) functionality. The HTML within the component tag is used as the inline template for the Vue.js component. It's rendering HTML tags out of pure Ruby on the one hand, and mounting pure Vue.js component on top of that in the browser on the other hand.

Re: Ruby on Rails in a week

#172

Post by jrochkind1 »

herpderperator wrote: post #65
jrochkind1 wrote: post #57

Earlier quoted context omitted.

Do you mean it didn't feel mature before June 2016 or August 2019? Cause... those things are there now, so how can they be examples of it not feeling mature now? What's it missing for you now to feel mature? (And also, lots of people and code definitely did left joins and multiple databases in Rails before those dates, without needing to add any sort of plugin/additional dependency. I did myself, plenty of times! Rai…

Well, business don't jump on the latest version right away for many reasons (stability, bugs, upgrade woes...) Maturity is closely correlated to how long things have been around. Just because multiple database support was officially added on August 2019 it doesn't make it mature after that date. It takes a long time to achieve maturity - people to adopt and improve on that functionality without breaking things. We ha…

So I have been accessing multiple databases for years, without any third-party gems. But it's true I've been doing it in limited ways, only a few tables that aren't the 'main' database, the secondary database being managed externally.

The things that were difficult before (that I didn't do), that are now supported/smoother, include: migrations (schema-history-as-code) for multiple databases; and the really new exciting feature, different database connections used for read and for write. (i'm sure there are other platforms that support that, but I know it's not universal).

To me these seem like fairly advanced features, I am not sure how many/which other "competing" frameworks support these features; it's a matter of opinion whether these features are required for 'maturity' or not, I'm not going to argue about that.

But to be clear that basic ability to connect to multiple databases has existed since long before August 2019.

For the other feature mentioned as being introduced four years ago in 2016, trying to make the argument that it indicates a lack of maturity because it should have existed for even more than 4 years in order to call it 'mature'? I think it's clear there is just some axe-grinding going on there.

In general, whatever Rails faults are (and of course it has plenty) I don't think a lack of "maturity" is one of them. There are few frameworks/platforms more mature (and I would actually be interested in what examples you are thinking of). If I wanted to talk about the places where Rails isn't as mature as would be liked, it's not features that don't exist or features that were introduced "only" four years ago -- it's in some new features that IMO were introduced with insufficient stability and polish, like webpack integration. That, or ActionCable, are much better examples if you want places where Rails isn't mature. The examples in this thread are... silly.

Re: Ruby on Rails in a week

#173

Post by Fire-Dragon-DoL »

brink wrote: post #13
johnklos wrote: post #11

Nah. In a week, some component will need a security update, and your "hello, world" will break.

Rails has been relatively consistent over the past 10 years with few breaking changes, especially compared to most other frameworks.

That's because they are not written in the changelog. From 5 to 5.1 the way dates are summed changed. In the changelog there was a point in changing the duration of a year, but not changing how dates are summed. This triggered a lot of problems in a software I worked on involving calculations with time and money.

Finally, rails upgrades are always painful, unless your codebase is written by engineers that know how to avoid those pains. In which case, you probably will end up without rails (a lot of the features are useless to highly experienced engineers)

Re: Ruby on Rails in a week

#174

Post by zbentley »

obiefernandez wrote: post #84
zbentley wrote: post #63

Earlier quoted context omitted.

> At what point do you need that? What percentage of users do? In my experience, rather a lot.

If you need to connect to multiple databases at a time for your business logic then you're doing it wrong.

...are you serious?

Virtually every software shop I've worked at has had most backend code communicating with multiple databases to get the job done. Sometimes those databases were behind [micro]service abstractions and the communication was indirected by RPC/one-way async dispatch. Sometimes it wasn't. But multiple backend datastores' contents were required for most business operations. The only places I've worked with that didn't need that were very, very small (single digits of thousands or fewer users).

Re: Ruby on Rails in a week

#175

Post by b0afc375b5 »

jurre wrote: post #140
b0afc375b5 wrote: post #68

Earlier quoted context omitted.

If anyone has any tips or documentation that might help with regards to Rails containerization, I'm interested in knowing as well.

What specifically are you running into? I may have trouble seeing any gaps in documentation because I’ve been running rails in a containzerized environment for years and it seems to just work

I'm still in the planning stages of migrating rails from ec2 to ecs.

I asked because parent comment said he/she was running into problems. But if your experience is smooth sailing so far then that's great.

Post reply on HN