Is Django actually worth learning? What about any of those NodeJS backend frameworks? How about any of the Go backend frameworks? Is it worthwhile to get back on the framework treadmill right now as a Rails guy?
@alex Gatsby is a frontend. I've done a little bit of Phoenix work just by dint of fiddling with Pleroma and writing a few MRFs. What's the point of picking up Phoenix really? Does it make you more hireable?
There's another concern that I have with Phoenix and that it is not as mature as Rails, or Ruby, the language it's written in. Whenever I want to do something that is non-trivial, I just type in whatever that thing is and then "Ruby gem" into Google and I almost always get something that works pretty well. It's actually what kept me in Ruby as long as it has, alongside the fact that once you get over Ruby's learning curve the language is quite elegant.
When you combine the maturity of both rails and basically the entire Ruby world with the fact that Ruby code is actually very elegant to read, it does for the most part makeup for its performance flaws. It's why I'm pretty reluctant to accept it face value claims that it's "dead."
@NEETzsche Gatsby isn't a frontend, it's a way to build static sites with React. It compiles React code into plain HTML pages that don't require any JavaScript to run.
Phoenix is good because of Elixir. But you're right that it's less mature.
I think the main argument in favor of something like Elixir is precisely that it’s more performant than Ruby, but if I were to lean into performance as an argument for something I’d probably pick up Rust or Go instead. I know that functional spergs will wig out at me for that but it’s true.
I really like Ruby “metaprogramming” too. Something about it is just so… muah, so sweet. But then again, that might just be my own acclimation to it speaking.
@NEETzsche In Rust and Go you have to think harder about scaling. Elixir makes vertical scaling an afterthought because it does a lot of the work for you.
I’ve been on the fence with this shit for years now. All these meme languages and frameworks and shit, with this expectation that I give a shit about them when they all just do permutations on the same handful of things.
Actually the main reason I’m even bringing this up is marketability. Everything I intend to write I can write in Rails, and everything else I want to write but don’t intend to I could write in C. That doesn’t leave much of an argument for these meme frameworks/languages outside of money.
@NEETzsche@alex I understand that. And unless you choose something and commit, the list grows monthly.
I'm going to have to commit to something. I can't learn every framework and language, and I'm planning to dump $EMPLOYER in the first half of next year, even if I wind up working at Home Depot.
@dcc I mean, a lot of nice projects use a lot of things. A great deal of things I want to do really can be implemented with fucking Ruby on Rails. I'm kind of doing a marketability query in this thread if I'm being honest with you