I'll name a few. Ruby really did capture me in this way. Being able to type irb into a terminal and then type "hello".upcase and see HELLO right there was really refreshing and spoke to me. I've been writing Ruby ever since.
In my brief experimentation with Flutter, I was quite impressed by the attention to developer experience that the developers are going for with this environment. I haven't done any production-oriented work, but if I went back to Flutter the experience would be a big reason for it.
Also "did you mean ... ?", Gotchas, syntactic sugar and Active Record in general. Coming from the .Net world where we have to write getters and setters even for the simplest model to this magical world where you can just code a db and a few relationships and everything just magically works. I sometimes get imposter syndrome while writing Ruby / RoR because everything is so easy and I feel like anyone could write a website in a few days. Of course it's not true, but it goes to show how uncomfortably good Ruby makes me feel.
From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
Never said it wasn't easy, just that you /have/ to. Even if it's small, my point is that it's redundant. In Ruby on Rails, you don't have to do that, it automatically generates most of the methods you need just by reading your database.
For most of my time, I was writing in Python.
I really loved it and was able to argue for Python for hours.
I thought would never prefer another language when I had a choice.
Well... I was wrong.
In current job, I met Ruby (or Rails, to be specific) for the first time.
It seemed nice, easy to learn after Python, had some nice features.
I didn't realize how much comfortable and elegant it is before I did some work on my hobby project in Python.
It's still good, but there were multiple moments when I thought "well, I could write this much nicely in Ruby, shame Python doesn't do this".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'll name a few. Ruby really did capture me in this way. Being able to type
irb
into a terminal and then type"hello".upcase
and seeHELLO
right there was really refreshing and spoke to me. I've been writing Ruby ever since.In my brief experimentation with Flutter, I was quite impressed by the attention to developer experience that the developers are going for with this environment. I haven't done any production-oriented work, but if I went back to Flutter the experience would be a big reason for it.
I agree, Ben. I have done some Flutter work and it was a pleasure to work with.
Also "did you mean ... ?", Gotchas, syntactic sugar and Active Record in general. Coming from the .Net world where we have to write getters and setters even for the simplest model to this magical world where you can just code a db and a few relationships and everything just magically works. I sometimes get imposter syndrome while writing Ruby / RoR because everything is so easy and I feel like anyone could write a website in a few days. Of course it's not true, but it goes to show how uncomfortably good Ruby makes me feel.
Unclear when you last worked with .NET.
T PropName { get; set; }
is not really that difficult.Never said it wasn't easy, just that you /have/ to. Even if it's small, my point is that it's redundant. In Ruby on Rails, you don't have to do that, it automatically generates most of the methods you need just by reading your database.
For most of my time, I was writing in Python.
I really loved it and was able to argue for Python for hours.
I thought would never prefer another language when I had a choice.
Well... I was wrong.
In current job, I met Ruby (or Rails, to be specific) for the first time.
It seemed nice, easy to learn after Python, had some nice features.
I didn't realize how much comfortable and elegant it is before I did some work on my hobby project in Python.
It's still good, but there were multiple moments when I thought "well, I could write this much nicely in Ruby, shame Python doesn't do this".