AOP on .Net

Erich Eichinger posted in december 2009 the first of a series of posts on AOP in ,Net. It is worth reading. Find the first here.

Silverlight vs Flex

I found a very well structured post on the comparison between Silverlight and Flex. It's almost a year old but remains relevant (to me at least): Find it here.

RDS launch

Amazon has launched a new service yesterday. Finally, they offer a RDBMS as a service. MySQL 5.1 as it turns out was their choice. I'm good with that.
There are quite a few posts about this: no surprise: Werner Vogels, Amazon's CTO has a post as well as Cloud Ave, RightScale and TechCrunch to cite only the ones on my RSS feed list.

ISMIR 2009

There are a few good posts on the web regarding ISMIR 2009. Seems it was once again the place to be for anyone having anything to do with music signal processing and information retrieval. Paul Lamere has a few posts already on the conference. We were working on many of the topics discussed during the conference: music instrument recognition, tempo, music similarity for recommendation purposes. Economic realities forced us to stop our researches but it is nice to see that people are making progress on those topics.

Waves and Raindrops

Mozilla is at it again.In many ways they have revolutionized browsers with Firefox and all the plugins that make it a favorite amongst developers and "normal" users. They also had a fairly descent mail client in Thunderbird. Now, they are taking a stab at the future of email with Raindrop. From what I could see and read on the web regarding that project, it sounds very interesting.Mashable makes the connexion between Raindrop and Google Wave: both are trying to re-invent web based communication.
You might also be interested in ReadWriteWeb take on Raindrop or that of WebMonkey or GigaOM or TechCrunch

5 new tech trends you can't afford to ignore

Hypebot has a short post on their take on the up and coming trend. Except for #5, I'm totally with them on this. Have a look at this post here.

Wave security

ReadWriteWeb has a good post on Google's Wave security. What I take away from this article has less to do with Wave per se as with the fact that security was a concern addressed from the start. One would wish this would be the "obvious" approach not worth mentioning in an interview. Since it's not the case, kudos to Google for showing the way both with their products and with their methodology.