News for hackers. Stuff that matters.
Re:Why We’re Sticking with Ruby on Rails at Gitlab by ElectricalUnion on Monday June 13, 2022 @01:00PM (#31728255)
> grok 2-3 languages

I don't think most people simply "accidentally grok" or use Smalltalk, Lisp or Raku; therefore I consider most people don't have what takes to grok Ruby either.

Re:Why We’re Sticking with Ruby on Rails at Gitlab by BlargMcLarg on Monday June 13, 2022 @01:13PM (#31728459)
Oh please, Ruby is not some arcane language. It's really not all that different from Python, JavaScript, Java and C# once you get used to your dev environment. Those languages alone cover way over half all the developers.

People here are acting Ruby is anywhere on the same level of difficulty for a regular high-level OOP developer as C++ or Haskell.

Re:Why We’re Sticking with Ruby on Rails at Gitlab by ElectricalUnion on Monday June 13, 2022 @01:23PM (#31728572)
> It's really not all that different from Python, JavaScript, Java and C#

I think that being able to dynamically replace behavior from almost anything at any point in your program is pretty much very different from Python, Java and C#.

The only other mainstream language with this capacity is Erlang, and Erlang is not exactly what I would call mainstream language.

Re:Why We’re Sticking with Ruby on Rails at Gitlab by BlargMcLarg on Monday June 13, 2022 @01:42PM (#31728807)
And you believe that Ruby both does not make it easy to learn this concept and makes aggressive use of this concept?

I believe you're severally overestimating the impact and importance of one quirk when many developers are picking up wildly differing languages and decently successful at it all the time.

Re:Why We’re Sticking with Ruby on Rails at Gitlab by corrral on Monday June 13, 2022 @01:42PM (#31728803)
> I think that being able to dynamically replace behavior from almost anything at any point in your program is pretty much very different from Python, Java and C#.

Javascript is pretty popular.

Re:Why We’re Sticking with Ruby on Rails at Gitlab by ElectricalUnion on Monday June 13, 2022 @02:46PM (#31729803)
I'm pretty sure Java != Javascript?
Re:Why We’re Sticking with Ruby on Rails at Gitlab by corrral on Monday June 13, 2022 @02:50PM (#31729871)
Sure, but it's a very popular language that puts the ability to modify behavior at run-time front and center. It's not like Ruby is special in that regard.
Re:Why We’re Sticking with Ruby on Rails at Gitlab by weatherlite on Monday June 13, 2022 @01:52PM (#31728950)
> I think that being able to dynamically replace behavior from almost anything at any point in your program is pretty much very different from Python

How so - Python is dynamic. Django does quote some magic (e.g defining methods on the fly etc).

Re:Why We’re Sticking with Ruby on Rails at Gitlab by ElectricalUnion on Monday June 13, 2022 @02:43PM (#31729744)
Python is dynamic but doesn't provide an easy way for you to change the types the language provides, while that is more or less expected in Ruby.
Re:Why We’re Sticking with Ruby on Rails at Gitlab by weatherlite on Monday June 13, 2022 @02:46PM (#31729802)
Looks pretty straightforward to me https://gist.github.com/fwenzel/622519
Re:Why We’re Sticking with Ruby on Rails at Gitlab by ElectricalUnion on Monday June 13, 2022 @11:31PM (#31734444)
That is not a language provided primitive?