Ruby metaprogramming made for some write-once-read-never codebases.
> about the size of life peoples let’s say
> live action role playing larger than life sage type of people
> Seems people just about the size of life
??
Statistics folks, data science peeps. Just needing to get things done, and not necessarily interested in--or aware of--programming ergonomics (for example).
> LARP
Personalities, like a Carmack. People we refer to just by name, due to technical agility, charisma, or sheer output.
I liked _why's stuff. The way he left is not how I would expect a persona to depart. There were some shifts in the programming landscape, and it led to a kind of forlorn sadness or mourning.
If I had to list others, Chris Crawford and Mark Pilgrim.
> Seems people just about... what's needed for language to flourish
Folks needing to munge data from CSV or Excel found python (and R, and other data libs) earlier, or more convenient to use; this built momentum as others tried Python instead.
Maybe also academia, python was there so it was taught. Another example could be students learned UNIX and brought it to their jobs. Same with Java.
I did a contract with a Rails shop and refused to renew it. Without Rails there's not a strong reason to use Ruby. It's a beautiful language, no doubt, but other languages fill its niche just fine (Python, PHP, js).
cpython has supported thread safety since last millennium, it's just slow is all
probably ruby, like lisp, is better for experiments to figure out what problem you're solving, but python (or, more so, golang or kotlin or typescript) is better for writing a maintainable solution to the problem once you more or less understand it
i think of python as favoring flexibility a bit more than i'd like, at the expense of comprehensibility and performance, but ruby is even more extreme along that axis
but probably random chance also plays a large role
Ruby had all the mindshare and hype over Python back then. To me as a Python fan, it felt like Python had peaked and wasn't going to grow further.
Then Node came along and stole the bandwagon followers that had flocked to Rails. The Ruby community was mostly the Rails community, so this kinda capped the growth of Ruby.
Python though had lots of competing Web frameworks, and other use outside webdev incl core tooling for Linux distros etc. Ansible (and Salt to a lesser extent) came along and stole back share from Chef/Puppet. Less fashionable Python kept on trucking along and was well placed to pick up machine learning.
AFAIK the .NET MVC setup was pretty influenced by Rails, but don't think Rails people went to .NET
I really doubt many Rails devs went to .NET. In those days Ruby was pretty bad on Windows machines (might still be?), and nearly all Rails devs were Mac users.
I never knew .NET MVC was Rails inspired - I always assumed it would've been closer in style to the older Java MVC frameworks Rails was keen to disrupt in the beginning.
Python was there first, and took a very long time to gain its hegemony. Pandas and Jupyter could in principle have been built on Ruby: why weren't they? Python suffered massively in the 2->3 transition and has only just begun to essay thread-safety, which both should have given Ruby a leg up.
Was it a core implementation group's superior openness to the needs of such projects?