Well if you want to work on redline and improve it , none will stop you, its a free... software... afterall ;)
Simply complaining about things wont change much if anything. Frankly If I ever wanted to use Java libraries for any reason , I would not give up on Pharo just to use another pharo implementation which may or may not work as I expect it. I suspect most Pharoers would agree with me as well :) I rather do this from the comfort of my gorgeous pharo enviroment :) The latest commit in redline was back in October 2013 https://github.com/redline-smalltalk/redline-smalltalk/commits/master On the other hand JNIPort had some recent commits by Tudor http://www.smalltalkhub.com/#!/~JNIPort/JNIPort/commits and it now supports pharo 5. Personally I dont care about making pharo more popular , I care about making pharo more.... pharo. I am very interested into live coding and visual coding. JVM is not invested on these areas, it has a very different mentality so porting pharo there is not something that interests me. Java with its huge popularly does not impress me as much pharo does in terms of flexibility, functionality and directness. I think that is why its difficult to bring pharo to diffirent platforms, the mentality of pharo and mentality of smalltalk is so specific that does not fit easily into other platforms. On Sat, Dec 12, 2015 at 7:17 PM horrido <horrido.hobb...@gmail.com> wrote: > I looked at JNIPort. It's **very** limited in its capabilities. "Improving" > it may be an insurmountable task. > > Redline's approach was very attractive. Relatively clean and elegant, and > quite capable. It's a pity James Ladd couldn't get back to the project. > > > > -- > View this message in context: > http://forum.world.st/PharoJVM-tp4866633p4866737.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >
