I am one of those developers coding Java for a living, but day-dreaming of using Smalltalk instead. As such, the Redline project of course cought my attention and took a look at it.
I am no authority on Redline, but I think there is some confusion here that I could clarify. 2012/11/30 Marcus Denker <[email protected]>: > We will see… it's hard to implement a real smalltalk in Java (think about > #become:…), but I think Redline is not trying to be a full-fledged Smalltalk (not like the Squeak port to the JVM). It is more in the spirit of Amber. A Smalltalk-to-Java compiler, with some underlying runtime support. It does not aim at supporting the full enchilada :-) Are there some vital things that are impossible if #become: is missing? (no irony in my question, I just don't know) > I fear it will be even harder to follow where Pharo is going… Again, I think the comment was meant to mean that Pharo-based projects could be exported to the Redline source format, and made be to run there also. Not that Pharo (core) code will/can run automatically on Redline. Many things just will never run or not make sense at all (Fuel, Monti-/Metacello, Polymorph/Spec, NativeBoost, etc.) I for one welcome the possibility to be able to run Smalltalk in one more runtime-environment. Smalltalk should run everywhere! :-) On the other hand I am also aware that the experience of coding in Maven/Eclipse projects is just not the same as in an environment like Pharo. It is just... different. I found joy and sorrow on both sides ;-) Cheers, Sebastian
