Skip to main content

Longhorn Outruns XP, Threatens Tiger - Really???

Michael points to an article in eWeek about how Microsoft may be ready to take on Apple after all but the entire article is based purely on speculation and even admits "But if Longhorn slips into 2007, Apple could have the next big cat version released or at least waiting to spring out."

This is the kind of journalism that belongs in weblogs moreso than a paper but then this is why eweek and other online journals are really having a rough time with bloggers and keeping readership up.

1. When Longhorn ships or even produces a real beta, then we can start a real comparison. Even with all of Scoble's comments about how "sexy" Longhorn will be (actually I think that was Vic's comment), the rhetoric is all about "wait and see - you'll love it".

2. Apple typically keeps everything under wraps until they're ready. So even guessing what's coming out from them is a matter of conjecture. Apple was rumoured to be switching to Intel for years but it only hit this week.

Both companies have things up their sleeves that no one knows about. Listening to the Gilmour Gang on podcasting, I really noticed it. Adam Curry commented that MS didn't really have a clue (my word, not his) about how to deal with podcasting and yet he was there a month ago (where they sent him a gift) and I'm sure they had some discussions back then. Sure, there are some at MS who would look at Podcasting, or RSS or whatever as a passing fad. But I would still be very surprised if they aren't able to do something.

Yet everyone loves Apple for that reason - they love to surprise. Very few people knew about podcasts on iTunes until it was announced. Microsoft went through a lot of speculation on Longhorn and now they're being quieter about it.

So if you want to compare operating systems, compare Tiger and XP. If you want to compare on upcoming systems, compare public betas. If you want to talk about what may or may not happen, go to Slashdot.

www.kogeler.com - michael's blog: Longhorn Outruns XP, Threatens Tiger

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...