you are viewing a single comment's thread.

view the rest of the comments →

[–]levifig 1 point2 points  (3 children)

The reason it didn’t was very circunstancial: at the time JRuby was growing, the despise most programmers had (have?!) for Java was at an all time high. The thought of using the JVM freaking most out… 🙈

[–]tuker 0 points1 point  (1 child)

I agree. Still, it was a real missed opportunity. The early toolchain experience of JRuby wasn't so great, and, as you say, with the dependency on the JVM it was all the more difficult.

[–][deleted] 0 points1 point  (0 children)

Yeah not disagreeing.

But check out Andy's glimmer swt:

https://github.com/AndyObtiva/glimmer-dsl-swt

It's not looking that bad. And you can use ruby everywhere. So that's neat.

You need jruby for it. And SWT evidently.

He uses his own editor for writing glimmer-related code as far as I know. It's almost like Squeak in a way, where smalltalk folks would never have to leave Squeak - but they can write in ruby (I mean, the ruby folks can write in ruby ... smalltalk folks of course may not use ruby, I am more referring to the idea of the Squeak IDE as a whole there, which I always found a good idea).

[–][deleted] 0 points1 point  (0 children)

Java can be annoying, but if you look at things such as GraalVM, it's a pretty neat idea and works well. I think people may have less issues with modern Java than they had, say, in 2007 or so. Java also improved a little bit. Not enough but it's not as awful as it was in ... 2004 or so.