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

131–140 of 522 posts

Re: I Miss Rails

#131

Post by burlesona »

0xADEADBEE wrote: post #22
jph wrote: post #14

Elixir and Phoenix are excellent, and you'll recognize many of the same concepts in these. The communities are excellent as well, and welcoming to newcomers.

They're fantastic and I hope the future is bright for them but I've had to pick Rails for a few projects over the last few months because the library support is so much more established. The more I get to use Phoenix, the more I am convinced it is the most well designed web framework there is, so I hope to use it a lot going forward.

Not a coincidence, Phoenix / Elixir originated with Jose Valim, a former Rails Core dev.

Re: I Miss Rails

#132

Post by davidbanham »

I actually have gone back to writing server-rendered apps like it's 2012 and it's been wonderful.

Server-rendered used to mean slow and clunky but I've found that using Go my page loads are super fast. The inter-page transitions can sting a little on really really slow connections, it's true. But users are much more willing to deal with them if they haven't first been subjected to a minutes-long spinner while the SPA loads up all its libraries and state.

A little game I sometimes play is asking fellow developers to try and guess the frontend framework used on one of my apps. They click around for a little while wondering "Angular or React" before I tell them it's actually just some Go templates rendered on the server. It often opens their eyes that the loads were so fast they couldn't actually tell they were happening.

SPAs have their place and I've written a lot of them. It's amazing how far you can take server rendering in 2019, though.

Re: I Miss Rails

#133

Post by burlesona »

jaequery wrote: post #73

I actually dislike RoR but I'm at the same conclusion as OP. There is just something about Ruby that makes me want to keep going back to it. It is difficult choice when given the fact that JS is (and probably always will be) the de-facto language for the web so it's really hard to dismiss Node. But if that wasn't the case, I'd stick with Ruby all day.

If you really like Ruby but don’t love the “magic” side of Rails, you should try Roda and Sequel. The whole ecosystem built by Jeremy Evans is a joy to work with.

Re: I Miss Rails

#134

Post by revskill »

0xADEADBEE wrote: post #123
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…

This sounds exhausting! But I'm betting there's some pretty solid benefits or you wouldn't do it. Could you expand on why someone might pick this a little?

The main benefit i got is that, i could independently package SSR React Component, then my application is just a composition of those packages.

Re: I Miss Rails

#135

Post by revskill »

wzy wrote: post #118
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".

Actually, this stack is deployed as a serverless function ! "Serverless for API" means i could use any language to develop API. Serverless provides better scalability in my opinion.

Re: I Miss Rails

#136

Post by strken »

tomc1985 wrote: post #92
BillFranklin wrote: post #6

> if the modern equivalent of Rails already exists, please let me know! You're in luck. Rails 5.2.3 was released 20 hours ago. More seriously, I feel rails is still excellent and I'm happy to work with it every day. I'd be interested to hear more about what makes rails not modern? I find it a very productive framework. EDIT: If you're talking about missing a JS equivalent of rails, do you know about Loopback? https:/…

Rails is FANTASTIC! I work on a hybrid React-on-Rails application and working on the React portions is so. fucking. painful. Seriously the shit people come up with with this "tool" makes corporate-hack Java programmers look good. I am always taking the backend Rails-y tickets if I have the chance

Blaming complexity on React is a bit like blaming complexity on ERB. The problem isn't React, the problem is the massive hole where React doesn't have an opinion. React improves the area around the hole so much that the technologies we use to fill the void look obviously deficient in comparison.

Re: I Miss Rails

#137

Post by burlesona »

westoque wrote: post #49

I believe we are at a turning point for the future of web apps and servers. After using Firebase and serverless (I hate this term) technologies in the last few, I didn't miss doing all what's said in the blog at all. Need authentication? Just turn the feature on in Firebase and use it. Need storage? Need analytics? Just do the same. The future is bright and we are heading in the right direction. With this, we can get…

This is also very expensive very quickly compared to the mileage you can get running an application on AWS.

And if you pick a neat tech provider and it goes belly up (like Parse!) you’re in some real pain.

Re: I Miss Rails

#139

Post by mooreds »

garren wrote: post #39
k__ wrote: post #12

AWS Amplify is becoming the "Rails" of serverless. It already has impressive code generators for GraphQL.

I was just playing with Amplify the other day. I was super impressed with the graphql codegen. I think the Rails comparison makes sense with the exception of the vendor lock-in. I haven’t looked at the Serverless framework very closely, but I know it’s not tied to AWS. I wonder if that’s a better comparison to Rails?

Serverless is more aimed at abstracting infrastructure, with small services written in lambda/cloud functions/etc. So not really a rails replacement.

Re: I Miss Rails

#140

Post by ravenstine »

People always forget Ember.js, like it's some relic of the past, despite it having very active development and a toolchain for a consistent Rails-like experience on the frontend. There's no reason why you can't use React or Vue components inside an Ember.js application if that's what you prefer.

As much as I've grown to despise the Ruby community for relying too heavily on metaprogramming and inheritance, leading to abstraction hell, I think Rails is still a great framework for serving web pages. Just because it's not the shiny new thing doesn't mean it can't do most of the things we want from it(not every company is FAANG scale), and there is still an abundance of Rails jobs in 2019.

Post reply on HN