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

111–120 of 522 posts

Re: I Miss Rails

#111

Post by wzy »

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.

Yeah, but I am quiet sure at least 12 new frontend frameworks were pushed to Github in the last 24 hours, plus 143+ NPM packages probably broke with the last Babel update

Re: I Miss Rails

#112

Post by viksit »

"Move fast and break things" very accurately reflects the state of Javascript development in 2019. Libraries and frameworks, and node/npm themselves move so quickly that APIs, versions, ways of doing things -- all break so quickly as to be ludicrous.

This post rings true.

I gave nextjs a try recently to build a simple dashboard that could connect to our oauth provider. Forget external libraries, even simple ways to do state management, user login, screens, HOCs to guard routes - all of this is poorly documented, managed, and there are 100s of github gists that aren't versioned, demonstrate old APIs that have been deprecated and aren't really usable unless someone who knows that they're doing goes in, and cobbles together an example.

Re: I Miss Rails

#113

Post by stock_toaster »

xvilka wrote: post #97
inapis wrote: post #37

Earlier quoted context omitted.

Shopify, Github, Gitlab are all built on rails. Even Twitter was on rails in its early days.

GitLab rewrote some parts in Go, because Ruby was too slow on a big scale.

So “use rails until you raise a C round?” heh

Re: I Miss Rails

#114

Post by namelosw »

ericb wrote: post #20
jonahx wrote: post #16

Earlier quoted context omitted.

Here are two of the most popular books on Rails on Amazon, along with their page counts: "The Rails 5 Way" (1088 pages) "Ruby on Rails Tutorial: Learn Web Development with Rail" (816 pages) Rails is enterprise.

What does this enterprise slur even mean ? Is it like saying a band sold out when they had a hit record? Do we only use undiscovered indie frameworks now?

My personal guess on this enterprise would be things like Spring or .Net where everything has an interface instead of just do things like Rails.

Re: I Miss Rails

#115

Post by 0xADEADBEE »

debuggerpk wrote: post #36
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…

coming from the django-world, i had the same complain with rails. It was a little too fast for a me.

Would you mind expanding on this? I went from Django to Rails and loved it so I'm always genuinely curious about the experiences of people who didn't have the same fun as me.

Re: I Miss Rails

#116

Post by rubyfan »

The current javascript landscape reminds me of PHP circa 2003 + isomorphic single page madness + functional philosophical purism + dreams of type safety +

Yuck.

Re: I Miss Rails

#117

Post by lainga »

Barrin92 wrote: post #108
barce wrote: post #102

Earlier quoted context omitted.

I think what the OP meant by 'modern,' was an equivalent of Rails that uses the technologies demanded by the tech industry today. On the one hand, the industry went to Python because a ton of data science libraries were written in that. On the other hand, React ended up real dominant on the front-end because of all the sh*t code people put between HTML JavaScript tags. Another route, is any promising asynchronous and…

>demanded by the tech industry today. That attitude needs to get out of everyone's head. You are the tech industry. If you want to build something in Rails, a mature and capable framework that has tons of support and won't go away, just do it. Who's going to stop you? Applies to any other technology that's stable as well.

The Whims of a Fickle Manager.

Re: I Miss Rails

#118

Post by wzy »

revskill wrote: post #68

Here's how i replace Rails with the "modern stack": - Compile Graphql schema into Typescript typings + Fragments for "Active Record" - React Hooks as controllers action. - React Suspense for HTML rendering. - Apollo for graphql caching - ExpressJS for middlewares. - @reach/router for routing. - @loadable/component for code splitting. - Serverless for API. I missed Rails, too. But i found that the "modern stack" is no…

... you had me up until "Serverless".

Re: I Miss Rails

#119

Post by scruple »

b212 wrote: post #67

As a front-end developer I hated Rails, every day was a struggle working with the project, it was so slow. It was around 4 years ago and I was using top of the line Macbook Pro. Our project wasn't badly written, it was just that slow. Is it better today? I somehow ended up working with PHP-based back-ends but for smaller projects and I sometimes miss Rails, because Docker for Mac...

You'd have to start by defining some things. Are we talking about AJAX request/response cycles being slow? Are we talking about SSR request/response cycles being slow? What was the app doing, CRUD? Something more interesting?

For reference, the Rails app that I am working on, almost literally right now, is responding to HTTP API requests, performing authentication and resource authorization, creating a background job (or 2 or 3), and posting an event to kafka, in 2-3 ms. This is on my work-issued dev laptop from 2016.

If I start hitting the SSR portions of this same app, I'm getting response times in the 70-80ms range pretty consistently across the 6 or so pages that I just hit to get a quick baseline. No front-end frameworks here. Just turbolinks, ERb, HTML, CSS, and sprinkles of ES6 (served via webpack(er)).

Re: I Miss Rails

#120

Post by namelosw »

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's only a recommended default way you can easily start with. You don't struggle with SpringWeb vs WebFlux, different JMS implementations, Hibernate or query builders, etc.

Post reply on HN