3 ms·
We can keep on adding... JavaScript, "We want a scripting language in our web pages." TCL, "It should be easy to extend your scripting language in C." SQL, "
by btilly 14y ago
We can keep on adding...
JavaScript, "We want a scripting language in our web pages."
TCL, "It should be easy to extend your scripting language in C."
SQL, "We need a standard way to talk to our databases."
PL/SQL, "We want to push complex logic into our databases."
BASIC, "We need an easy language for absolute beginners."
And so on.
But one historical comment. The ACTUAL problem that Ruby was created to fix was that Matz needed a scripting language that could handle Japanese text. People may adopt it now for different reasons, but that is not the historical inspiration.
- jeltz 14y agoPerl was made for processing text too, and for some reason he thought Perl was not good enough for the task.
- btilly 14y agoThe "some reason" that I gave is that handling Japanese byte encoded text in Perl was very hard in 1995.
- ColinWright 14y agoThe ACTUAL problem that Ruby was created to fix was that Matz needed a scripting language that could handle Japanese text. That's why it's on my enhanced chart.
- windsurfer 14y agoPerl can handle Japanese just fine nowadays. Back in 1995, though, Unicode support was... iffy at best. Now, Ruby must be differentiated by other things.
- btilly 14y agoThe issue was much worse than Unicode support. Ruby natively supports multipleincompatible Japanese encodings, including Unicode and shift-JIS. This is a lot harder than just marking off a Unicode checkbox.