Tagged: microsoft

Open Source, the beginning

This is the first real post in the Open Source category of my blog, but one of many in the blog as a whole, and one of many to come on Open Source.  If you have read my blog from the beginning you will know that much of my recent experience is with Enterprise Infrastructures, and that has to a large extent involved software from IBM/LOTUS and Microsoft.  Integration with Unix systems being through well defined and mature interfaces like NFS, X-Windows and DNS.  This means that I have a lot of familiarity with Microsoft and I am open about the fact that there are things to admire about Microsoft, (and many things to not admire of course), however I have a long held low tolerance for Zealotry which I have talked about previously, but want to expand on here.

 

When I say I dislike Zealotry, I am not talking about passion, I am talking about taking a stance for or against something that can not be defended by rational argument.  This causes me a problem, because as an enterprise architect, I spend my life having to defend the decisions I take with rational argument, and for me, ‘I …

Microsoft and integration

I have thought for a long time that Microsoft don’t make much use of their own software to build pre-integrated solutions for their customers, (unlike Oracle for example).  They seem to have caught onto the idea at last, (not from listening to me though :-)).  Anyway a few months ago they started to talk about solution accelerators, which are solutions built from sets of MS products with associated processes, procedures and best practices as well as custom systems integration.  These solve particular business problems, like for example, the process of hiring new employees.  There is also evidence that Microsoft is doing the same at the infrastructure level where the range of tools available to them is even richer, SQL Server, BizTalk, SharePoint etc.  This is a good example:

Microsoft also plans to make available to enterprise partners a “zero touch provisioning” accelerator that will enable end users to self-service tasks such as requesting the installation of an application or resetting a network password.

“We built in a rules-based engine based on BizTalk that can automate requests, get approved by a manager, and install a new application,” Hassall said. “And the opportunity is not just for desktop deployment but add-ons for server …

Office news

Office news. 

A new version of open office is available.  The main improvements are:

Enhancements to the open-source productivity suite include support for PDF and XHTML exports and improved compatibility with Microsoft Office, according to the OpenOffice Web site. The new release, for example, will support forms conversion within Word documents and import text document layouts with more fidelity. OpenOffice 1.1 also boasts enhanced support for mobile device formats such as Palm’s AportisDoc, Pocket Word and Pocket Excel.

IBM has ideas of its own, taking a thinner approach with its WorkPlace products

A wild card in the Office wars is IBM, which plans to offer server-based word processing, spreadsheet and presentation functionality to buyers of its WebSphere portal. At the very least, that could allow large customers to negotiate better Microsoft Office pricing/licensing, observers said. (See IBM Plans Sneak Attack On Microsoft Office.)

The MS Office team are majoring on quality for their next release, does this imply major changes, requiring major testing, or just good practice?

Software development, especially for a product as feature-rich as Office, is a repetitive process comprising what can seem to be endless feedback loops and rework.

“We’re trying to reduce the iteration of …

The five top objections to open-source

Computer World has an article on this topic, most of which has already been debated many times with simillar answers to the ones that CW gives.  However I repeat the list here, because item 5 on the list is actually new to me:

  1. Support availability

  2. Functional limitations of the software

  3. Software license terms

  4. Rapid software release cycles

  5. Package road maps or future plans

Items 1 to 4 are answered pretty well, and I don’t think are a major concern now for most companies and the service offerings are developing at a rapid rate.  However here is the answer to item 5:

Package road maps or future plans are important to most companies. Major vendors tend to heavily promote their road maps, even to the extent of publicizing future capabilities years in advance. Of course, there is no promise that any advertised feature will ever see the light of your computer display. Not all vendors publish such road maps, and some share them only with strategic accounts under nondisclosure agreements.

Some open-source groups publish road maps, and some do not. At times, the stated goal is to mimic the functionality of a commercial package, though when any particular feature will appear …

Microsoft: Linux isn’t cheaper

Yet another Linux isn’t cheaper story from Microsoft.  I don’t get the focus on cost all of the time.  To me cost is a small part of the story.  The Linux/Microsoft debate needs to consider the following in this order, (client side):

  1. The application portfolio that needs to be delivered to the client device.  In most enterprises there will be hundreds of client applications, many of these won’t be deliverable on Linux even using emulation.

  2. Whether you believe in Microsoft’s value proposition.  Only Microsoft has the ‘integrated innovation’ value proposition that links client, office tools, infrastructure services and application services.  If you buy into that value proposition then you are probably going to continue to use office and Windows.  My view right now is that MS is doing a pretty poor job of telling us what that value proposition is in their next generation products,  I think because they are still figuring out how to move forward when they are dragging such a legacy behind them

  3. Whether the user-base can be segmented.  Its likely in every enterprise that some users will be best suited to Windows Portables, some Windows Desktops, some Linux and some thin client technologies or one sort …

