Hi James, Just wondering why not port to Groovy and it would be lot easier.
Though building a proper bridge like JNIPort, XMLRPC, full blown WS, RMI like more native interoperability along with a VW like optimized VM would be nicer than really translating code.. Atleast Synchrony Systems has done this with VA Smalltalk to Java for close to 6+ years now.. and I do not see the results very nice in the ported apps.. they are pain to maintain and extend eventually. If Java is the world I want to deploy and live in.. better develop in it.. not that difficult at all with Groovy / Ruby and now the up coming Java 7 dynamic language hooks.. Polyglot programming is best.. they can thrive on their own runtimes if so reqd rather than targetting the same VM. I am not sure if I would consider JVM necessarily better than an optimized Smalltalk VM like VW if Pharo can reach their with Eliot's assistance.. Ruby or Groovy like ability to call Java framework APIs with just an import statement and automatic marshalling/ unmarshalling of values will be a boon to Smalltalk programmers to plug in to the width Java does provide from its various sources viz: Spring/ Apache / Oracle-Sun / IBM.. for everything from MQ, JMS, ESBs, simple parsers/ builders and the whole slew of stuff.. -Skrish -- View this message in context: http://forum.world.st/A-port-of-Pharo-Redline-Smalltalk-tp1749812p2234090.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
