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

Where is Ruby Headed in 2021?

bignerdranch.com

Post reply on HN
Print view View original

161–170 of 360 posts

Re: Where is Ruby Headed in 2021?

#161

Post by cpursley »

joelbluminator wrote: post #155
cpursley wrote: post #150

Earlier quoted context omitted.

Elixir and Phoneix are more popular than ever, especially with the release of LiveView. The ecosystem and community continues to absorb refugees from Ruby and other stacks. It's such a better platform than Ruby and Rails that I won't bother writing about it here - there are already hundreds of blog posts about it. Productivity is at least on par with Ruby (I believe better) and performance on another plane of existen…

Sorry that really doesn't add up to what I see when I look at job boards, Elixir has really poor numbers. The Ruby guys who wanted to jump ship to Elixir already did so a few years ago (some of them will continue to jump ship from Elixir to Rust or Go because hey why not). So I don't know where new growth will come to Elixir. It's not just jobs, by any metric you can think of Elixir is an obscure tech, if you want I…

You may have heard of some of these companies:

- https://appunite.com/blog/top-10-elixir-companies-to-follow

- https://elixir-companies.com/en

Re: Where is Ruby Headed in 2021?

#162

Post by Lio »

clairity wrote: post #127
scrose wrote: post #87

Earlier quoted context omitted.

> I’m sad about the move to mounds of JavaScript. Nothing can match the productivity of simple_form and bootstrap. You might like some of the recent Rails 7 previews. I believe they’re removing Webpack out of the box and trying to simplify things on that end[0]. [0] https://weblog.rubyonrails.org/2021/9/15/Rails-7-0-alpha-1-r...

to me, this is what makes the upcoming rails 7 release really exciting: no more node, npm, webpack, & yarn! all that js tooling complexity thrown right out the window, replaced with the much simpler set of es6 modules, turbo & stimulus (and maybe strada too).

There seem to a lot of ruby pieces falling into place for Rails 7.

The Achilles Heel of Hotwire apps has previously been the low number of supported websocket connections and high memory usage when using ActionCable and Puma but I have high hopes that Falcon[1] will take care of that.

That along with Github's View Components[2] and Tailwind make me really please with the way Rails is heading right now.

1. https://github.com/socketry/falcon

2. https://github.com/github/view_component

Re: Where is Ruby Headed in 2021?

#163

Post by joelbluminator »

cpursley wrote: post #161
joelbluminator wrote: post #155

Earlier quoted context omitted.

Sorry that really doesn't add up to what I see when I look at job boards, Elixir has really poor numbers. The Ruby guys who wanted to jump ship to Elixir already did so a few years ago (some of them will continue to jump ship from Elixir to Rust or Go because hey why not). So I don't know where new growth will come to Elixir. It's not just jobs, by any metric you can think of Elixir is an obscure tech, if you want I…

You may have heard of some of these companies: - https://appunite.com/blog/top-10-elixir-companies-to-follow - https://elixir-companies.com/en

Pepsico, Toyota ...come on now that's weak. They're not even IT companies let alone Tech. Whatsapp is running on a fork of Erlang afaik , not Elixir. Look I'm not saying no one is using Elixir, I'm just saying there's little jobs that's all. Cherry picking some famous names isn't gonna change that.

Re: Where is Ruby Headed in 2021?

#164

Post by gls2ro »

chishaku wrote: post #160

Other than Rails, what do people use Ruby for?

Sinatra is a great framework for fastly developing REST APIs. It benefits from almost the whole Rubygem possibilities while being fast to develop.

Middlemanapp is a great static website generator written in Ruby and easy to extend that I used many times to generate simple generated websites.

Jekyll is a great static blog generator.

Re: Where is Ruby Headed in 2021?

#165

Post by oblio »

devoutsalsa wrote: post #112
sanderjd wrote: post #110

Earlier quoted context omitted.