More loss of direction around Exchange?

Ed Brill makes a point in one of his posts about the woes of the Exchange Group in Microsoft, here is the guts of it:

It hasn’t been a good few months for the Exchange product team at Microsoft.  First the Outlook team ships an updated connector for Lotus Domino; then they dismantle their own roadmap; and now they are facing internal competition:

“Our first product here is going to be using Outlook that uses the Hotmail e-mail infrastructure. So you don’t need to have an Exchange Server if you’re a small business; you can just use Hotmail and you can have that synchronized experience, as well as the calendaring and everything else with other people who are on Hotmail.”

Sort of confirms the feeling I got when I posted on a simillar topic a while back.  Then I got a bit more encouraged when I posted this.  lets hope for some clarity soon!

It’s when I see something like this that Microsoft really disappoints me!.

I have just been sent details of this InfoPath web application by Microsoft.  I should have been pleased, but I was very disappointed, not by InfoView which seems to be a great way of publishing an InfoPath form so that it can be completed using a web form, but because Microsoft did not ship it!

 

Microsoft would have got such a different reception and eliminated a lot of trust issues if InfoPath had been positioned as a web form designer, offline editor and aggregation tool, with a complementary web forms interface for those not able to take advantage of the native client.  I can not believe that developed in parallel with the thick client developing the web client would have been that big a deal either.

 

Anyway Microsoft chose a different route and instead of being seen as producing a great innovative standards based product that demonstrated the best of rich and reach, they chose a route that exposed them to constant criticism over attempting to lock people into Office and Thick Client technologies!

 

Come on Microsoft examine everything you are planning from the perspective of those who are uneasy about your track record,  …

Goodbye to the Tablet

There is a flurry of debate in the blogs because Peter says, I Still like the tablet.  But I am all out of love, well I have a story to tell about Tablet love as well.

 

I got my first Tablet, a HP TC1100, in January and it was love at first sight,  I just took to the slate format and at the time forgave the terrible keyboard, (although it didn’t take me long to remember my old IBM keyboard with increasing longing).  I wrote all about my early experiences in my tablet blog.  Well my circumstances changed and I found myself working mostly from home so the mobility benefits I was getting from the tablet reduced and I started to look at the platform more objectively.  These are some of the conclusions that I came to, but I think it’s a pretty personal view so don’t expect any conclusions that I draw to apply to you.

 

The Tablet didn’t work for me when I was mainly deskbound:

 

  1. I love screen real estate, before I had a Tablet I had a 1400*1050 resolution ThinkPad A20p, it had a great keyboard …

More integration between WinFS and XML

Jon Udell of Infoworld says in his blog:

Meanwhile I’ve been working on a story about Longhorn, for which I had long and an extremely interesting interview with Quentin Clark, the architect of director of program management for WinFS. I’d like to transcribe the whole thing to post along with the story, when it runs, but the upshot is that Microsoft is planning more and better integration between WinFS and XML — both in terms of data definition and query — than I’d previously heard, which is welcome news

I’m pleased too because it means we are one step closer to the vision of WinFS that I have been talking about in my blog.  Complementary and not competetive to the web.

He then goes on to talk about the different types of search experience:

It seems clear, though, that whatever can be accomplished by means of what I’ve come to call “managed metadata,” we’ll always want that Google effect to be happening in parallel. When asked about the Semantic Web and RDF at InfoWorld’s 2002 CTO Forum, Sergey Brin said:

Look, putting angle brackets around things is not a technology, by itself. I’d rather make progress by having computers understand …

Rich Versus Reach – my perspective

The Rich versus Reach debate is raging in the blogsphere at the moment.  The debate has been very healthy with less of the usual emotional clutter that clogs up most debates that touch on the future of Microsoft.  I am an enterprise guy, with a complex home network as well, which gives me an interesting perspective so I thought it would good to pull some of the threads together.

 

The debate mainly started with a post by Joel on How Microsoft Lost the API War it’s a good article at the start but then begins to lose its focus and starts to make some bold assertions which are hard to substantiate.  These are partially rebutted by Olivier Travers in his post Microsoft Lost the API War? Not So Fast and more thoroughly by Robert in his post Seven Reasons Why the API War is Not Lost After All, which comes over a bit evangelistic but is still a good contribution to the debate.  Robert introduces a new perspective for me on Avalon where he describes how it may be possible to download XAML directly from the web as an alternative UI experience to HTML …