4 ms·
Yeah, I'm also curious about how ruby would have faired. 15 years ago it was sillycon valleys poster child (but without being too harsh was actually a very good
by bjconlan 7y ago
Yeah, I'm also curious about how ruby would have faired. 15 years ago it was sillycon valleys poster child (but without being too harsh was actually a very good citizen and had perhaps had the best open and active community the internet era may have seen to date). It had many of the points corrected that have been outlined without stupid amount of corperate support java/.net have seen
- pjmlp 7y agoFor many of us it was a synonym to a very slow runtime and being the Rails' language. So why throw away the performance and graphical tooling of Java/.NET, when they shortly thereafter also got their Rails inspired frameworks? Personally having used an AOLServer inspired framework during the .com wave, meant that Ruby wasn't something I felt to be usable in production at scale, without wasting resources making it fast.