I mentioned a few already. Some more that I recently ran into, are in the niche of "verifiable credentials", SSI and DIID. A weird niche, but relevant to my current work.
There's plenty of work, references, implementations, type-systems for TS, Rust, Python and even .net. But nothing significant (a very few experiments at most) in Ruby.
There's little support for WASM, eventhough that's a promising tech to run and manage backend stuff as well as maybe someday client-side stuff already. There's little tooling to manage cloud infra in Ruby (Chef and Puppet still chugging along, but hardly as omnipresent as Ansible etc)
PHP, Python, Typescript: typing is emerging everywhere, albeit "bolted on". Ruby has efforts in this direction, but far behind the ones mentioned above.
There's no practical "frameworks" or libraries to make games. Very few frameworks or tooling to build desktop software. There's little effort around architectural concepts like Event Sourcing, Hexagonal architecture, Actors and so on. They are there, but I suspect overshadowed by Rails and far less used and documented than their counterparts in other ecosystems.
I actually dropped Ruby due to lack of typing, if Rails/Ruby gets static typing maybe people like me will come back.
Not every language needs/should have static typing, so sounds like you just found a better language for your own needs, doesn't mean Ruby has to change. Personally I think it's perfect as it is :)
But having worked with PHP and Python, who having typing annotations like Ruby can have through addons (sorbet) and might get to core someday, I would not go back to Ruby if it got this.
Typing annotations in PHP or Python are hardly useful to me. Their net benefits aren't there for me.
So, rather than trying to make Ruby (or Python, or PHP) like Rust, or .net or Java, why not just pick Rust, .net or Java instead?
When I don't need typing, I'll gladly pick ruby still. But when I do, I don't want to shoehorn Ruby into something it was never designed to be, but instead pick an option that has typing designed into its core.
Comments
Can you give me some examples? This seems like an interesting problem.
Examples of what? Missing gems?
I mentioned a few already. Some more that I recently ran into, are in the niche of "verifiable credentials", SSI and DIID. A weird niche, but relevant to my current work.
There's plenty of work, references, implementations, type-systems for TS, Rust, Python and even .net. But nothing significant (a very few experiments at most) in Ruby.
There's little support for WASM, eventhough that's a promising tech to run and manage backend stuff as well as maybe someday client-side stuff already. There's little tooling to manage cloud infra in Ruby (Chef and Puppet still chugging along, but hardly as omnipresent as Ansible etc)
PHP, Python, Typescript: typing is emerging everywhere, albeit "bolted on". Ruby has efforts in this direction, but far behind the ones mentioned above.
There's no practical "frameworks" or libraries to make games. Very few frameworks or tooling to build desktop software. There's little effort around architectural concepts like Event Sourcing, Hexagonal architecture, Actors and so on. They are there, but I suspect overshadowed by Rails and far less used and documented than their counterparts in other ecosystems.
I actually dropped Ruby due to lack of typing, if Rails/Ruby gets static typing maybe people like me will come back.
Another problem was lack of concurrency, I don't know if that is still an issue today.
Not every language needs/should have static typing, so sounds like you just found a better language for your own needs, doesn't mean Ruby has to change. Personally I think it's perfect as it is :)
Same here.
But having worked with PHP and Python, who having typing annotations like Ruby can have through addons (sorbet) and might get to core someday, I would not go back to Ruby if it got this.
Typing annotations in PHP or Python are hardly useful to me. Their net benefits aren't there for me.
So, rather than trying to make Ruby (or Python, or PHP) like Rust, or .net or Java, why not just pick Rust, .net or Java instead? When I don't need typing, I'll gladly pick ruby still. But when I do, I don't want to shoehorn Ruby into something it was never designed to be, but instead pick an option that has typing designed into its core.