Tag: microsoft

Architecture astronauts

I believe the future is one in which eventually all or most of our data will be stored in the cloud. Desktops and cell phones will, for most tasks, be terminals to the cloud, and so the concept of synchronization will be meaningless for most users. To be sure, there are solid use cases for synchronization but I don’t think sync is the best model for most people in most scenarios. And yes, Mesh does allow you to store data in the cloud as another data point in the mesh. But adding the desktop sync layer is, for most people, just not necessary, and I suspect will be generally perceived by mainstream users as an irrelevant added layer of complexity.

exactly. you only need to “sync” if you think in terms of offline applications. no wonder ozzie would push for that

The hallmark of an architecture astronaut is that they don’t solve an actual problem… they solve something that appears to be the template of a lot of problems. Or at least, they try. Since 1988 many prominent architecture astronauts have been convinced that the biggest problem to solve is synchronization. And what is this Windows Live Mesh? It’s a way to synchronize files. Jeez, we’ve had that forever. When did the first sync web sites start coming out? 1999? There were a million versions. xdrive, mydrive, idrive, youdrive, wealldrive for ice cream. Nobody cared then and nobody cares now, because synchronizing files is just not a killer application. I’m sorry. It seems like it should be. But it’s not. But Windows Live Mesh is not just a way to synchronize files. That’s just the sample app. It’s a whole goddamned architecture, with an API and developer tools and in insane diagram showing all the nifty layers of acronyms, and it seems like the chief astronauts at Microsoft literally expect this to be their gigantic platform in the sky which will take over when Windows becomes irrelevant on the desktop. And synchronizing files is supposed to be, like, the equivalent of Microsoft Write on Windows 1.0. It’s Groove, rewritten from scratch, one more time. Ray Ozzie just can’t stop rewriting this damn app, again and again and again, and taking 5-7 years each time.

provides the takedown on “live mesh” that the lightweights at techcrunch were not able to do

Laundering Office

Microsoft has announced that it will – with a European partner – contribute to an open-source project for reading and writing Excel, Word, PowerPoint and Visio files. The Apache POI API is already used by various open source projects to handle Microsoft Office documents, but work is needed to add Office Open XML support as used by Office 2007 and 2008.

looks like the sourcesense guys are helping microsoft to establish a standard no one wants. not sure that is progress.

Robot programming models

a model that deals with the inherent complexity of concurrency, and the coordination or orchestration of what’s going on. This was the whole reason for choosing the CCR and DSS pieces for robotics. This was actually an advanced programming model designed not for robotics per se, but as a general purpose programming model. We put it into the robotics SDK as a way to test this out, but now we’re seeing that people are lifting the hood on the engine inside this SDK and finding other uses for it. We have people who are using it to build trading systems, who are doing large data-set scientific modeling, the folks at MySpace are using it to manage their server farms.

need to check our the MSR robotics SDK

Sneaking behind IT back

By easing the grassroots adoption of Apps, Google hopes to begin reshaping the way employees – and then employers – think about personal productivity apps. The idea isn’t to displace, say, Microsoft Office, but to complement it, providing a simple way to collaborate on documents and other files. As the use of Apps becomes more established, it becomes natural for companies to formally adopt the programs to gain further capabilities and controls. In the process, they’ll probably also sign up for the premium edition, which requires a $50 per user subscription. And then, in the long run, people start realizing that they’re doing pretty much everything they need to do within the web apps, and they start asking themselves: why exactly are we still licensing the old-fashioned versions of these programs and suffering the expense and nuisance of installing and running them on all our PCs?

lets kill some sharepoint revenue!

.aspx considered harmful

I guess I’m extra-sensitive to the .aspx thing now that I work for Microsoft, because I know that to folks outside the Microsoft ecosystem it screams: We don’t get the web. It’s true there are plenty of .php and other extensions floating around on the web. But non-Microsoft-powered sites are far more likely to suppress them than are Microsoft-powered sites, because you have to go out of your way to get IIS and ASP.NET to do that. I hope that cool URIs will become the default for Microsoft-powered websites and services. Meanwhile, there are a variety of add-on URL rewriters for IIS that can streamline and normalize web namespaces. I wish they were used more extensively.

Jon Udell it only took them 10 years to get clean urls. wtf?