wavesplash

Write in whatever gets you the largest amount of marketshare the fastest. If you're making big $$$ or pulling in redonculous amounts of eyeballs the acquirer won't care if you wrote it in assembly or cobol. More importantly, don't worry about acquisition - concentrate on a business model that makes $$'s. Acquisition is for the lucky few and she's a very fickle suitor.

And we're getting tired of linkbaiting posts.

Moved over from SVN to Git for all of our Rails projects. Plugins? Doesn't matter if they're SVN/Mecurial/CVS/Git whatever. Once you './script/plugin install' the plugin is in your vendor/plugins dir. Git plays well with SVN. Give it a whirl.

YUI css is designed to do a few layouts well and make other layouts possible. Its not bad, but it is clunky to work with and a pain if you don't fit one of its proportional models precisely.

Blueprint is more logical and conceptually easier to understand - everything is put on a flexible grid and you choose how many grid units you want to use for each layout block.

I dig the rest of the YUI toolkit, but compared to blueprint, YUI CSS feels like a hack.

Being a better feature has nothing to do with being a lucrative acquisition. If Xobni can show a clear benefit in $$'s to M$'s bottom line, then the corpdev guys might get excited. Right now there's no serious competitive threat to Outlook as installed software, so buying Xobni (or anyone else) just for additional features isn't interesting. Without a competitive threat MS could take 2 years to copy most of Xobni and roll it out in a future version.