As you may already know there was a huge discussion (with some aggression from time to time) about changing E17 and EFL’s license (BSD to LGPL). Now apperantly it came to an end, and the result is that Eina, Etk, Evolve and Edje_editor are under the terms of the LGPL license.

Currently the Eina library is in proto/, maning that it’s still a prototype but is supposed to be in our core foundation libraries (as it will become a dependency for Evas and maybe Ecore). If this happens EFL will be dual-licensed – BSD and  LGPL.

Only time will show if this is for good.

Recently it has been suggested to release Embryo. And while everybody agreed that it is almost as stable and bug-free for a release in the very near future (2 weeks), another important question appeared: do we actually need Embryo?

This is because some developers (including raster) are considering to move to Lua – a more powerful, wide spread scripting language. And so, if there is such a move it makes using (and thus, releasing) Embryo pointless. On the thread some people suggested to use JavaScript or Python instead of Lua, but that is unlikely.

in all honesty – javascript is not going to make anything a lot better… as
the only thing we will get is language constructs – the massive pool of
knowledge on js is its use WITH www objects and with the api and event
facilities a browser provides. this will not be the same. this bit will be
different, thus all we get is syntax and core language constructs (i.e. C
without even libc).

raster said…

As for Python both KainX  and raster said that it is too heavy and big for our needs.

We will know the future of Embryo very soon – it will either be released and maintained for awhile or it will never be officially released and will be replaced by Lua (or something else). If you want to join the discussions, subscribe to the E-Devel mailing list.

First test post.