Monthly Archive for July, 2009

Microsoft and Yahoo! to enter rev-share deal that makes Bing default search egngine on Yahoo!

As per this article, it looks like MS and Yahoo! will enter into a rev-share deal that will set Bing as the default search engine on Yahoo!.

Apparently the formal anouncement is to be made tomorrow, so lets perhaps take this info with a grain of salt.

Link originally picked up from this slashdot article.

The difference between a manager’s day and a developer’s day

Over on boing boing, a link to an interesting article on the difference between a manager’s day and a developer’s (the maker’s) day, and how a 1 hour meeting can have a devastating impact on a developer’s day.

It’s rare that I get to make anything in terms of development these days, but I also consider setting team strategy and process and ensuring execution on that strategy a “making” activity. I do this all the time and can confess to having the same feelings as Paul Graham, relishing in days that are appointment free, and sometimes going so far as booking out a whole day to make sure I don’t get interrupted.

Link to actual article, a very interesting read, Maker’s Schedule, Manager’s Schedule.

Yet another Premium Mobile service

On boing boing, this post mentions a new scheme to allow people to order movies at home for $1 using their mobile phone. Once ordered a gadget attached to the TV descrambles the signal, with the money being billed to the user’s mobile account.

Silverlight TreemapViewer

Miguel posts about a TreemapViewer they implemented in Silverlight. Cool code snippet if you ever need to do something like in a rich client.

Silverlight Treemapviewer

Silverlight Treemapviewer

The code is available online.

Swearing mitigates pain

I always knew this was true. Over on boing boing, Cory tells us about a journal article that confirms what we’ve always known, swearing mitigates pain.

Silverlight 3 released

Over on Scott Gu’s Blog, Silverlight 3′s release has been announced.

Highlights include better font support, accelerated video and 3D support and bit-stream manipulation allowing you to right custom codecs. As well Silverlight 3 now supports H.264, MPEG-4 video and AAC audio.

Silverlight 3 also sports out-of-browser capabilities as well as a whole plethora of new UI controls, and whole lot more business application development focused features.

Microsoft extends community promise to ECMA C# and CLI

First seen over on monologue, Miguel writes to say that Microsoft has extended it’s Community Promise (around patents etc.) to the ECMA standardised C# and CLI components.

Quote from the announcement by Peter Galli at MS:

It is important to note that, under the Community Promise, anyone can freely implement these specifications with their technology, code, and solutions.You do not need to sign a license agreement, or otherwise communicate to Microsoft how you will implement the specifications.

The Promise applies to developers, distributors, and users of Covered Implementations without regard to the development model that created the implementations, the type of copyright licenses under which it is distributed, or the associated business model.

Under the Community Promise, Microsoft provides assurance that it will not assert its Necessary Claims against anyone who makes, uses, sells, offers for sale, imports, or distributes any Covered Implementation under any type of development or distribution model, including open-source licensing models such as the LGPL or GPL.

Full Community Promise over at Microsoft.

Note: as Miguel says in his post, mono implements a whole bunch of .Net technology above and beyond ECMA C# and CLI and those parts (ASP.Net ADO.Net etc) aren’t currently covered by this promise.

Mono VPC appliance

Over on monologue, a mono virtual PC appliance.

Not blocking the UI in tight JavaScript loops

Found on planet gnome. Cool code snippet for getting UI updates from a javascript loop using jquery.

Retargeting P/Invoke to managed code

Chris Toshok over on monologue post’s about minvoke, a tool to retarget p/invokes out of unmanged land and into managed code.

The potential of this tool is absolutely awesome. As I understood it, the primary reason is to enable the guys to shoe-horn portability onto .Net apps with over-zealous p/invokes into windows api calls. Makes sense.

But that’s not the only reason you’d use it. You could use this tool to force managed applications that call into native land to be completely managed, enabling you to ensure that the .Net security model is applied to every aspect of the code, or simply freeing yourself of the need to have developers around that can develop in more than just .Net.

As stupid as that sounds, it’s getting increasingly hard to find developers around that understand more than one language/framework. Even those that do, generally only understand multiple web-development languages. So if you ever find yourself in a situation where you are working on a Winforms app that needs to interface with a device of some sort you’d be shit out of luck.