Friday, December 12, 2008

When Good may not be so

The other day I was reading some news that NetFlix was laying off support people due to the fact that their application was more stable since they started using Silverlight.

Are Netflix layoffs Microsoft's fault?

This made me reflect on "how good is .NET and Silverlight".

In this case "Good" is a relative word and that relativity prompted me to write this blog.

As an architecture I really like .NET it is a first class runtime platform. As a developer I love working with Visual Studio .NET. I think it's the best development environment around. As a designer, Silverlight provides all the flexibility to achieve the look and feel I want. So on that regard, the tool set is good.

On the other hand as a consumer and software user I don't understand why I should be installing runtimes to view a web page. Why I'm not able to view that same web page on my hand held or on my PS3. Why do I have to user Windows when the web was built platform-agnostic. In that regard, the tool set is bad. very bad.

But there is no surprise here. Microsoft bases his commercial practices on a monopoly (or quasi monopoly if you like) and while they enjoy a huge advantage on the desktop, they know, as any other person following the evolution of personal computing, that the next grow potential is on ubiquitous computing. Handhelds, TV set tops, kiosks, on-car access, etc. where they don't enjoy that advantage.

When companies decide using a development tool, they should not only look at the developer productivity but mainly at the business opportunities out there. By using .NET/Silverlight they are playing in the hands of Microsoft which may have one of two outcomes:

If most companies do it, they will enable a Microsoft monopoly on the ubiquitous computing space with all the bad consequences that entails

If most companies realize that there are more opportunities than just the desktop, they will be left with an application that can only run on a small percentage and will be out of the market.

Both scenarios are bad, either for the consumers, for the company or both.

In summary:

Companies creating internal applications where they control the platform the users are using, will get great gains from going Microsoft.

Companies that rely on external users are shooting themselves in the foot especially knowing that there are many other development platforms that rely on open standards to achieve the same effects.

Monday, December 01, 2008

Why hacking the iPhone?

After I read some news about hackers being able to run Linux on an iPhone, I went to read the reader's replies.

I was surprised to see that there were many people asking "why?" as if this was a useless exercise.

For them, here are some answers;

  • Because it is there.

  • Because it was fun for the people that did it

  • Because they may have learned something while doing it

  • Because it proves one of the benefits of an open environment: portability.

  • Because that is how we've gone from scavengers to hunters, to farmers, by trying things that aren't status quo, as futile and useless as they may seem.

Will it have a practical application down the road? who knows, that's not the important news here.

Why do people climb mountains and swim across a channel?

Because that is a challenge that can be conquered

Why is there a "Perimeter institute for theoretical physics" where people research and think about science without a clear application?

Because that's how knowledge is acquired and transmitted. That's how we've evolved.

I'm not expecting those dinosaurs to understand this but I am still surprised that they haven't gone extinct.