Four short links: 9 November 2009

Moth Mind Readers, Shiny UI Futures, Usable Newspapers, Hardware Testing

by Nat Torkington | @gnat | comments: 0

1. A Battery-Free Implantable Neural Sensor (MIT Tech Review) -- Electrical engineers at the University of Washington have developed an implantable neural sensing chip that needs less power. Uses RFID's induction technology which means the power source can be up to a meter away. Proof of concept was implanted in a moth to sense central nervous system activity.
2. New Microsoft Interface Technology -- videos from Craig Mundie (Chief Research and Strategy Officer) on the MS Campus Tour talking about the future of UI using a sexy glass prototype that features tablet PC, gesture, speech recognition, and even eye tracking. Lustable.
3. Adding Usability to Print -- detailed description of a failed pitch to reinvent a newspaper, to bring web sensibility to print. Make the paper more usable, think cross media instead of separate media, while using the strength of the paper (pictures, info graphics, nice text) to the max… Make a product that people want to buy because it is more usable that the competitor, not because it wins graphic design prizes. (via Evolving Newsroom)
4. StressAppTest -- Google-created open source project to pound the living crap out of hardware by maximising random traffic to memory from processor and I/O, with the intent of creating a realistic high load situation in order to test the existing hardware devices in a computer.

Why Google and Bing's Twitter Announcement is Big News

Tweets will finally become first class web citizens

by James Turner | comments: 11

Lurking innocently on Google's blog this afternoon, like many of their big announcements, was the bombshell that they have reached an agreement with Twitter to make all tweets searchable. This followed an earlier announcement at the Web 2.0 conference by Microsoft that Bing has also arranged to make tweets searchable.

This is not only a huge thing for Twitter, it is also well past due. Until now, Twitter really hasn't been a first class web citizen, because you're not really part of Web 2.0 until you're searchable by Google (and, I suppose, Bing). Sure, you can read someone's tweets from Twitter, or get a thread via a #tag, but the full text searching capabilities that make things really usable on the web, largely powered by Google, have been missing.

Making tweets searchable is a major usability improvement as well. Twitter handles are cute, but sometimes obscure as well. Perhaps people will start using more full names in their tweets in addition to @ references, which would let you find tweets about people without having to know what their handle happened to be.

It appears that Twitter is going out of their way not to play favorites in the search space, by cutting deals with both Microsoft and Google. Microsoft seems to be ahead of the game right now, since they have a live site up, whereas the announcement from Marissa Mayer of Google only hints at things to come over the next few months.

The Bing interface is interesting, it seems to be a hybrid of a web search engine and a twitter search. Typing in a term gets you back both the latest tweets that match the keywords, as well as web pages that more than one tweet share in common that also match the keywords. This is a tacit acknowledgement that a lot of the useful content of Twitter is found in the web pages that are linked from the Tweets.

If I had to guess, I'd say that Tweets will show up more traditionally on Google, as just another kind of search result, that can be narrowed in the same way that you can narrow results to just images or movies. I guess we'll have to wait and see on that.

Random Hacks of Kindness: Disaster Relief Codejam

by Brady Forrest | @brady | comments: 7

Google, Microsoft, Yahoo! and the World Bank are getting together to support disaster relief projects. The first Codejam will be Nov 12-14 i the Bay Area. You can sign-up now. The list of proposed projects is online.

What is Random Hacks of Kindness?
It is an initiative that brings together disaster relief experts and software engineers to work on identifying key challenges to disaster relief, and developing solutions to these critical issues. This Codejam is the first of a series of Random Hacks of Kindness (RHoK) events that will bring the best and brightest together for a "give camp" to solve real world-problems related to Crisis/Disaster Relief.

Objectives:
This event is the first step in building a global community dedicated to solving disaster relief challenges through technology.
At the RHoK Codejam, programmers will partner with subject matter experts to tackle “real world "problems. These challenges have begun to be defined (see preparation), and will continue to be refined during the event.
The software created at this first event will continue to be developed at subsequent RHoK events, and openly shared with the international community. Our hope is that this software will address some of the serious challenges facing the disaster response community, and evolve in response to their needs.

Background:
In May 2009, the first ever Crisis Camp barcamp was held in Washington, DC. During one of the opening sessions an industry panel including representatives from Microsoft, Google and Yahoo! agreed that some matters supersede competitive concerns. We agreed to cooperate to mobilize our developer communities to create interoperable solutions/code that will have real impact in the field. We have partnered with NASA and The World Bank to make this happen.

Organizers:
Microsoft, Google, Yahoo and The World Bank are founding sponsors
NASA-Ames is a co-sponsor

