News for hackers. Stuff that matters.
Re:What Languages Fix (2002) by btilly on Friday December 21, 2012 @05:36PM (#4954885)
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.

Re:What Languages Fix (2002) by ColinWright on Friday December 21, 2012 @05:49PM (#4954941)

    The 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.
Re:What Languages Fix (2002) by windsurfer on Friday December 21, 2012 @06:09PM (#4955006)
Perl can handle Japanese just fine nowadays. Back in 1995, though, Unicode support was... iffy at best.

Now, Ruby must be differentiated by other things.

Re:What Languages Fix (2002) by btilly on Friday December 21, 2012 @08:54PM (#4955461)
The 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.

Re:What Languages Fix (2002) by jeltz on Friday December 21, 2012 @05:40PM (#4954900)
Perl was made for processing text too, and for some reason he thought Perl was not good enough for the task.
Re:What Languages Fix (2002) by btilly on Saturday December 22, 2012 @01:50PM (#4957161)
The "some reason" that I gave is that handling Japanese byte encoded text in Perl was very hard in 1995.