Why WOSH Icarus series is so important?

Icarus is a character in Greek mythology.
He is the son of Daedalus and is commonly known for his attempt to escape Crete by flight, which ended in a fall to his death.
Daedalus fashioned two pairs of wings out of wax and feathers for himself and his son.
Daedalus warned his son not to fly too close to the sun, nor too close to the sea. Overcome by the giddiness that flying lent him, Icarus soared through the sky curiously, but in the process he came too close to the sun, which melted the wax.
[ http://en.wikipedia.org/wiki/Icarus ]

WOSH byron (series before icarus) was quite stable and growing. But as a framework and its components increase and get complex (as their iteration), new features are required and old architectures become tight.
The new 'trunk' which was going to include a bunch of backward incompatible updates, revisions and pattern-changes, was named WOSH Icarus.
Some update's topics are: object-allocation and identification (reflection), serialization, user-sessions, security (just started), source-tree and supported-libraries revision, funtionals, data-models, tree container, (..too many).
As talking, WOSH Icarus is still under development, the concept of "icarus" is positive in every way. Even melted wings, translated into new features/pattern which didn't fit as expected (in other words: rollback) are considered good tries to solve a new problem.. or just an experimental functionality :)

Enjoy WOSH Icarus (untill "WOSH wolf" will tear it)