Preparation:
We want our hacks to make an impact. To that end we need the problem definitions as tight as possible before we begin coding on the 12th. The following is a link (see here) to the preliminary project definitions. Please contribute by adding new ideas and/or refining ones that are already there.

Four short links: 12 October 2009

DSL for NLP Task, Insider Tradespotting, Outsource Fail, Cloud Fail

by Nat Torkington | @gnat | comments: 3

1. Snowball -- a small string processing language designed for creating stemming algorithms for use in Information Retrieval. (via straup on delicious)
2. Insider Trades -- a Yahoo! Hack Day app that turned out to be worth continuing. Scans SEC systems every 30 seconds and alerts you if the stock you track has been traded by an insider. (via straup on delicious)
3. Air New Zealand Slams IBM -- central point of failure in the outsourced IT. "In my 30-year working career, I am struggling to recall a time where I have seen a supplier so slow to react to a catastrophic system failure such as this and so unwilling to accept responsibility and apologise to its client and its client's customers is not the glowing endorsement you want.
4. Danger/Microsoft Loses Sidekick Customers' Data -- Regrettably, based on Microsoft/Danger's latest recovery assessment of their systems, we must now inform you that personal information stored on your device - such as contacts, calendar entries, to-do lists or photos - that is no longer on your Sidekick almost certainly has been lost as a result of a server failure at Microsoft/Danger. This cloud had a brown lining.

Microsoft Press Enters Strategic Alliance with O'Reilly

by Tim O'Reilly | @timoreilly | comments: 32

Today, Microsoft and O'Reilly Media announced an agreement to support and expand Microsoft Press. Under the terms of the strategic alliance, O'Reilly will be the exclusive distributor of Microsoft Press titles and co-publisher of all Microsoft Press titles, on Nov. 30, 2009. We'll be working with Microsoft to develop new books, as well as distributing both existing and new co-published books to bookstores, and, perhaps most importantly, to the emerging digital book channels that represent the future of book publishing. Microsoft could have chosen to partner with any of the major computer book publishers. That they chose to work with us is a testament to three advantages we bring to the business:

1. O'Reilly is more than a book publisher. We are an advocate, a connector, and a community builder. We help developers and users make the most of technology, with a focus on what they need to know. Microsoft has a history of building great developer communities, but in today's world, those communities need to be connected with other communities outside Microsoft. Especially in technology, "the world is flat."
2. O'Reilly plays a unique role in the technology ecosystem: from our earliest days, we provided the documentation for important technologies for which there was no "vendor." The internet, the World Wide Web, Linux and other open source software, and Web 2.0 all were documented and given mainstream awareness by O'Reilly books and events. We identify and evangelize the disruptive technologies that reinvigorate the industry.
3. O'Reilly has been a pioneer in the new world of ebooks. In the early 1990s, we co-developed docbook, one of the first standardized formats for ebooks, and the progenitor of future XML-based ebook formats. In 2001, in partnership with the Pearson Technology Group, we launched Safari Books Online, the largest and most comprehensive electronic subscription library of computer books and videos. We've built a successful direct business with DRM-free downloads of ebook bundles that work on any device. We're an early leader in publishing books for the iPhone and other portable reading devices, and understanding how to use ebook channels to reach new customers. And of course, our Tools of Change for Publishing Conference (TOC) has become the place to share knowledge about the changes sweeping through publishing.

On this last point, I'm particularly excited that as part of this agreement, Microsoft has committed to make its ebooks DRM-free and device-independent. One of our goals at O'Reilly has been to make sure that ebook customers can read them on any device, and have the ability to keep using them even if they change their preferred device. Having Microsoft Press join us in this commitment is a big step forward towards an open ebook market.

Why is HTML Suddenly Interesting?

by Simon St. Laurent | comments: 16

Web developers couldn't stop talking about HTML and its evolution during the 1990s. New features were usually tempting, though not always workable, and the Browser Wars meant that vendors competed by providing and copying features. The HTML standardization process had its twists and turns, moving from the IETF to the W3C, developing standards that reflected immediate needs and tried to channel developer energy in more productive directions.

Then, suddenly, HTML was incredibly boring. The dot-com bust was part of that, but a more fundamental change doomed the conversation: Microsoft dominated the space. Whether because of the dominance of Windows, the technical quality of key innovations like Dynamic HTML, or the disappearance of Netscape into AOL, the stark reality was that Internet Explorer ruled the browser world. Outsiders asking Microsoft for improvements to Internet Explorer invariably heard that Microsoft would be willing to upgrade IE "when our customers ask for it" - which was an almost polite version of no.

