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

271–280 of 522 posts

Re: I Miss Rails

#271

Post by vturner »

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 trouble is "we," the developers aren't the tech industry making the decisions. The managers, who once were full time developers, are making the decisions. I can say hey let's use this stable, mature tool, but which catches enthusiasm more? That or the guy drooling over React and all the complex mystery JS libs saying it's the best thing ever?

Re: I Miss Rails

#272

Post by keypusher »

inapis wrote: post #37
hw wrote: post #30

Earlier quoted context omitted.

I believe Shopify is built on Rails and is (or was) a Rails monolith. It's worked well for them.

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

Airbnb, Kickstarter, Twitch, GoodReads, Bloomberg, there is quite a list of companies who still run a significant amount of their site through Rails. Over time I imagine that particular bottlenecks and performance critical pieces have been pulled out into other languages and services as necessary, but I certainly wouldn't feel bad about it if I was developing or maintaing a Rails site today. It's significantly better than PHP, and a hell of a lot of sites are still run on that. The reality is that if you really need to scale, your primary bottleneck will probably be the datastore, not the frontend.

Re: I Miss Rails

#274

Post by jeremy_k »

rohan404 wrote: post #203

Ruby on Rails out of the box gets a lot of bad rep for being slow and non-performant. Has anyone replaced MRI with JRuby or TruffleRuby to mitigate that? Were there any significant "gotchas" with integrating it?

Been following TruffleRuby, I did recently just spin up a super dummy app where I swapped out mysql to postgresql, made a migration to create a table and generated some fake data. Opened a console and ActiveRecord was able to query. Thats a big step forward as they had said the ActiveRecord connections were some of the biggest hurdles.

Does this story answer your question about performance? Not really, but if I wanted to dive deeper (which I do at some point!) I think TruffleRuby is a real option.

Re: I Miss Rails

#275

Post by realusername »

gurkendoktor wrote: post #183
hombre_fatal wrote: post #154

Earlier quoted context omitted.

Static-typing seems so at odds with Ruby/Rails that I can't even imagine what that would look like.

I'm waiting for a chance to try out Crystal/Amber, which is type-checked (not sure how safe?) and can be pre-compiled like Go apps. It looks really close to Rails: https://github.com/ChangJoo-Park/amber-realworld-example-app... (I couldn't find any code snippets on the official Amber framework page, I hope this is representative.)

Crystal/Amber combination is such a joy to work with, it's too bad it's not more popular, I'm contributing a bit to the project sometimes and use it for personal stuff. I regret it's not that trendy because it's the best web experience I ever had.

Re: I Miss Rails

#277

Post by lytedev »

enraged_camel wrote: post #86
wefarrell wrote: post #76

Earlier quoted context omitted.

Agnostic of stack, SPAs provide a clear separation of concerns. The api layer is responsible for transforming data between the client and controlling access. The client is responsible for presenting the data structures provided by the api to the user, and turning user inputs into data structures that the api can consume.

Don’t forget interactivity and real-time feedback for user actions. SSR simply can’t provide that without lots of javascript thrown inside each template, and we all know what that leads to...

Also check out the newly released Phoenix LiveView!

Re: I Miss Rails

#278

Post by peteforde »

revskill wrote: post #134
0xADEADBEE wrote: post #123

Earlier quoted context omitted.

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.

Honestly, this is such an un-sexy answer that it might shock some sense into people that are still on the fence. It might not be too late for you.

Seriously, gang: Rails is productive, fun and lets you focus on making your customers happy instead of optimal package composition.

Re: I Miss Rails

#279

Post by [deleted] »

jonahx wrote: post #41
ericb wrote: post #20

Earlier quoted context omitted.

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?

It means it's everything but the kitchen sink: heavyweight, difficult to learn and use, and full of features you don't need. It has nothing to do with popularity being bad. In general that's good a thing, because support is better (and rails does have terrific support), but it does exert a feature-accretion force.

[deleted]

Re: I Miss Rails

#280

Post by james_s_tayler »

vips7L wrote: post #230
nurettin wrote: post #145

Earlier quoted context omitted.

Long time rails developer turned "enterprise". Spring-cloud now requires much less boilerplate and is easy to develop with using kotlin's syntactic sugar shortening code and making it more concise. Orm is kind of a failure and requires us to write some queries by hand into string literals, but at least it has it's own sql syntax to avoid engine dependence.

Spring Boot is so amazing. I don't feel like any of it is boiler plate at all.

I used to think SpringBoot was amazing until I tried Rails. Then I really felt another level of holy shit.

I have lots of love for both. They're different tools. Ultimately I dropped Rails because being without static typing just isn't for me, but certain parts of the experience were positively magical.

I sort of feel the same way about Boot. That auto configuration mechanism is next level. The breadth and depth of what's available in the Spring ecosystem is great too.

They're really kind of optimized for different things though. Like Rails has some gems you just drop in and it blows you away what you get for stunningly little effort. But then it's not that customizable and you find yourself fighting with it. Spring has all kinds of battle tested enterprise grade bits and bobs that take a lot longer to operationalize but they'll last you forever.

I'm currently trying out aspnetboilerplate as a middle ground between the two. Specifically the aspnetzero version. It's like that "holy shit I get all this out of the box?" with Rails but the "I can understand this, work with it, customize it if I need to and it's going to last the distance". Im finding there is a slight learning curve to it and I wouldn't necessarily make all the same choices the framework does, but so far I can see this becoming a happy medium once I've found my groove with it.

Post reply on HN