Live data from Hacker News

An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

web.archive.org

71–80 of 132 posts

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#71

Earlier quoted context omitted.

I take it you’ve never tried to install nokogiri?

I think this joke is five or six years out of date (maybe more?). Nokogiri has been a breeze to install for a long time now.

I used nokogiri in Ruby on Rails in 2015 and since, and have never had a problem installing nokogiri.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#72

I was a devoted rails fan 10 years ago, but haven't looked back since full stack typescript. What's the general vibe on RoR nowadays?

Still using it, still highly productive. Not doing as much Rails work as I was 10 years ago but that's due to a change in the nature of my business. We still use it and Sinatra for the bulk of our Internet-facing and internal stuff.

If you use Sinatra take a look at roda. It’s fast and elegant.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#73
post #45

I was a devoted rails fan 10 years ago, but haven't looked back since full stack typescript. What's the general vibe on RoR nowadays?

Rails is unfortunately much slower, and it’s quite coupled to the concepts of server-side rendering and OOP MVC. Making Rails work with a modern frontend feels pretty hacky compared to using a full-stack TypeScript framework.

I'll give you the slow, but "modern" frontend is a breeze. Webpacker (yes, the deprecated one, newer solutions are worse) handles React beautifully, and my graphql API definition gets seamlessly converted into typescript types. If anything, it often feels even easier than the code sharing I've experienced in node-land.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#74
post #37
post #8

Earlier quoted context omitted.

Shopify and Github being run on Rails sorta put it to bed a long time ago.

Yes but we should not look at unicorns to settle this argument. After all not every company has the size of a unicorn, the world is not big enough for that. Very few companies get to the point that any random technology won't do. I've seen dozens of Rails projects going in production and many are still there. Same thing for any other programming language I guess. For normal sized companies Rails is OK. What matters i…

I just hired a developer for a Rails application. They definitely exist :-).

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#75
post #61

Earlier quoted context omitted.

If Hey has shown me anything, it is that Hotwire IMO is a complete gimmick. The frontend of Hey had so many issues for me. I used used hey from release until about a month or two ago, and it was the terrible UXUI experience that pushed me to cancel. Weird loading issues, things would update after performing actions, not loading in place correctly etc.

If you think Hey’s UI is bad, you should try Basecamp

Could you provide some examples? I use basecamp 8+ hours a day and have no idea what you have in mind.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#76

1. Rails retired Webpacker [that] compiled and bundled JS. Import maps, Turbo and Stimulus [are now the] default options, replacing Webpacker, Turbolinks and UJS . How do these new tools compare with the old? Versus Webpack, Vite etc?

We went with esbuild and regardless of speed (it's way faster) the main reason I like it is because the config is tiny and I actually understand what it's doing. Our Webpacker config was big and fragile by comparison.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#77

I was a devoted rails fan 10 years ago, but haven't looked back since full stack typescript. What's the general vibe on RoR nowadays?

I’ve never seen a more productive stack. Enables me to build complete apps as a single dev - which would take 2x-5x of the time and effort if using separate front end apps. Ruby makes me happy when I use it. Hotwire and Stimulus let me create front end interactions without a separate SPA. The ecosystem is mature and well maintained. Absolutely love it.

I second this sentiment exactly!

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#78
post #7

Great to see so many new features in Rails. Tbh, one of the reasons I use it for certain backend projects is how simple to do complex things. Managing files and image variants is a pain when developing a site. Rails make it easy and even adds more features around. However, I still think the UI layer is too coupled to the backend. Webpacker was a try, but I understand why it's deprecated. I would go on supporting comm…

It being a SSR framework is one of its advantages. De-coupling it is beyond trivial. They really have offered the best of both worlds.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#79

> Later in the year, Rails retired Webpacker Is Rails anti Typescript? It’s weird to see most other JS environments move to Typescript by default, while Rails now now ignores the ability to use it without jumping through hoops.

Webpacker was a wrapper for webpack, which was an attempt to make webpack easy to use but instead added unnecessary complexity.

You can use Rails with React/Vue + TypeScript pretty easily by using something like rails-esbuild or vite_ruby.

I'm currently working on a project with Rails, React, TypeScript, Vite, and InertiaJS and have been very much enjoying it, especially now that Inertia supports SSR.

Re: An Overview Of Upcoming Ruby on Rails 7.1 Features Part 1

#80
post #10

I was a devoted rails fan 10 years ago, but haven't looked back since full stack typescript. What's the general vibe on RoR nowadays?

> What's the general vibe on RoR nowadays? Most people that use it are fine and productive. Because of lazy evaluation, type issues persist though. Plenty of instances of trying to call string methods on integers, and array methods on nil, and Rails devs in denial that that's a big problem as the app continues to grow.

For what it's worth I've been working with Rails projects for over 7-8 years and I've never encountered this as a problem
Post reply on HN