undefined | Better HN

0 pointsjhancock14y ago0 comments

Don't see your update yet. But telling me that redline is running on JVM bytecode, is on its own, only mildly interesting. What evidence/argument do you have that Smalltalk without a traditional Smalltalk dev environment is any more interesting than a scripting language like Ruby?

0 comments

3 comments · 1 top-level

spooneybarger14y ago· 2 in thread

By traditional "Smalltalk dev environment", I assume you mean an image. If that isn't correct, then my entire response isn't going to be off base.

We are currently aiming for file based support with optional image support coming later down the road. Even in a file based system, we will have resumable exceptions and reloadable classes with the image.

The website is very much a work in progress, we do have a page up that attempts to answer some: 'Why the JVM' questions.. FAQ for things like 'Will you support an image' is still coming.

http://www.redline.st/discover/why-the-jvm.html

jhancockOP14y ago

Your "Why the JVM" info is solid. Your argument starts with "Joining the number #1 virtual machine with the number #1 language for getting things done is an easy choice." I will assert that Smalltalk is the #1 lang for getting things done because of its toolset/image. I'm not sure you get much value until you get to this point.

spooneybarger14y ago

There are plenty who feel as you do and plenty who don't. For people who feel as you do, we are going to be working on making sure that Pharo or another Smalltalk ( probably Pharo ) could be used as a development environment and Redline would be a deployment platform much like how many people develop for Gemstone's GLASS environment.

j / k navigate · click thread line to collapse