[flagged]
[flagged]
[flagged]
Ruby Together
61–70 of 86 posts
Re: Ruby Together
#62I'm a a typescript/java engineer. I would say my lifetime code stats are probably around 40% JS / 35% Typescript / 15% Java / 8% Python / 2% other. That is to say, I've barely ever written any Ruby outside of the occasional little script. And yet it's secretly my favorite language. I wish I wasn't afraid that demand for it would vanish over time, which makes me reluctant to invest skills in its ecosystem. It seems so…
I'll be honest, I'm worried too. I'm a fullstack dev, but I consider myself a decent rubyist. I've been writing it for about 10 years and have spoken at rubyconf a few times. All else being equal, I just like the language itself. The points others make here are true, there are a ton of ruby shops, and demand for someone with a couple years of rails experience is still quite high. But the issue is not where ruby is no…
I think the crucial factor is async/concurrency. With the explosion of mobile sudden growth is a bigger possibility and the microservice architetcure caters for that. Languages like Node and Go have an advantage over Ruby here. Ruby 3 has addressed the async concerns to some extent but it's unlikely that Rails will ever be based entirely on async Ruby and the MVC model doesn't lend itself to micro services so well.
Re: Ruby Together
#63Last week I compared RubyOnRails (RoR) and Python Django. For rapid prototyping, I think RoR has still something to say. I like Django but I see little use (correct me, if I am wrong) from big Startups. I was able to setup a tiny custom status page with RoR picking a module found on the web, and starting customizing the app for my own goals. AngularJS and React are the king on the frontend in this years, so the Djang…
I personally see a lot more for Django than Rails, but then again I know Django and don't know Rails (been meaning to learn it for a long time) so that could be biasing me
Yes. Indeed.co.uk has had more Django than Rails jobs for a long time now but recently the gap has dropped from 70% to 30% so maybe Ruby 3/Rails 7/Hotwire has generated more interest.
Re: Ruby Together
#64Last week I compared RubyOnRails (RoR) and Python Django. For rapid prototyping, I think RoR has still something to say. I like Django but I see little use (correct me, if I am wrong) from big Startups. I was able to setup a tiny custom status page with RoR picking a module found on the web, and starting customizing the app for my own goals. AngularJS and React are the king on the frontend in this years, so the Djang…
My take is that Django is stronger for websites: leaning slighly more towards a selfbuilt CMS. Whereas Rails is stronger for webapps. With a large overlap, and only slightly so. But that both lack severely for complex business flows, -logic and integrations. Both are strong for CRUD cases, with accidental workflows attached to those operations. But that both lack tooling, and have the wrong architecture, to support c…
Compared with what? Spring? ASP.Net?
Re: Ruby Together
#65I love that the ecosystem is starting to grow again. I'm doing my part in building fantastic developer tools I'd love if Rails' ecosystem becomes more vibrant like Laravels'
I think a major holdback for Ruby, is how tightly it is coupled to Rails. Comments like this show how the community, unconscious, ties them together too. I think for Ruby to truly thrive again, it must become more than 'the language rails was once written in'. I'm a Ruby developer. I don't particularly like Rails (but don't hate or avoid it either) and I'm more and more convinced that Rails is doing Ruby more harm th…
On the contrary, I think Rails continues to sustain the Ruby ecosystem. It's not like there aren't alternatives such as Sinatra and Grape for microservices. There are also plenty of non-Rails Ruby jobs. If you search for `ruby -rails` on Indeed.co.uk there are 1879 results so 1503 when you factor-out 10% for unrelated results.
Re: Ruby Together
#66Ruby is so wonderful. For me and the type of software I write it makes developing a lot less miserable. I think there will be a serious renaissance of Ruby in the coming years as people get fatigued with the constant churn of languages and frameworks.
Re: Ruby Together
#67I'm a a typescript/java engineer. I would say my lifetime code stats are probably around 40% JS / 35% Typescript / 15% Java / 8% Python / 2% other. That is to say, I've barely ever written any Ruby outside of the occasional little script. And yet it's secretly my favorite language. I wish I wasn't afraid that demand for it would vanish over time, which makes me reluctant to invest skills in its ecosystem. It seems so…
When I was contracting full time, a _very_ large portion of my time was paid for in Rails work. Something like 90%. I market myself as a true generalist, basically a CTO-for-hire, and still the contracts I landed almost always involved Rails in some way.
Re: Ruby Together
#68Earlier quoted context omitted.
I understand job security and demand is important. But for me the most important has always been to enjoy myself as much as possible. That's also how I can do my best every day. If that means having a 10% lower salary or half the number of job postings I'm fine with it. If I really needed to find a non Ruby job I'm sure I still could, there's enough demand in general.
This is similar to my take, only I never ever want to work with Ruby, since it just rubs me the wrong way. This is a throwaway comment unless you care about the following question. What is the the fundamental difference between Ruby and Lisp enthusiasts? The easy answer is OOP vs FP, but as soon as you dive into the details the distinction becomes more difficult. A thread [vs] between Alan Kay and Rich Hickey is perh…
Before embarking on my programming career, I went through HtDP while I still had time to do stuff like that. So I got a bit of grounding in Scheme. Regardless, when I discovered Ruby, I jumped on it and to this day I prefer to use it over any flavor of Lisp. In the end, I really think it comes down to syntax. I much prefer a normal, imperative kind of workflow. You lose a little bit of power and flexibility over Lisp but the friendliness of having verbs, nouns and diverse semantics wins out over what feels like a monotonous landscape. As you say, the underlying language semantics are largely similar, expressivity is just very similar. So the only thing left is syntax, and when you talk about syntax, you're talking about the most aesthetic part of the language, the part that's hardest to describe and reason about.
Re: Ruby Together
#69Last year Ruby Together, which primarily supported Ruby packages & infrastructure, merged into Ruby Central, which runs the main Ruby & Rails conferences as well as key Ruby infrastructure (Rubygems) https://rubytogether.org/news/2021-10-21-ruby-together-and-r... http://rubycentral.org/
I heard about this at Boulder Ruby last night. Sounds like there's some good things coming down the pike from this.
Re: Ruby Together
#70Earlier quoted context omitted.
My take is that Django is stronger for websites: leaning slighly more towards a selfbuilt CMS. Whereas Rails is stronger for webapps. With a large overlap, and only slightly so. But that both lack severely for complex business flows, -logic and integrations. Both are strong for CRUD cases, with accidental workflows attached to those operations. But that both lack tooling, and have the wrong architecture, to support c…
Compared with what? Spring? ASP.Net?
Compared with "No Framework".
Spring, ASP.net, Rails, Symfony, Django all follow very much the same patterns and architecture.