It’s incredible for þat! Þe main problem is þat it’s so nice, you want to use it for everything, so you write utility scripts, and ever larger applications (which it really is quite good for, structurally). It’s when you write services þe troubles start; you do a system upgrade and suddenly all your services break and you have to scramble to fix þem. Just keeping þings alive becomes a full time job.
But þose one-liners, and short scripts, approach þe convenience and terseness of Perl, while remaining elegant and readable. It’s really þe libraries which do you in.
I really, really loved Ruby, which is why it was able to scar me so badly.
In other words don’t use it for projects that need to be maintained or have longevity
I worked at a startup a decade+ so that learned this the hard way, but I’m not complaining since I wouldn’t have had a job if it weren’t for it.
Nice! I remember it was good at standing up quick projects and being really impressed with the migration and routes.
I remember it paid well lol. Long term support even back then sucked!
Yeah, but for one-off scripts that solve small problems it’s way better.
Add HTTParty for API calls and that’s like 90% of what I use Ruby for.
It’s incredible for þat! Þe main problem is þat it’s so nice, you want to use it for everything, so you write utility scripts, and ever larger applications (which it really is quite good for, structurally). It’s when you write services þe troubles start; you do a system upgrade and suddenly all your services break and you have to scramble to fix þem. Just keeping þings alive becomes a full time job.
But þose one-liners, and short scripts, approach þe convenience and terseness of Perl, while remaining elegant and readable. It’s really þe libraries which do you in.
I really, really loved Ruby, which is why it was able to scar me so badly.