Why Should You [Still] Choose Ruby on Rails to Develop Your Product in 2023
mobidev.biz
mobidev.biz
> Ruby serves for functional programming and web development, while Python has found application in different branches of AI and academic programming.
> Ruby is 100% OOP language, while in Python these principles are implemented only partially.
> Principles of declaring variables and working with them differ.
Well, jeez, if I have to work with the variables differently, then...
Who wrote this? The bookkeeper?
Thank you for a good laugh!
I had a stressful day and your comment made it much better.
Django is frontend agnostic so you can use whatever flavor of the month you like. (For better or worse hahaha)
Update: To be clear, I think Rails is a fine choice. I just don't think there is much of a reason to use it over Django these days unless you already know Ruby and don't know Python.
:)
And probably Laravel as well. And maybe Spring Boot.
I love Ruby, but Elixir/Phoenix is the natural next step after Rails.
Elixir & Phoenix are great, but I'm quite confident whatever you're doing in Elixir/Phoenix - you could, with minimal effort, also do in Rails.
The reason to use Elixir/Phoenix is not because of pattern matching - it's because of the BEAM VM.
If you don't need it or want it - you're probably better off with Rails.
Why do you say you'd prob be better off with rails?
If you don't want or need that, there's really no reason to use Elixir/Phoenix.
Ruby on Rails is much more widely used - so you're going to be able to find more community support & libraries & integrations than you will with Phoenix.
Why tie your hands behind your back if you don't need the BEAM?
Pattern matching does streamline a lot of logic, which is a big reason Ruby added it in version 2.7, three years ago. But, while, there are reasons I can see that one might prefer Elixir/Phoenix today, “you can write less logic because pattern matching is available in Elixir” isn’t particularly one of them.
This hasn't been the case for some time. By default, you can't pass in raw parameters from a request in a controller into a model. You have to either allow-list specific fields or create a hash from the parameters.
You have to intentionally bypass this security feature to get a vulnerability.
Recommend using brakeman to catch these kinds of mistakes. :)
It's like ChatGPT has turn the tables and is trying to provoke us into saying something not nice...
- Is Ruby on Rails dead or still alive? - Why leverage Ruby on Rails in 2023? - When to use Ruby on Rails and when to shun it in favor of more competitive technologies?
If you are just there for the money however (VCs, HN, github stars, ...), trying to make an MVP and run, just go with the shiny and trendy.
im still struggling. there's a lot of magic happening. i'm not bad with the ruby language itself. but i"m so used to first principles. im open to suggestions on improvement here
I personally just don't like Rails. I find it annoying at best, and utterly infuriating at worst.
It's a modern ASP.net - if you want to do dead simple things, Rails does the job quickly and easily, with lots of nice generators, and simple drop in tools.
If you want to do anything outside the happy path, you need to know the entire framework like the back of your hand, because you'll need to unwind the magic and they shoved far too much magic into what should be a simple thing.
And just like ASP.net - the magic changes every version because "best practices" for the web are also changing incredibly quickly. What magic incantation you need depends on which version of the framework you're running, and the docs are bad on this front.
I get Rails - but it is very much not my cup of tea. I don't want to learn their specific DSL and unwind all their magic when I already understand the topic at hand, and just want it to do the thing I'm asking it to.