Well, I'll give a quick little rundown of various items, just more of an "about Moose" than anything technical, so feel free to ignore this since it's mostly useless.
In any event, it is my opinion that Io isn't moving back towards use in an embedded market. Sure, currently it seems quite like a good tool for a control language in many applications; but as for use in embedded devices, it's sorely lacking and not looking as if it's going to be making any strides in that area any time soon. This isn't really a shot on Io, it's just there's really nobody interested in doing this -- and the more and more the language is written in itself, the less and less that is practical for embedded devices, as the memory footprint grows. This is one main area of focus for Moose.
Secondly, but more as an extension to the first point; the memory footprint must be small, and as a result, Io's choice in garbage collection strategy, just doesn't lend itself very well to operating with a small memory footprint. So instead of copying Io's mistakes, all objects will not be of the same size, as mandated by Baker's Treadmill collector, and instead, we'll use a slight variation on cheney's copying collector supporting generations initially, and eventually find and implement a better algorithm for time.
Thirdly, and finally for now, I'm going to design a new standard library which will be mostly incompatible with that of Io and will probably more resemble standard libraries distributed with many Smalltalk vendors implementations thereof.
Finally, the name... If anybody has ever seen a Moose (Alces alces), it's a very large member of the deer family (Cervidae) with long springy legs, a heavy body and quite awkward looking when in motion. It's the most awkward animal I could think of that is native to Canada.
More details will be forthcoming when they well... are. =]
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment