Skip to main content

What companies plan their purchases strategically?

Craig Bailey posted this link on Twitter regarding Sun's lacklustre performance last quarter -
Jonathan Schwartz's Blog: Our Q3

Choice quotes:

"Why don't you just stop giving your software away?

Because we prioritize developer adoption. Let me give an example....the MySQL team had scored a design win - ahead of the proprietary competition. What should we have charged them beforehand? No matter what it was, they wouldn't have used the product - startups and developers don't pay for software...We didn't pay them, the MySQL team earned their adoption."

"Why does Sun's CEO waste time writing that blog?
Because I believe in providing clarity surrounding our strategy and operations - not just once a year in the Annual Report. I believe clarity behind our direction is useful for our shareholders, customers, partners and employees."

It's a great post, full of honesty (as far as I can tell) about what's going on at Sun and it contrasts with the Microsoft/Yahoo debacle.

The most disappointing thing I have heard regarding the proposed (now dropped) merger was Balmer's assertion that he wasn't buying Yahoo for the technologies but rather simply for the online advertising business. While I can appreciate that to some extent (there was a fair bit of overlap) , it's also a bit strange because both companies are now getting known for their ability to scoop up companies and then let them languish. I think Microsoft does a far better job of integrating their purchases into their entire system (consider FoxPro into SQL and other technologies) but some obviously don't think so.

Microsoft does a great job with their development tools and getting the message out (Rock the Launch was a great example of that) - but their direction can be spotty or there is a rush to get something out and then to correct it later.  And yet, there are lots of technologies within Microsoft just dying to see the light of day, be they internally-developed or purchased.

There was a FoxPro devcon quite a few years ago when the mantra was not "Fox Rocks" but rather "Challenge Me" - the premise being that you could do virtually anything with FoxPro.

Microsoft continues to do that but it seems, to me at any rate, that it's in areas that they are already behind the curve. As a result, it's seen as a "me too". Consider that Yahoo introduced Pipes before PopFly and even though they are different, they are also similar enough to let people make a connection.  As Joel Spolsky wrote, even Mesh seems like something that's been done before.

Where is the Excel 3.0 of the next generation of web apps?

Microsoft - don't just challenge me - challenge yourself. You've done it before - show us you can do it again.
Labels:

Comments

Post a Comment

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .
4 comments
Read more

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...
11 comments
Read more

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...
Post a Comment
Read more