Live data from Hacker News

Where is Ruby Headed in 2021?

bignerdranch.com

131–140 of 360 posts

Re: Where is Ruby Headed in 2021?

#131

Earlier quoted context omitted.

Could you elaborate more? Your comment doesn't make much sense otherwise - if anything I'd argue that NOT tying yourself to a single framework is what makes you grow into a senior developer. I'd argue that Python (or similar) back-end and JS-flavor front-end is a better path to growing since it's just a much wider area of growth.

Updated my original comment to include my story. Once learning Ruby/RoR techstack, you can jump to all other techstack in NO time as it already taught you everything you need. The rest is ecosystem and syntax. About your concern, other frameworks/languages offer you only part of story, Ruby and RoR offers you complete story in a concise way, it's the difference.

I would argue that’s anything. I started by web service development career in C# and moved to Python and Rails was easy enough to figure out except for the magic junk.

Most systems use similar-enough patterns you can carry them over where-ever. It doesn’t have to be rails, but it was for you.

Re: Where is Ruby Headed in 2021?

#132
post #51

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

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 frameworks with a lot of excitement behind them. But will it take over Ruby? Probably not.

Re: Where is Ruby Headed in 2021?

#133

Earlier quoted context omitted.

Updated my original comment to include my story. Once learning Ruby/RoR techstack, you can jump to all other techstack in NO time as it already taught you everything you need. The rest is ecosystem and syntax. About your concern, other frameworks/languages offer you only part of story, Ruby and RoR offers you complete story in a concise way, it's the difference.

I would argue that’s anything. I started by web service development career in C# and moved to Python and Rails was easy enough to figure out except for the magic junk. Most systems use similar-enough patterns you can carry them over where-ever. It doesn’t have to be rails, but it was for you.

Because the ease of installation of Ruby, RoR and deployment to Heroku. It's cross-platform. So u can bring your application to production in like 30 mins.

In era 2010, .NET stack couldn't offer you that.

I wrote about 4 production application in Ruby stack in 6 months, it's super productive and the Ruby language has OOP/FP done right in comparison of other languages, too.

Re: Where is Ruby Headed in 2021?

#134

This is really cool. I’ve used a number of languages and dabbled in a few frameworks but nothing I’ve used brings me joy like ruby does. I approach programming creatively. I think in large systems and architecture. Ruby allows me to skip worrying about the details. Code blocks abstract away thinking about loops and just focus on data. Just about every array operation I could want is there, waiting for a code block. I…

Bet one entire language's future on a single framework isn't working very well I guess.

It is 2021, web frameworks are ... one of the solved problems. Polyglot is the future, and people are already adapting

Re: Where is Ruby Headed in 2021?

#135

Earlier quoted context omitted.

Honestly typeorm and nestjs are pretty bad.

NestJS has some pretty horrific default settings, like a max 1MB request payload size. And you have to write custom content-type processors for anything other than 'application/json'. So if you're doing say, file upload's over 1MB, you already have to make 2 configuration changes. But you wouldn't assume that OOTB 1 MB file upload isn't supported for what claims to be a full nuts-and-bolts web application framework.

> a max 1MB request payload size

How would that be a bad default, when it's probably more than sufficient for 99% of the use cases out there? It's even the same default as nginx: https://nginx.org/en/docs/http/ngx_http_core_module.html#cli...

Nest.js is clearly targeting JSON-based CRUD apps, and the defaults are pretty good. File uploads through JSON is not as simple a problem as you try to make it. Are you using bas64 encoding and embedding it in the JSON? Are you using multipart/form-data?

Re: Where is Ruby Headed in 2021?

#136
post #50

Earlier quoted context omitted.

The downside is the ecosystem turning into the JS/TS ecosystem. Where the zealots have pushed TS to the point it all just looks like C# and what makes JS nice is being lost.

1. What's wrong with C#? 2. What made JS uniquely nice? I wanted to leave these questions entirely open to answer, but I'll add my own opinion on (2) because I feel compelled: nothing, JS is quite possibly the worst language ever designed. Certainly the worst in widespread use.

Why is JS one of the worst languages ever designed? I've used many languages and JS is one of the better designed ones in my opinion.

Re: Where is Ruby Headed in 2021?

#137

Earlier quoted context omitted.

I would argue that’s anything. I started by web service development career in C# and moved to Python and Rails was easy enough to figure out except for the magic junk. Most systems use similar-enough patterns you can carry them over where-ever. It doesn’t have to be rails, but it was for you.

Because the ease of installation of Ruby, RoR and deployment to Heroku. It's cross-platform. So u can bring your application to production in like 30 mins. In era 2010, .NET stack couldn't offer you that. I wrote about 4 production application in Ruby stack in 6 months, it's super productive and the Ruby language has OOP/FP done right in comparison of other languages, too.

I worked in Microsoft shops for the majority of my early career, so cross-platform didn't matter to me.

C# had task-based async and a very good, compared to the competition in Java, database framework to work with. Seriously, how doesn't Java have named parameters yet?

Re: Where is Ruby Headed in 2021?

#138

Don't get me wrong. I'm happy to see type declaration support in Ruby and have sorely missed it working on long-lived Rails codebases. But it is pretty funny that after years of rah-rah about how static typing was a pointless barrier to productivity, all the "duck-typing" languages have eventually added it after all.

There's something swingy about society. dynlang were freedom from cpp/java style, until other typing ideas came up, and now it diffuses in dynlangs that want clarity over conciseness (until the ml family takes over with single variables fully typed category theory web4 framework)

Re: Where is Ruby Headed in 2021?

#139

Earlier quoted context omitted.

> I’ve tried python, but I end up having to deal with the mess of importing modules Without those imports, how will people reading the code find the definitions? How will they track down the source code for all the methods being called? If the answer is "with an IDE / tools", then can't those same tools be used to solve the "mess of importing modules"? If you're using a good IDE, imports and go-to-definition are both…

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.

This magic is delightful in small codebases I’m familiar with and absolute hell in large codebases I’m not familiar with

Re: Where is Ruby Headed in 2021?

#140

This is really cool. I’ve used a number of languages and dabbled in a few frameworks but nothing I’ve used brings me joy like ruby does. I approach programming creatively. I think in large systems and architecture. Ruby allows me to skip worrying about the details. Code blocks abstract away thinking about loops and just focus on data. Just about every array operation I could want is there, waiting for a code block. I…

Bet one entire language's future on a single framework isn't working very well I guess. It is 2021, web frameworks are ... one of the solved problems. Polyglot is the future, and people are already adapting

> Polyglot is the future, and people are already adapting

Yes, right. I like how you can read into the future. Let's see what happens 10-20 years from now, things tend to change. But even if we look at how things are now, plenty of places still commit to 1-2 languages (in fact if you're a small shop it's pretty crazy to try anything else).

Post reply on HN