Linked by Kaj-de-Vos on Thu 20th Dec 2012 00:22 UTC
Permalink for comment 546202
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2007-02-15
Well, seems that's what the "syllable team" did in the past few years.... predictions and plans.
To be honest, core syllable lacks a lot of stuff.
Syllable has a "malnourished" core, which made as good as no progress in the last 3-5 years, the api is missing a lot of features and is quite buggy or even unfinished (e.g. the layoutmanager,...)
Instead of improving core syllable (e.g. the media kit is unfinished and buggy) and being up-to-date with the neccessary developer tools (at least a recent gcc).
Instead you have... rebol plans and predictions.
Good, but i must admit i don't know the internals of rebol, but imagine a nice situation:
what if in future the rebol interpreter will need a more recent compiler (e.g. they could use a useful c++11 feature).
Even if rebol will get out of this alpha phase some day, it's very unlikely that syllable will have a complete port, since the media-kit, opengl/mesa..etc are in a unfinished state.
Instead of building and improving the syllable "infrastructure", syllable was making rebol plans and predictions.