As a result, the last decade, even for those of us who turned to Mozilla, Opera, Safari, Chrome, or other browsers, has been one long exercise in making the most out of tools that took their last major steps in the late 1990s. There was enough in HTML 4.01, Cascading Style Sheets 2, JavaScript, XML, HTTP, and XMLHttpRequest to keep us busy, especially as users acquired higher-speed connections and faster computers. There was also constant frustration with browser limitations, driving the development of more flexible plugin approaches like Flash and Silverlight, though none of them succeeded in replacing the traditional Web, however dull it might have become.

Today, though, the HTML conversation is reborn. Standards development around HTML seems to actually have a chance of influencing user experience in the browser, and Microsoft itself is participating in the HTML 5 conversation despite still holding roughly two-thirds of the browser market. While Microsoft's market share is only slowly eroding, developer mindshare seems to have shifted decisively to the band of WHATWG upstarts, Microsoft's competitors.

The reason for this, I think, is that HTML 5 clearly has a bright future in a place that Microsoft can't presently block: mobile web browsers. When I ask people about the future of computing, the word I keep hearing in their answers is "mobile". Even if it's small now, it has a much greater effect on how people evaluate what's coming.

Microsoft has a mobile presence, certainly, but it's hard to argue that it has anywhere near the visibility of the iPhone, or even the Android. Mobile web browsing has kept Opera going for years, but the iPhone and Android give Apple and Google much more visibility for their HTML 5 work, and Apple's decision to keep Flash off the iPhone in particular gave developers further cause to rethink their dependencies. (The WebKit browser engine these share will also be integrated with Blackberry soon, and is also on the Palm Pre.)

In the mad rush to build mobile applications, HTML 5's competition isn't even desktop web browsers, but other mobile development toolkits. As my co-worker Keith Fahlgren put it recently:

Speaking from personal experience, I've had a lot more fun writing an HTML5 application based on CSS3, the database API, and jQuery that runs out of the box on all of the hot mobile platforms than I ever would have had writing some silly Objective C app for a locked down App Store (or Java for an open one).

