What's really cool about web standards is that they are damn useful. What's crappy about Adobe is that it means the exact opposite of web standards. Yet the "crap" Adobe produces every year (since the late nineties) is damn useful as well. The climax of this contraddiction is the widely known "Div over Swf" phenomenon.
In my past freelance experience I have often been dealing with small business entities asking me to make a website without knowing why they wanted a website. Kind of embarassing: you have been hired as a web developer and you expect the customer to deliver you some content, which he/she wants to be properly published on the web. Sometimes a simple site structure is delivered and the content must be dynamic, which is good as well. Or sometimes even the site structure has to be discussed and this is, let's say, interesting. But in most cases the customer hired what his/her imagination calls a "Web Site Maker" (or a "Websiter" or a "Webber" or a "Siter"...) just because he/she felt some kind of (social? cultural? environmental?) pressure for the need to have a website. Five years ago this could be easily fixed. The solution was the simple showcase website. Standard structure, static content and pay-for-edit money vacuum. Great. But then came Web 2.0, and small companies CEOs surf the net and see that new websites increasingly focus on user-generated content. And they feel troubled.
My best congratulations to the Ubuntu Desktop team. Yesterday I installed Ubuntu 9.10 and everything worked with simply no effort. I really did nothing, just specified the partitions and mountpoints (which is even greater, because when you attain a certain level of simplicity it is really difficult to keep giving advanced users the choice to do things their way). This is what I was dreaming of when I started learning the usage of the mount command back in 1997, in order to read a cd-rom. Thank you, guys. You are making the world a better place.
Yesterday I found that, working with Flex, there is no way to find a Container's child if it is not a direct-son of the component. This means that in a structure, for example, like Container_1 -> Container_1.1 -> Child_A it is simply useless to perform a getChildByName("Child_A") over Container_1.
|
