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

I Miss Rails

chanind.github.io

Post reply on HN
Print view View original

371–380 of 522 posts

Re: I Miss Rails

#371

Post by acdha »

ggregoire wrote: post #104
ericb wrote: post #4

Why miss it, come on back, the water's still warm and the dev is still as fast as ever in Rails. Honestly, the JS stacks all seem vastly more annoying on so many levels. It seems like the JS ecosystem changes so fast because it knows better is possible, so it just tries to reinvent itself over and over. The JavaScript world starts with this weird prototype based language with a syntax that looks like it might be some…

> It seems like the JS ecosystem changes so fast Does it tho? React, Webpack, Babel and TypeScript have been around for a while now, and I can't think about anything else more recent that had a similar impact on the JS ecosystem.

Awhile back I converted a React app to pure JS after noticing that most of the commits for the last year had been updating as the slew of libraries it used had incompatible releases. The code size went down, performance went up, and you no longer needed a 300+MB toolchain just to load it.

Re: I Miss Rails

#372

Post by olavgg »

I love Rails vision about how to do full stack web development. It is a really good abstraction, that hides unnecessary technical complexity and lets you focus on solving business problems.

A lot of people here complains about Rails performance, and that is one of the reasons why I use the Grails - Java framework. It is not as polished as Rails, and has a few sharp edges, and it has a much smaller community which is still super-friendly and awesome. Grails however can still take the advantage of the enormous Java ecosystem. You have a library for about everything. And many of them is of really high quality too.

I have for the last five years built three successful startups with Grails, where the last one now employs 100 people. Grails has been really helpful here, as it has made it possible to move fast and add,fix,improve,break changes quickly. For my last startup Rails would most likely have struggled with the amount of data we are dealing with, while Java is hardly sweating. It is not something Grails specific, but still a part of the Grails application, that is why I mentioned Java.

My last startup, which now employs over 100 people didn't use React nor Angular either in the beginning, just vanilla Javascript. More speed, less complexity, less errors and so on. We use React today, but that is because new employees really really wants to work with. And developer happiness is really important.

Re: I Miss Rails

#373

Post by mikewhy »

baroffoos wrote: post #162
namelosw wrote: post #120

I've known rails for years but haven't yet used it seriously. I felt it's good because setting up is easy and the velocity is high. Until now I use it every day and I found it's really great and better than my previous impression: 1. Compared to JS there's always a specific way of doing things - how to validate, how to dispatch async Job, how to send emails and real-time notification etc. 2. Compared to Spring there'…

>1. Compared to JS there's always a specific way of doing things - how to validate, how to dispatch async Job, how to send emails and real-time notification etc. This is so important. When doing something on rails you always get instructions on the exact things you have to do where as JS always seems to either give you 500 different versions of the instructions or just expects you to work out how to set it up based o…

I mean, we're comparing languages to frameworks here. Of course there's going to be multiple different solutions for a language while a framework will have fewer.

Re: I Miss Rails

#374

Post by almostarockstar »

If I understand the situation correctly:

Rails applications benefit from batteries included boilerplate because Rails "owns" the whole stack.

"Modern" (contemporary?) JS applications benefit from separation of concerns, and flexibility because each layer is interchangeable.

So how do we make this better? We can't reasonably split Rails up to match the benefits of JS. The obvious (naive?) solution is to provide a protocol that JS layers can follow. Specific packages/layers can decide to provide the protocol which makes them interoperable. The developer may then pick and choose, knowing that if they choose packages that comply with the protocol, they can use the "batteries included" features.

It would be fairly trivial to identify the major features that most apps reimplement. Getting it all to play well together would not be as easy.

As the OP described, I think Meteor was a great platform, but had some fatal flaws. If "Meteor-the-company" was "Meteor-the-protocol" I think we would have been in a much better position.

Re: I Miss Rails

#376

Post by styfle »

lettergram wrote: post #40

I still write Rails applications regularly, some applications I've maintained since 3.0 to 5.x. What's amazing, is I booted up a 4 year old project in minutes the other day at work. A co-worker was interested in using the project, it took 15 minutes to setup clean. Overall, I find Rails is easily more maintainable and definitely enjoy it more than the Django and Flask apps I write regularly. Javascript (Node + React/…

That’s a fascinating tool! Now I realize I need to use more enjoyable words when discussing TypeScript :)

Re: I Miss Rails

#380

Post by sickcodebruh »

jrochkind1 wrote: post #189
0xADEADBEE wrote: post #28

Earlier quoted context omitted.

I know this is the opposite of what you asked but I find Rails to be keeping pace with modernity much better than its conemporaries! Django seem to have given up on integrating websockets (ActionCable has been in Rails for literally years now), nor is there trivial integration for JS assets/asset pipeline functionality. I don't write much of either anymore, but I'd still reach for Rails the instant I need to get some…

I'm interested in hearing about applications successfully using ActionCable for what and how. It's unclear to me how much use it's getting, or how well it meets actual use cases.

I just deployed ActionCable into production yesterday. I’ll be using it to share some information between our users’ mobile app and our web client.

I’m concerned about performance. As much as I know that premature optimization is the Devil, it’s hard to stomach deploying something that is so notorious for becoming a bottleneck. Once I get past my MVP of this feature and have some maintenance hours budgeted, I plan on exploring AnyCable.

Post reply on HN