Language and Cognition
Philosophers and linguists have long asked the question, Does the language we speak shape the way we think?
We n...
For further actions, you may consider blocking this person and/or reporting abuse
I think this is also happening in reverse a lot these days. I definitely think I spot Rubyisms in new ideas these days. Hard to trace idea origins though.
I, too, am still very much enjoying developing in Ruby.
I agree that programming languages borrow good ideas from each other all the time, but Ruby's focus on developer happiness seems to make this a first class goal of the language.
Totally agreed. I can't think of a single other language that has developer happiness as one of its stated goals. Although I don't have many opportunities to use Ruby these days, I still think that I was at my most productive when I did. Ruby (and Rails) taught me, among other things, that
π, I used to have questions like which language is better ? After discussing with my friends and listening to people online, I realized that Its better to stop asking these questions. Instead start asking which tool is better for current Job and Trend.
Choose the right tool for the Job.
C#orJavafor building enterprise and large applications.JSFyou can think of usingAnuglar orReactorVueetc. for Front End.Pythonfor Machine Learning.Gofor Micro Services based performant applications.In future maybe today's Languages and Framework may be outdated, so to survive you will be forced to learn new language of that time.
Conclusion:
Developer Happiness, stick to the language which make your life easier, like easy to read syntax, maintainable, has Good IDE. I like C# for current work, and its up-to you to decide what you like.
Its always good to be Open to learn any language as required and Choose the right tool for the Job.
Hope this helps.
Yup. Like Rust! Obviously Crystal, which is a statically typed Ruby mock-up I believe.
I think this is a key takeaway. I always hear people talking about how they are trying to create Rails for their given language, like JavaScript, but no one has quite hit the mark. It's called Ruby on Rails for a reason!
Like Ben, I am also still really enjoying developing in Ruby.
Laravel comes pretty close doesn't it? Although it seems that Laravel adopted a bit more of the "architecture" and "patterns" mindset of Java, and it's a bit more verbose (I admit you could say more clunky) than Ruby/Rails. But, when working with Laravel the feeling I get is pretty close to the feel of working with Rails.
Is
Rubymore readable and maintainable thanC#andJava, What are its advantages compared toC#andJava?Ignoring frameworks and libraries I would say this:
One thing I'd like to add for those who are put off by dynamically typed languages (scripting languages, usually). There's a project called crystal, which is a statically typed Ruby-based compilable language. So if you wanna learn Ruby but use it in a compiled language, consider crystal. It's still in pretty heavy development, it seems, but I've done some small projects with it. It's a little different, but I like it because of its Ruby syntax. I love Ruby.
Actually Ruby does not have functions at all. There are all methods.
They are all objects! :D
Procs are functions.
If you love Ruby in 2020, go join Crystal lang community, Ruby and Crystal should tinker with more cross-project collaborations.
Compared to the mantra of python. "There should be one-- and preferably only one --obvious way to do it". I wonder if that has constrained python developers :)
Matz (the creator of ruby) used to talk about the "Principle of least surprise" being this idea that if the way some language feature works doesn't surprise you, then you're happier for it.
Because of this idea Ruby has many MANY different obvious ways to do anything. This makes many different kinds of devs happy, because they can always write in the way that makes the most sense to them.
This is an amazing boon as a solo dev or a small team, but in larger settings this can be kind of a pain since a code base could become inconsistent pretty quickly unless the org enforces a kind of style.
Python takes the opposite approach.
That's probably why in the early 2010s there was a lot of (mostly comedic) volatility between the ruby and python communities
"Principle of least surprise" maps pretty well onto there should ideally only be one way to do something. If there isn't several ways of doing something it's not surprising :).
I was reading some ruby a while ago, and stumbled upon.
array << element. It took some serious googling to figure that one out, and I'm sure there are several ways you can write that too.I think the approach that ruby took is one of individuality. Imaging that the "one preferred way" of adding elements to arrays was
array << element.You'd be surprised that something like
array.pushwasn't working, and even more surprised thatarray << elementeven existed.Even though, in our hypothetical language, that's the only preferred way to push to arrays, it's still surprising.
If any of that made sense
It's fascinating to see how something like "principle of least surprise" can be interpreted and addressed so differently. The Ruby and Python solutions for this could not be more different.
Itβs especially interesting because both languages (python 2.7 at least) are pretty similar from a high level technical point of view.
Both OOP style languages
Both interpreted (usually)
Both very high level
Both dynamic
Both are even heavily used in web development
I still find it easiest to think in Ruby. Maybe that's because I have been writing it for so long, maybe it's because the standard lib handles many details I don't need to think about, and maybe it's just because it truly does live up to Matz's mantra of developer happiness.
All I know is that I still love writing Ruby too.
The way people talk about Ruby makes me want to learn this language so much
It's a pretty approachable, tons of resources I'd highly recommend you give it a go.
I agree on some stuff, disagree on others.
Most points you make about ruby resonate with me, I love the expressivity, the malleability - gives me options.
In theory it does allow me to explore a lot an solve problems in many different ways.
But does "ruby culture" really exist? Or all we have is "rails culture"?
Rails probably represents 95%+ of all ruby projects out there, with them often you get that aggressive rails culture of "the right way to do things is X" and suddenly fantastic language features are thrown out the window...
I'd like to be as optimistic as you are, I really do, but I'm almost out of faith here..
Agree that Rails monoculture isn't always great and can be dogmatic at times; however, the non-Rails (or Rails adjacent) ecosystem seems pretty vibrant to me right now. Hanami, Roda, Phlex, etc... lots of activity and cool stuff going on out there.
Benefits of Ruby's development happiness can be translated into it one key business metric: Development lead time. That is a important metric for businesses to stay a step ahead of the competitors especially for startups. I think that is why a lot of the new companies are still on RoR, even though people keep shxtting on it :)
Although I never coded in Ruby (Python dev) it would still be my second choice - I love Django and in many ways, Django is great because of RoR
Iβve heard Taylor Otwell say he pulled a lot of inspiration from for Laravel from Rails as well.
I still love Ruby and use it every day.
I never thought Python would bound back as it did.
I have used Ruby instead of Perl and Awk for 18 years already. π
I love Ruby...but I love Perl too!
I enjoy developing in rails and I wish I had the time to learn more.
After 3-4 years of coding in Ruby, I'm still learning new things.
I'm still learning new things after 10+ years with Ruby and Rails. The breadth of features has much to do with this I think. It may not be at the top of the hype cycle, but there are new and interesting things constantly happening in and around both Ruby and Rails.