@NEETzsche Genetic algorithms... I remember implementing them in C almost 20 years ago. Nostalgic memory.
@crunklord420 You can repeat that it’s dead until you’re blue in the face but that doesn’t make it so. I agree with you that if I were to start a back end project today I would not use Rails, but I also know for a fact that a lot of companies are because they keep trying to recruit me for new projects that are going to be written in Rails based on experience on my resume from like a decade ago. These aren’t maintenance projects but actual new things from scratch. Once you get into industries that aren’t obsessed with tech sperging Rails still has a lot of credibility that Django just doesn’t.
I’ve done a little bit of open source work for Pleroma to pick up Phoenix because I would like to jump ships to it, but the truth is actual companies in the real world want to hire for things that do not correlate to Google search result data. They don’t even want my .NET experience and I have more of that than Ruby.
If you really believe that Rails is dead, in the sense that nobody is making new projects with it, you’re in for a very rude awakening when you go out there and the rubber hits the road. JavaScript backends are deader than Ruby backends by a long shot.
@colonelj there is already a well-developed enough foreign program that’s written in Ruby called Discourse. So he may have meant running that.
@crunklord420 I’m really not a fan of Discourse. It’s written in Rails.
@crunklord420 I’ve been meaning to pick up Rust, but even now it just doesn’t have the momentum Ruby does, unfortunately. It looks cute, though, in spite of the trannies into it
Man I haven’t seen much with genetic algorithms in a while. I should get back into that.