The often impossibility of finding the definition of the methods I'm calling is the main thing that soured me on Rails. I think a more explicit style is more common nowadays, which is a good thing.

“git grep” is pretty amazing for tracking things down.

That's like someone asking for directions and you giving them a shovel and a introduction to archaeology manual.

If someone asks for directions you give them directions or a current map.

Re: Where is Ruby Headed in 2021?

#166

Post by gls2ro »

d3nj4l wrote: post #132
coldtea wrote: post #51

Earlier quoted context omitted.

Wanna bet and check back in 5 years?

I love Ruby but I'd still cautiously take that bet. At the same time, I don't think it's easy to come up with terms for a fair judgment of who wins. What does Crystal being the future of Ruby mean? To me, I think in the specific cases where people who like Ruby want Ruby - mostly webapps with great dev ergonomics and productivity - Crystal will definitely start to gain ground, because both Amber and Lucky are lovely…

Adding to d3nj4l's answer, that Ruby also has a great community of active and passionate (yes, in the proper sense passionate of the programming language) developers.

I think Elixir has better chances of taking over some of the Ruby pie from this perspective as the Elixir community is a lovely and helpful as the Ruby one.

Without such community it is very hard to build momentum and most programming languages remains great options but limited to a small number of projects.

I like Crystal and played with it a little bit. I tried to use it in production for a small project where I offloaded some tasks from Rails into Crystal small programs.

Re: Where is Ruby Headed in 2021?

#167

Post by jug »

Minor49er wrote: post #37

The future of Ruby is in Crystal https://crystal-lang.org/

This was honestly what crossed my mind as I read that article as well. They're basically asking for Crystal and it's already done. Static type checks, performance, fibers and channels. As a bonus things like compile time null checks.

Re: Where is Ruby Headed in 2021?

#168

Post by huma »

The first time, a while ago, when I tried Ruby, coming from Java, it was pure joy of freedom :) I really liked the duck typing approach and the dynamic feel of the language. It's rather sad to see static "Java" creeping into it.

Re: Where is Ruby Headed in 2021?

#169

Post by chrischattin »

valenterry wrote: post #98
prescriptivist wrote: post #86

Earlier quoted context omitted.

Those are fair points, but I just kind of hold the entire program space in my head. I work on a pretty large and complicated Rails app that does real world things (handle money, deal with people and companies, etc) and it's daunting at first but after a while it's sort of become one big system of objects interacting with other objects in a global objectspace and that's how it exists in my head. I think for people tha…

I think this is actually a very efficient way of programming. but it doesn't scale in project size and team size. Similar for Lisp. This is why these languages are really good for prototyping, but not as good anymore for big, longterm projects imho. That's also why I don't think it's a great idea to add types etc. to programming languages like python or ruby. They are not made for this and they should focus on what t…

This is just not true. There are several multi-Billion dollar public companies with millions of users and thousands of employees built on Rails.

In fact, the philosophy of convention over configuration et all makes Rails MORE scalable and easier to onboard new people than anything else out there that I’ve seen.

Re: Where is Ruby Headed in 2021?

#170

Post by discreteevent »

inopinatus wrote: post #119
saagarjha wrote: post #118

Earlier quoted context omitted.

I don’t see how this helps?

Ruby's dispatch is Smalltalk-like, not Java-like; it is (very) late-bound. The consequences for interface design are dramatic, the natural style being one in which objects notify each other, rather than telling each other what to do, and the result is loose coupling and ease of composition. People trying to write Java-like OO in Ruby end up confused and frustrated.

There's a tradeoff between coupling and cohesion. All the books and talks are about decoupling because that's the interesting part. The problem is that in poor codebases you find everything has been decoupled and the complexity is a nightmare. As Adele Goldberg said: "“In Smalltalk, everything happens somewhere else.” It's better to have a system where you only decouple where and when you want to because you have decided that paying the cost is worth it.
Post reply on HN