New member, couple of questions :)

"J J" <[email protected]> Sat, 12 May 2007 08:13:39 +0000
Newsgroups gmane.comp.lang.smalltalk.strongtalk
Message-ID <[email protected]>
Hello all,

Glad to see that work is picking up momentum on this project.  Personally, I 
have done a lot of C++ and feel pretty comfortable with it, but I have not 
yet studied these subjects and thus couldn't help (yet) with the VM.

I don't have as many years experience in Smalltalk, but the language seems 
so intuitive I feel much more productive in it then any other language.  I 
certainly wouldn't consider myself "top flight" as the web page requested, 
but maybe there are things I can do anyway. :)

I saw that it was desired to port Squeak to Strongtalk.  I don't quite 
understand this.  What would be considered success here?  Determining what 
the core is and putting what ever core classes that are missing in?  
Morphic?

I also saw "portable GUI" project in the issues list.  I don't know what you 
had in mind, but personally I like the Dolphin MVP (a more modern MVC 
pattern) framework for doing the GUI work.  Obviously Strongtalk would want 
to have something like wxWidgets as the base views instead of only windows.  
So what is everyone looking for here?  Do you prefer to go with more of a 
Morphic framework (which I don't know much about, except that it seems to be 
a mess in Squeak :)?

And lastly, I saw that someone requested native thread handling in the 
image.  Personally I feel this is not necessary.  In my opinion the way to 
go is stay green threads, make them preemptive somehow and make a nice way 
to do message passing.  After a question came up in the Squeak mail list I 
gave my overview of concurrency [1] options today.  If Strongtalk goes with 
in-image native threads then you have two options to deal with them:  fine 
grained locking (a la Java) or Software transactional memory.

As I stated in that message, fine grained locking isn't going to be any more 
tenable in the future then manual memory management is now.  STM may turn 
out ok, but I don't have high hopes for it in the long term.  Personally I 
think a pure message passing strategy like Erlang is the superior model 
here.

Thanks,
Jason

[1]   
http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-February/114181.html

_________________________________________________________________
Like the way Microsoft Office Outlook works? You’ll love Windows Live 
Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---