Really depends honestly. The decision you make for your product in the first years are rarely the right ones for your product of the years after that.
Rewriting will often happen no matter which language you choose once you really start to scale. You don't build an MVP in micro services running on a Kubernetes cluster, that's just over-engineering.
It's a common mistake, but what you think the direction is at the MVP step WILL NOT be the direction a few years after that.
Locking oneself into a specific techno is not good, choose the right ones for the right stages and evolve continuously instead of investing 3x the price in your solid future-proof MVP when 90% of products don't even reach that "future"
Yep of course, but choosing rails and coding in rails involves flexing a brain muscle that probably isn't worth flexing. Ruby was a lovely language but time hasn't been kind to it. Best off forgetting it now and solidifying better faster, more modern, easier and more flexible languages and frameworks in 2021.
Let's just agree to disagree 🤷 To me Rails is the definition of easy, you don't need to flex any muscle since everything is done for you, perfect for fast iteration ! I guess we just had different experiences with it, and that's ok, I don't think it's meant for everyone, just like MacOS's """Simplicity""" can turn off a lot of people (including me).
No matter how easy something is you're still "flexing". The more you use your brain on any task the more you remember how to do this kind of task and forget other types of task. So using ruby at all anymore is just a waste of thought and training that you could be using on something that actually has a future. Ruby is like an abusive relationship right now. It may feel good but it's letting you down, it's not doing a good job, and it's not going anywhere good. Leave it before it leaves you.
Ahaha I see what you mean, a bit dramatic but I get where you're coming from. I agree that Ruby is not objectively the best language to work on in terms of future (pretty good in terms of career though if you can go international, since there's so few of us and no competition, but only works for the next 10 years I guess).
If you like the Ruby syntax and ethos more than the other languages though, just go for it... Life is not always about optimization, it's about having fun as well ! And Ruby is definitely fun 🤡
If you want to optimize your career path like crazy and don't really have any preferences, by all means, go JS, Python, Rust and all that jazz ! I don't really need to optimize my career so I just focus on what I like doing and what makes me happy ☮
I really liked ruby too, until they really messed up building a type system. But it's not just about optimising for your career (although that is really important, money makes life easier), it's optimising your present and your future.
I love programming languages so much, and that's why I want to keep evolving, helping my career is just a byproduct of that.
I'm just disappointed the creators of ruby were so bad at evolving the language that it got trounced by things that came about much later. So much wasted promise. If you're enjoying hanging out on your sinking ship then by all means hang around for a bit longer, but don't fool yourself long enough that you drown with it.
Really depends honestly. The decision you make for your product in the first years are rarely the right ones for your product of the years after that.
Rewriting will often happen no matter which language you choose once you really start to scale. You don't build an MVP in micro services running on a Kubernetes cluster, that's just over-engineering.
It's a common mistake, but what you think the direction is at the MVP step WILL NOT be the direction a few years after that.
Locking oneself into a specific techno is not good, choose the right ones for the right stages and evolve continuously instead of investing 3x the price in your solid future-proof MVP when 90% of products don't even reach that "future"
Yep of course, but choosing rails and coding in rails involves flexing a brain muscle that probably isn't worth flexing. Ruby was a lovely language but time hasn't been kind to it. Best off forgetting it now and solidifying better faster, more modern, easier and more flexible languages and frameworks in 2021.
Let's just agree to disagree 🤷 To me Rails is the definition of easy, you don't need to flex any muscle since everything is done for you, perfect for fast iteration ! I guess we just had different experiences with it, and that's ok, I don't think it's meant for everyone, just like MacOS's """Simplicity""" can turn off a lot of people (including me).
No matter how easy something is you're still "flexing". The more you use your brain on any task the more you remember how to do this kind of task and forget other types of task. So using ruby at all anymore is just a waste of thought and training that you could be using on something that actually has a future. Ruby is like an abusive relationship right now. It may feel good but it's letting you down, it's not doing a good job, and it's not going anywhere good. Leave it before it leaves you.
Ahaha I see what you mean, a bit dramatic but I get where you're coming from. I agree that Ruby is not objectively the best language to work on in terms of future (pretty good in terms of career though if you can go international, since there's so few of us and no competition, but only works for the next 10 years I guess).
If you like the Ruby syntax and ethos more than the other languages though, just go for it... Life is not always about optimization, it's about having fun as well ! And Ruby is definitely fun 🤡
If you want to optimize your career path like crazy and don't really have any preferences, by all means, go JS, Python, Rust and all that jazz ! I don't really need to optimize my career so I just focus on what I like doing and what makes me happy ☮
I really liked ruby too, until they really messed up building a type system. But it's not just about optimising for your career (although that is really important, money makes life easier), it's optimising your present and your future.
I love programming languages so much, and that's why I want to keep evolving, helping my career is just a byproduct of that.
I'm just disappointed the creators of ruby were so bad at evolving the language that it got trounced by things that came about much later. So much wasted promise. If you're enjoying hanging out on your sinking ship then by all means hang around for a bit longer, but don't fool yourself long enough that you drown with it.
You can't sink when you have a whole armada of boats 😎
There's no armada, just a waste of time and a waste of priorities: youtu.be/_F2k1zwDymw
You're pretty stubborn.. I was hinting at the fact that when you work with multiple programming languages, you're golden. No waste of time here