This creates a whole new world for the "where should HTML go?" conversation. Web developers certainly have pent-up demand for new features, but previous conversations about revising HTML always foundered on the "but will Internet Explorer support it?" question. Today, when that question feels less important, the ice is finally breaking. (Microsoft is even participating in HTML 5, though it's not yet clear how committed they are to implementation.)

It will doubtless be years before developers can safely deploy fully-featured HTML 5 sites without concern for older browsers, but for the first time it is plausible that changes to HTML will find wide adoption, and hope is rising. That hope, of course, brings its own risks. I can't say the HTML 5 process has done credit to either the W3C or the WHATWG - it feels to me like an ugly scramble - and there are plenty of specific decisions that deserve careful questioning. That the broken process is actually important to people, however, is a huge sign in itself that HTML is relevant once again.

After years of quiet, it's worth paying attention again!

Who's Winning the Smartphone Wars?

by Raven Zachary | @ravenme | comments: 7

The short answer - Microsoft and Nokia are slipping, RIM and Apple are gaining. It's too early to tell with Google. This shouldn't come as a surprise to anyone.

Last week, UK-based analyst firm Canalys, released its findings on smartphone market share based on Q2 2009 unit shipments (see "Smart phones defy slowdown"). Before sharing Canalys' findings, there are two important points to understand:

• How market share is defined is based on the numnber of units shipped during a particular period of time, not the number of active users of a specific smartphone platform, which is the installed base. These are commonly misunderstood terms. To determine the share that any particular smartphone platform has of worldwide active smartphone users would require aggregation of data from all of the mobile network operators. Good luck with that.
• The results of these reports are not reflective of how well a company is actually doing in terms of profit (see "A Visualized Look At The Estimated Revenues Of The Top Cell Phone Manufacturers" as an example).

Canalys covers a number of topics in their latest smartphone research, but the one topic are I want to focus on is "Global smart phone market by OS". Which companies are shipping the largest number of plastic phones into the world is less interesting to most of us than which mobile operating systems are winning. Dell vs. HP is not as compelling as Microsoft vs. Apple, in the personal computer market. LG, Fujitsu, and Samsung, three successful handset manufacturers, generally are not fully part of the smartphone conversation as they have historically licensed smartphone operating systems from companies such as Microsoft (this trend is changing to include more diverse licensing partners and increased in-house OS development).

Symbian (Nokia) accounts for half of the smartphones shipped in Q2 2009, followed by RIM, Apple, and Microsoft. Compared to the same quarter in 2008, Symbian and Microsoft are losing smartphone market share, and RIM and Apple are gaining significantly. Apple's growth percentage over the prior year is artifically inflated due to contraints in availability of the original iPhone just prior to the release of the iPhone 3G in Q3 2008. Minus that event, it would have been closer to RIM's annual growth percentage.

Even though Nokia has a 50% smartphone market share right now with Symbian, I think they are the most vulnerable of all the major players covered by Canalys. Symbian is a mobile operating system struggling to be modern with a developer ecosystem that seems to be far more fractured and unmotivated when compared to the excitement I see regularly from Android, iPhone, and BlackBerry developers. Microsoft's Windows CE and its variants have been in the market since 1996, and on smartphones for nearly a decade, yet has not been able to effectively remain competitive recently. And while Android has shipped on just over a million smartphones during the quarter, that's still impressive considering the small number of devices that it's currently available on, especially due to the number of pre-announced devices that wil be coming over the next few quarters.

Surprisingly absent in this data are other Linux-based mobile operating systems, which must fall into the ambiguous "Others" category, along with mobile operating systems, such as Palm Pre. The fragmentation of the various Linux mobile operating system efforts, including handset manufacturer specific implementations, is doing more harm than good right now in terms of market share growth.

Four short links: 9 July 2009

by Nat Torkington | @gnat | comments: 1

1. Ten Rules That Govern Groups -- valuable lessons for all who would create or use social software, each backed up with pointers to the social science study about that lesson. Groups breed competition: While co-operation within group members is generally not so much of a problem, co-operation between groups can be hellish. People may be individually co-operative, but once put in a 'them-and-us' situation, rapidly become remarkably adversarial. (via Mind Hacks)
2. Yahoo! TrafficServer Proposal -- Yahoo! want to open source their TrafficServer product, an HTTP/1.1 caching proxy server. Alpha geeks who worked with it are excited at the prospect. It has a plugin architecture that means it can cache NNTP, RTSP, and other non-HTTP protocols.
3. App Engine Conclusions -- I've reluctantly concluded that I don't like it. I want to like it, since it's a great poster child for Python. And there are some bright spots, like the dirt-simple integration with google accounts. But it's so very very primitive in so many ways. Not just the missing features, or the "you can use any web framework you like, as long as it's django" attitude, but primarily a lot of the existing API is just so very primitive.
4. Microsoft Hohm -- Sign up with Hohm and we'll provide you with a home energy report and energy-saving recommendations tailored to your home. Wesabe for power at the moment, with interesting possibilities ahead should Microsoft partner with smartmetering utility companies the way Google Powermeter does. This is notable because this is a web app launched by Microsoft, with no connection to Windows or other Microsoft properties beyond requiring a "Live ID" to login. For commentary, see Microsoft Hohm Gets Green Light for Launch and PC Mag. (via Freaklabs)

Four short links: 8 July 2009

by Nat Torkington | @gnat | comments: 3

1. Stop Whining About Facebook's Redesign (Slate) -- How can I be so sure that you'll learn to like the redesign? Because you did the last two times Facebook did it. The conclusion is that sites don't say why they're redesigning, and that causes the resistance.
2. C# and CLI under the Community Promise (Miguel de Icaza) -- Microsoft have announced they won't pursue patents relating to C# or the .NET Common Language Infrastructure (CLI): 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. Good news for Mono and other .NET-compatible projects.
3. app-engine-patch -- a patch that lets most of Django work on Google App Engine. (via caseywest on Twitter)
4. Scope -- talk by Matt Webb, given to Reboot 2009. Every ten slides I sigh happily as new mental connections slide into place, as only Matt can make them. Worth it just for finding this Stewart Brand quote, "We are as gods and might as well get good at it." That one sentence could direct a lifetime of action.

Velocity Preview - The Greatest Good for the Greatest Number at Microsoft

by James Turner | comments: 4

The psychology of engineering user experiences on the web can be difficult. How much rich content can you place up on a page before the load time drives away your visitors? Get the answer wrong, and you can end up with a ghost town; get it right and you're a star. Eric Schurman knows this well, since he is responsible for just those kind of trade-off decisions on some of Microsoft's highest traffic pages. He'll be speaking at O'Reilly's Velocity Conference in June, and he recently talked with us about how Microsoft tests different user experiences on small groups of visitors.

James Turner: Why don't you start by describing what your gig at Microsoft is now and what your career path has been there?

Eric Schurman: I'm a principal dev lead for Live Search, what used to be MSN Search. And I started at Microsoft back in the late 90s working in Microsoft's Press organization, where we actually were developing training software that would emulate new Microsoft products, but didn't require those products to be on a user's machine. So, for example, if you had an organization that was running Windows 95, we would have a training system for Windows 98 that would emulate a bunch of the functionality of Windows 98 so that you could deploy it to your people. They could train their people on how to use Windows 98 before they actually deployed it.

I then moved on to the Microsoft Press website, where I became the dev lead for it. I made a few other moves and ended up going to Microsoft.com, where I ran the download center, the Microsoft.com homepage, the product catalog, and a bunch of other places from a dev perspective.

I then moved to what was then MSN Search, back in about 2005, and was there through the MSN to Live transition. At the time, I wasn't working on performance; I was just working on the Live Search application. And it became very obvious that we had some major performance problems. Performance has always been one of my really strong interests, so I took on addressing a lot of those. And when we addressed them, we had very significant improvements in our business metrics. That really surfaced how important performance was to the organization, and I moved into a role where I was really focusing just on performance. I've been in that role now for about two years.

JT: You've worked on at least three very different parts of the Microsoft website. The homepage has lots of hits, fairly static. The download page is a lot of data for long periods of time. Live Search is high volume, but there's also a lot of backend on that. In what ways do you need to architect them differently? And where can you reuse the same lessons?

ES:: That's a great question. On the web, you've got different concerns on what you have for client apps. The main things that tend to impact end-user perceived performance on the web are often things about how you've designed your application from a network perspective. So how many different HTTP get requests are you making? How are those get requests structured? So, for example, are they serialized? Did you have a JavaScript file that then gets returned to the browser that requests another JavaScript file and another JavaScript file and then some content and then it finally gets rendered? So the number of assets that you request, that's going to be something that's important no matter what product your doing.

There are other things, like how much script do you have on the page, how much CSS you have on the page, how much actual content are your rendering to the page, etcetera. There are tricks that you can use like combining many different graphics into a single tiled image and sending that down to the browser. It's much faster to send one image to the browser than, say, 20 images. Even if you end up sending the same overall graphics, but combined into one, it's still must faster to send it as one request.

There are also different data volume concerns. They're also different from a business perspective. A lot of what we were sending out from the download center was extremely time critical. We would have an update go out, and we needed to make sure that update was going to be available anywhere in the world within a certain time frame, which required us to handle very high bandwidth, and a very high volume of requests coming into the site that were transferring lots of bits. So that required something totally different than something like the Microsoft.com homepage.

It's also interesting looking at the volume of traffic and how that traffic reflects real users. So, for example, one of the problems that you end up with on both the Microsoft homepage and Live Search is that we have a huge number of bots that are trying to hit the system, lots of people trying to do SEO work are trying to hit search engines to gather information about their site, about competitor sites, about all sorts of things. On the Microsoft.com homepage, it's always under distributed denial of service attacks. It's not a question of how frequently does it happen; it's just what is the rate right now? Also, the Microsoft.com homepage has historically had such a high up-time rate that it's actually hit by a lot of hardware devices simply to check for connectivity to the internet. And so you'd want to treat a request from that kind of "user" very differently from a request that's coming from a real user.

So that's kind of a long, rambling answer to your question. Do you have any areas that you want me to drill in or maybe talk about something else?

(continue reading)

Four short links: 7 May 2009

iPhone Rocketry, Copywrongs, Econopocalypse, and Empire

by Nat Torkington | @gnat | comments: 1

1. How To Use An iPhone To Fly RC Airplanes and Helicopters -- So I had my basic idea down. iPhone joins the Linksys router network. It gets an IP address. Then, I open up my pilot program. The pilot program interfaces with the router via SSH (I couldn’t think of a better way that has redundancy, and speed, and was already buily by someone else). The pilot program interprets what the iphone is doing, and outputs data to one of the ethernet ports of which there are conveniently 4. Rudder, Ailerons, Throttle, Elevator.
2. Economist Debates: Copyrights and Wrongs -- The Economist live debate about copyright, with the moot "This house believes that existing copyright laws do more harm than good." Public comments, voting, and new informed opinions each day.
3. How I helped build the bomb that blew up Wall Street (NYMag) -- story of the software developer behind a lot of the mortgage repackaging software. Many good lines, e.g., But even then, I was wondering why I was making more than anyone in my family, maybe as much as all my siblings combined. Hey, I had higher SAT scores. I could do all the arithmetic in my head. I was very good at programming a computer. And that computer, with my software, touched billions of dollars of the firm’s money. Every week. That justified it. When you’re close to the money, you get the first cut. Oyster farmers eat lots of oysters, don’t they?
4. Yow -- words of wisdom from John Battelle on Google as the new Microsoft: If any lesson is to be drawn, perhaps prematurely, from all this, it's that no company - or two companies - can lead a culture for longer than half a generation. After that, the culture starts to distrust the companies' motives, regardless of whether they are pure or well intentioned.

Four short links: 1 May 2009

Smart Grids, Open Source, Stuff That Matters, and Global Culture

by Nat Torkington | @gnat | comments: 2

1. A Little Give and Take On Electricity (NY Times) -- Dennis L. Arfmann, a lawyer at the Boulder office of Hogan & Hartson who specializes in environmental law, said he had no idea how much electricity he and his wife, Dr. Julie Brown, had used before he filled his roof with solar panels producing 4.5 kilowatts of power. During the day he sells power to Xcel and at night he buys it back; his goal is to cut his use so his net sales rise. All hardware networked, everywhere!
2. Open Source World Map (Red Hat) -- very nice map showing the intensity of open source use in countries around the world. (via Flowing Data)
3. Imagine Cup -- Microsoft's contest to get students working on stuff that matters. The winners of the New Zealand leg, Team Think, tackled literacy: they devised a program for tablets that provides both handwriting recognition and audio output, eliminating the need for basic literacy to understand lessons or instructions. They hope to take this prototype to developing countries that have underutilised computers due to literacy issues. (via Idealog newsletter and Scoop)
4. UGT -- It is always morning when person comes into a channel, and it is always late night when person leaves. [...] The idea behind establishing this convention was to eliminate noise generated almost every time someone comes in and greets using some form of day-time based greeting, and then channel members on the other side of the globe start pointing out that it's different time of the day for them. Now, instead of spending time figuring out what time of day is it for every member of the channel, we spend time explaining newcomers benefits of UGT. (via migurski on delicious).

Windows 7 Starter Pushes the Web and IE

by Brady Forrest | @brady | comments: 6

I run XP on my netbook and I've been looking forward to running Windows 7 on it. So I've been watching news about Windows 7 with interest. There is much discussion this week that the low-priced Starter Edition will only let you run three apps at a time. If you want to run more then you'll have to pay for the next level up.

Ed Bott's got a great post that details what it's like to use Windows 7 Starter and its limits. It's not as simple as just three apps. There are many utilities and minor apps that don't count. Windows Explorer, the Command Prompt, Task Manager, some services (like anti-virus software) and Desktop Gadgets don't count.

The most interesting move is that IE doesn't count towards your three apps. So using IE gets you that fourth app in a pinch. I wonder if this was a conscious decision on Microsoft's part to try to keep people using IE. Updated: I had misread a portion of Ed's post and IE is not exempt from the 3 app limit. My apologies. Thanks to Ed for pointing this out in the comments.

Of course limiting the apps will just push people to the browser for more things. Need a notepad then fire up Google Docs or Zoho. Need mail well, there's Gmail or Hotmail. This seems counter to Microsoft's goal of preserving the customer's relationship to Windows -- the more I am in the browser, the less I care about the underlying OS.

It's good to see Microsoft embracing the netbook market. They'd be foolish not to, but at the same time they have to be careful to not cannibalize Windows sales on high-margin machines. I don't think that the Starter Edition will be a non-starter as Information Week's headline reads. Though it will be bad for marketing purposes (I'm very curious about how they will position it on the Sales site), I ultimately don't think that the limit will matter for regular use.

Kodu: Visual Programming on the Xbox with P2P Level-sharing

by Brady Forrest | @brady | comments: 1

How do you make programming fun? How do you make it fun enough for kids to want to spend hours learning how to make loops and if/then statements? Simple you give them simple visual commands that let them control robots on the Xbox -- or at least this is the thesis of Microsoft Research's Kodu (formerly Boku).

Kodu (Boku) made a splash at Techfest two years ago and gave a demo at Ignite Seattle (Radar post). Since that time the levels and characters have gotten much sexier and the controls simpler, but more powerful. I sat down with the Matt MacLaurin, creator of Kodu (get it? Code-You) at MSR's Techfest last night. He told me that we can expect Kodu to be released on the Xbox this Spring (it's in select schools right now on the PC, but there's no word about a broader release).

It takes just 8 lines of "code" (see the image to the right) to create a game. Matt and his team have replicated most game types you would expect including Races, RPGs, Shooters (with cool missiles), Strategy and Puzzle. They've also included Sample Levels that teach a specific lesson (like how to change color, create loops, etc.).

Embedded into the game are the notions of sharing and openness. Any level can be tweaked. In fact the first option after finishing a level is "Edit This Game". I saw a working version where levels can also be shared amongst gamer friends via a form of P2P. When you are online you can choose to share all of your levels. Each level could fit on a floppy disk (not that your kid will know what that is). Embedded in each level is the creator and all subsequent editors. Kodu will track changes and try to determine who has made the most significant modifications to the level. When you start playing make sure you share with the Kodu team. They want to track how far levels are spread to create kind of a genealogy.

I took a lot of pictures and video of the game last night. You can see the video after the jump and the pictures on Flickr.

Visual programming environments are on the rise and something that every techie parent will want to keep an eye on. Kodu seems like the most accessible to me. It effectively hides the programming with "fun". I'm looking forward to its release.

We're featuring MIT's visual programming language Scratch at ETech this year. Use et09ffd code for 40% off the admission price.

(continue reading)

Four short links: 2 Feb 2009

by Nat Torkington | @gnat | comments: 4

1. Songs off the Charts -- Johannes Kreidler's audio visualizations using Microsoft Songsmith. Reminds me of Douglas Adams in Dirk Gently's Holistic Detective Agency where the amazing spreadsheet program could produce happy jingles or funereal dirges based on a company's revenues. (via Ben Fry)
2. PWN! YouTube -- elegant URL hack: replace "www." with "pwn" in a YouTube movie URL and you'll be given links to the Google content server location of the movie so you can download it.
3. Apple iPhone and Microsoft Surface -- the interesting folks at Stimulant have written the code to connect an iPhone to a Microsoft Surface. It recognizes one or more iPhones on the Surface and lets you display different things on the iPhone. In the demo you see an iPhone on a photo showing you a sketch version of the subject of the photo. The zoom is very smooth.
4. Flickr, Getty, and the Greater Good (Phil Gyford) -- "Flickr and Getty Images, the stock photography giant, are launching a new scheme which enables people to market some of their Flickr photos as stock photography through Getty." Phil points out that CC-licensing and Getty-listing are mutually exclusive, and Flickr will switch the licensing on a photo to "All Rights Reserved" if you list with Getty. The first way people think of to profit from commons are to enclose and sell them. But the commons are a lot healthier when you make money by adding to them, not taking from them.

Data Center Power Efficiency

by Jesse Robbins | @jesserobbins | comments: 8

James Hamilton is one of the smartest and most accomplished engineers I know. He now leads Microsoft's Data Center Futures Team, and has been pushing the opportunities in data center efficiency and internet scale services both inside & outside Microsoft. His most recent post explores misconceptions about the Cost of Power in Large-Scale Data Centers:

I’m not sure how many times I’ve read or been told that power is the number one cost in a modern mega-data center, but it has been a frequent refrain. And, like many stories that get told and retold, there is an element of truth to the it. Power is absolutely the fastest growing operational costs of a high-scale service. Except for server hardware costs, power and costs functionally related to power usually do dominate.

However, it turns out that power alone itself isn’t anywhere close to the most significant a cost. Let’s look at this more deeply. If you amortize power distribution and cooling systems infrastructure over 15 years and amortize server costs over 3 years, you can get a fair comparative picture of how server costs compare to infrastructure (power distribution and cooling). But how to compare the capital costs of server, and power and cooling infrastructure with that monthly bill for power?

The approach I took is to convert everything into a monthly charge. [...]

Daddy, Where's Your Phone?

by Tim O'Reilly | @timoreilly | comments: 36

I met recently with Vic Gundotra, formerly Microsoft's head of platform evangelism, and now VP of Engineering at Google, responsible for all their mobile efforts outside of Android. We were talking about Google's mobile strategy and the insanely cool new voice-activated Google search in the Google Mobile Application for iPhone. But what I really want to share is Vic's story about why he left Microsoft. It was one of those "wake up, the future is staring you in the face!" moments that we all experience from time to time, but often ignore.

The story goes something like this: Vic was out for dinner with family and friends. The adults were on one side of the table, the kids on the other. The adults were debating some issue, and Vic said, in response to a question from one of his friends, "I don't know."

His four-year old daughter Samantha, whom everyone knows as "Tiger," piped up from the other side of the table: "Daddy, where's your phone?"

"What do you mean, where's my phone?" She explained that she'd overheard the question. Why wasn't he just looking up the answer on his phone?

Out of the mouths of babes. Vic said that he realized in that moment that the era of the PC was over, and that the future belonged to cloud applications accessed via phones.

Kamla Bhatt was busting my chops about the same subject when I did an interview with her last week for Mint, the Indian business site. "Tim, you don't talk enough about mobile!" she said. "In India and around the world, there is a whole new generation that accesses the internet, and they have never seen a PC. To them, it's all on their phone."

It's not entirely true that I don't talk about mobile. On Radar, we talk about not just mobile, but all kinds of distributed sensors all the time. And "instrumenting the world" has been a major theme in my talks.

But I plead guilty to Kamla's charge: I think about the web as experienced on a PC, and then about mobile as an add on. The tipping point has come; that notion has to flip: if we're trying to get ahead of the curve, we need to think first about the phone, and then think about the PC browser experience as the add-on.

In short, to borrow Accenture's slogan: "Be a Tiger!" She is the next generation. Always remember her question: "Daddy, where's your phone?"

Microsoft Releases a Technology Preview of OpenID for Windows Live

by David Recordon | @daveman692 | comments: 6

This morning at Microsoft's Professional Developers Conference, the Windows Live ID team announced that Windows Live ID will support OpenID 2.0 with a Community Technology Preview today and production support sometime next year.

Beginning today, Windows Live™ ID is publicly committing to support the OpenID digital identity framework with the announcement of the public availability of a Community Technology Preview (CTP) of the Windows Live ID OpenID Provider. You will soon be able to use your Windows Live ID account to sign in to any OpenID Web site!

Microsoft joins Yahoo! who implemented support for OpenID earlier this year for all of their accounts. By sometime next year, every AOL, Microsoft and Yahoo! user will have an OpenID which makes the emerging focus on improving OpenID's user experience even more important.

Angus Logan from the Live team has put together a quick screencast showing the current developer oriented process for testing the Windows Live ID OpenID Provider with an OpenID 2.0 enabled site.

Windows Live ID OpenID Provider Screencast from Angus Logan on Vimeo.

While this is great news from Microsoft, real web-scale adoption of technologies always faces a chicken-and-egg problem between developers and vendors. Developers don't want to adopt a technology without buy-in from platform providers and platform providers don't want to support a technology if developers won't use it. We've largely been able to successfully avoid this concern with OpenID as it grew from roots in an open source community with lots of people and companies involved in making OpenID what it is today. There are now well beyond half a billion OpenIDs available on the web which means we can mark the first phase of OpenID adoption, platform support, as a success.

The next phase of developer adoption will not be measured in the number of OpenIDs or sites that support it, but rather user experience, accessibility, and seamlessness of integration into a wide variety of applications and experiences.

Live Stream of MSR's Social Computing Symposium

by Brady Forrest | @brady | comments: 2

Microsoft Research is holding their annual Social Computing Symposium for the next two days. During the event their will be a number of speakers and discussion groups. The goal of the event is to bring together people from industry and academia. The four areas that are being discussed this year are Location (Monday morning), Boundaries (Monday afternoon), Play (Tuesday morning), and Social Objects (Tuesday afternoon). I've embedded the Live Stream above.

Here are the speakers:

Location (Monday morning, 10:30 - 11:30 AM)

• Brady Forrest
• Tom Carden (Stamen)
• Felix Peterson (Plazes/Nokia)
• Mary Hodder (Apisphere)
• Tom Coates (Yahoo! Fire Eagle)

Boundaries/Context (Monday afternoon, 1:30 -2:30 PM)

• Liz Lawley (RIT)
• Lili Cheng (MSR)
• Molly Steenson (Princeton)
• Kevin Marks (Google)

Play (Tuesday Morning, 10:30 - 11:30 AM)

• Elan Lee (Fourth Wall Studios)
• Jesse Alexander (Heroes/NBC)
• Paolo Malabuyo (Microsoft)
• Merci Victoria Grace (GameLayers)

Social Objects (Tuesday afternoon, 1:30 -2:30 PM)

• Jyri Engestrom (Google)
• Matt Webb (Schulze & Webb)
• Kati London (Botanicalls)
• Rob Faludi (ITP)

Updated: Corrected some speakers

Is Adobe Still Sleeping Well?

by Mike Hendrickson | @mikehatora | comments: 10

Last May, Tim O'Reilly posted a piece on whether or not Adobe was worried about the new threat to their dominance in the RIA space by the introduction of Silverlight from Microsoft. In a nutshell, the answer was no. From a book sales perspective, that was true and remains true today. But there is more to that answer than what appears at face-value from data on book sales.

Silverlight 2 is the product that Microsoft is backing in the RIA race. That in itself is worth, at least, some restless nights. Silverlight has not become a publishing event. At the present time, there are 10 Silverlight books published yet only one is on the current release and is truly a 2 book because it offers free, or paid, updates all the way through to a FCS launch.

But it does appear as though Silverlight is gaining some ground on Adobe. At least on Search volume. The image below shows the Google Trends for these technologies

silverlight [blue] adobe flash [red] adobe flex [orange] adobe air [green]

        A.    Adobe AIR Puts Companies on Desktops

        B.     Adobe Introduces Adobe AIR, Adobe Flex 3 Software

        C.    Nokia to bring Microsoft Silverlight to mobiles

        D.     Microsoft reveals new content partners, DRM for Silverlight

        E.    Microsoft to highlight Silverlight, 'Oslo' at show

        F.     Onstream Media Debuts Microsoft Silverlight Webcasting Service So the long and short of this is that Silverlight is likely not causing Adobe to lose sleep at night, but rather giving them one of those a rough, restless nights ... knowing that soon Microsoft will launch a credible product aimed squarely at them.