Microsoft Is Dead (2007)
paulgraham.com
paulgraham.com
On the flipside, the demise of Slack as an independent company and the slowness of Google cloud-wise shows that Microsoft is not "dead" in his definition.
The web / startup / open source / constantly changing world of continuous learning and building solutions looking for problems.
And the enterprise world of minimizing risk, meeting all day to kick real problems to someone else, and staying just far enough below radar to keep direct deposit and 401Ks humming along.
Make no mistake about it: Microsoft OWNS the enterprise world and has for 25 years. These people know little else. They do Webex and Skype, not zoom or slack. They use Microsoft Project and Sharepoint, not Trello. They outsource or purchase e-commerce, HR, and supply chain. If any programmer knows anything not Microsoft, they're either "not a team player" or "a god". Hell, even one CEO once told me, "I do not allow my people to use I.T. as an excuse. They have Excel." That's pretty much the thinking and I don't see any evidence that it's changing anytime soon.
Any enterprise people here have similar experience?
Oh, and can't forget wiring all of Production to specifically target MS SQL Server dialect
That MS security blanket is cozy for somebody though
This sort of hubris is common in startup and VC circles, where it's a necessary part of the narrative required to convince people that a scrappy startup has a chance at upending an established industry player. There is obviously some truth in it, as we routinely see new startups come out of nowhere to capture significant market share. However, these narratives can also be a trap that leads startups to underestimate the power and abilities of their multi-billion or even trillion dollar market cap competitors.
Keep in mind that the 2000s were a different era in the tech industry. If you had a tech product or service to sell, there weren't nearly as many tech-centric peer companies to sell to as there are in 2020. The big money focus was on enterprise sales, not scrappy SaaS startups with <$100 monthly pricing plans on their generic website pricing page. It was easy to feel that big companies like Microsoft just didn't get it, and that they were going to miss out on the new era of tech.
As it turns out, there's a lot more to being successful than simply building the best technology faster than your competitors. Companies like Microsoft were slower to catch up, but their distribution channels and finely-honed sales processes were harder to compete with than us startup people wanted to admit. It also turns out that with hundreds of billions of dollars in revenue to work with, big companies really can overcome their inefficiencies through brute force to deliver quality products.
This was also before the 2010 lawsuits against Silicon Valley companies for colluding to keep engineer wages down. Microsoft wasn't part of that lawsuit, but high engineering salaries in general weren't as easy to come by in the 2000s as they are in 2020. When this was written, working for a startup didn't necessarily mean you were going to earn less than working for a big company. Funding rounds were also smaller and fewer (less dilution) and engineering teams were generally smaller, meaning your odds of having worthwhile equity in a startup were better than they are today. The modern era of ultra-high FAANG compensation has been very effective at funneling top engineers into big companies and away from all but the most overfunded startups.
I do think that startups worry about Microsoft. Slack worries about MS Teams I believe. So I think Paul Graham looks like a fool on this one. And that’s ok, he knew the risk, and even laid out the terms which would make him look like a fool.
A little weaselly since that can be said about any company.
Microsoft had one of the greatest comeback. Just wondering if Oracle and IBM are capable of this ever.
This title does a great job of setting the essay's arrogant tone. Like the Cliff Notes, this essay is written for people who didn't bother reading the original Microsoft is Dead. It's not a walkback, not even a defense, just a summary.
> When I wrote that Microsoft was dead, I didn't mean it literally. I couldn't have. Companies aren't alive, so they can't die.
Companies can go bankrupt.
> In fact "Microsoft is Dead" was what we in the trade call a metaphor. I meant something else.
> What I meant was not that Microsoft is suddenly going to stop making money, but that people at the leading edge of the software business no longer have to think about them.
To say that someone is dead, if not meant literally, means to predict that he's going to die soon. It does not just mean that people no longer have to think about them. Metaphors are not arbitrary. Metaphors, like words and phrases, are usually based on conventions. You can't just write something and then claim that you meant some other thing. That's not how metaphors work. Note also the implication that people who don't understand that saying "x is dead" means that people no longer have to worry about x just aren't "in the trade", don't even know what a metaphor is.
But even the claim that people at the leading edge of the software business no longer have to think about microsoft turned out to be wrong. Maybe it's time for "Microsoft is Dead: The Cliff Notes: The Cliff Notes" to explain that this claim was also meant metaphorically?
That is completely true of course, but people said the same thing about IBM too. The rebuttal is always something like “but Azure” and yet they’re undeniably not the primary leader or innovator in the public cloud space. Most of their products are that way, outside of Office and Exchange and AD. Microsoft has gone from leading, to skating where the puck once was, and that isn’t a good sign imo
This is something I personally believed as well in the past, probably because of my experience with highly hierarchical companies and middle management.
This idea changed after hearing how teams work independently from each other at Amazon.
I'm not sure if this is really the case at Amazon, but I believe that if a company is able to organise itself so that you essentially have an internal market of tiny startups instead of teams (so they have freedom to pursue their products, they can fail and they can be hugely successful) you can replicate most of the startup benefits.
I've been trying to propose this model in the companies I've worked at - but generally there is always some Napoleone on top who vetoes risky bets or force teams to work on non productive endeavours.
You can get approved some practices that give more freedom to individual contributors, but important decisions always need to be directly or indirectly approved on the top.
I'd be curious to know what M$ did internally
You need a separate R&D division that plays by different rules than the established product division.
New product/market R&D is expensive, slow, and risky. If a company swings too far to the sales-oriented mindset, new R&D ventures can look very unappealing under typical models. Sales-minded executives would rather focus on the investments they know, such as hiring more sales people or increasing advertising expenditure.
Having a separate division responsible for R&D allows them to play by different rules and take more risky, longer-term bets. However, this is easier said than done. These R&D budgets are usually the first thing on the chopping block when sales are down and executives need to clean up the budget numbers. It's also extremely difficult to transition new products out of R&D and into their own, sustainable divisions. Some companies, executives, and engineers get hooked on tinkering with new product R&D and forget that they have to turn things into long-term product offerings. This is how you end up with constant product churn like Google's ever-expanding graveyard of abandoned products.
I’m surprised it was legal for MS to attach a Slack competitor to O365 and grow their monopoly so easily.
I understand that they had a harder problem working from where they were and trying to make it cloud, versus GDocs starting cloud from the ground up.
And death where? The application space? The cloud space? Most comments I've seen here suggest Microsoft still lingers in these domains. Its tentacles still manage to reach Cthulhu-like into spaces that weren't expected.
For people that think they can foresee the future of "tech" or whatever else: tell me how around 2000-2004 anyone could have foreseen that Yahoo Search will be completely smashed by Google Search. I mean how could anyone come to a facts-based conclusion that would draw today's picture (Yahoo essentially bankrupt, Google one of the most profitable companies in the world).
Oh, and the article was dead on. There's a lot of examples, but the only one you need to consider is that Microsoft now owns Github.
Ironically Apple’s ownership of iOS, which came out shortly after this was written, is now dangerous in the way Windows used to be.
I'm on Teams for close to a year now. It's great, much better collaborative tool than Slack - assuming your company buys into MS ecosystem enough to also use MS Office, Outlook and SharePoint. I keep hearing all these negative comments about it, but my N=1 experience since April disagrees. I'm guessing it's the matter of all these integrations.
I don't know if there is something better than Teams, but between Slack and Teams, Teams is vastly superior, even without MS integrations in my opinion.
The calls are bungled up almost half the time.
I get calls on both phone and laptop, and can’t accept for at least 10 seconds after I start hearing the incoming call sound.
And of course, there’s omnipresent “Poor network” notification, even when network is strong, leading to call drops or in the very least highly attenuated communication.
The moment you start Teams, it has to guzzle at least 0.5GB of your RAM.
Poorly designed software (or should I say bloatware)
Microsoft has reinvented itself again and again. Defying conventional wisdom. Multiple times. Under different leaders.
Was it able to do this because of its culture? Or was it just luck? It will make for an interesting case study :)
I'm too young, but I wonder if the thought of Microsoft not being the biggest forever in the 90s is equal to Google not being the biggest forever in 2020
There are always differences, of course, no analogy is perfect, but this is the basic pattern. Note that AT&T and IBM both fell from alpha predator status, but ended up in very different places, and the same is true of Microsoft and Intel, so Facebook and Google will both fall, but how far is not so easy to say.
The mismanagement of AT&T should be a course at Harvard Business School.
I can't imagine an OS that is very closely associated with pro gaming also being associated with grandmas.
A Mac is very definitely what you'd still give to your grandmother these days.
Anyone who wants a one-stop shop for doing computing is forced into Windows 10 by default.
Don't believe that? Name another OS you can play AAA games on, then fire up professional software suites (Office, Adobe CC) to do nearly anything creative / office / analytic-related, etc. so forth.
This article is idiotic. That statement is idiotic.
Microsoft should be fucking terrifying to anyone with any foresight. Yeah, they're not Apple... it takes them 3-4 tries to get shit "right", but once they do, its fantastic.
The entire Surface line up is proof of this. Until the M1 MacBooks, Surface Book 3 was hands down the best laptop you could buy. Sleek, powerful, good battery life, and the pen support basically makes it an iPad Pro / MacBook Pro in a single device.
Microsoft's first ARM chips will be garbage, sure. But their 3rd and 4th ones won't.
I'm a little terrified at the walled gardens that are going up, and everyone else ought to be as well. A world where Apple chips run on Apple OSes and Microsoft chips run on Microsoft OSes and Amazon chips run on Amazon OSes and who knows who else is going to jump into this ring, but I'm not sure this is the best direction for computing.
I'm very surprised that Apple hasn't tried to tap into this market. I miss gaming since I'm on exclusively on Mac. Once in a while I get an urge to set up Steam etc., but then the effort involved makes it tough for me to overcome the inertia so I leave it at that.
Why don't EA Sport etc., launch native app on Mac? Would someone from the gaming domain/industry comment?
At least start to read the article.
> They still make a lot of money—so does IBM, for that matter. But they're not dangerous
It's not "unfair" to not match your definition. The author is making the case about a particular definition of a predatory force in software, at large.
There's perhaps an argument that they are dangerous in a way we haven't yet seen, due to their involvement with the US military and the corruption inherent in that terrible choice.
Can you elaborate?
In some of their other businesses, I'd argue that they are very scary. If you work at AWS they are a formidable competitor. If you are in the video game industry, they are a behemoth. But very few startups can really compete in this space, other than for the niches.
On the other hand, Azure is the closest thing to an actual competitor to AWS, and in that sense Microsoft is very much not dead in the sense that pg means it.
Nope. Once the net became fast and mobile devices became prevalent, it was inevitable.
True, they were late to the game, but they still had enormous piles of cash, existing relationships with virtually all corporations, and a strong brand.
Nadella finally stopped leaving all the money on the table by pushing to embrace open source, web-based apps (Office 365), and Azure, and now Microsoft is back to being the third-largest company by market cap.
Frankly while I do use some web apps / services like Netflix, Amazon store etc. for which web app model is a natural the rest of my the software I use on Windows or Linux is native. The sheer amount of high grade consumer and pro level native applications for Windows is insane. I do not think Windows is even remotely close to being dead.
My workflow includes locally installed IntelliJ, Confluence, Jira, GitHub Enterprise.
And somebody on HN told that 90% of the people use Phone/Tablet for those tasks. Not PC.
From what I see in practice PCs and native applications are abundant in way too many work places.
That too. I also use a browser (or Workday's Android app) to do a lot of things that used to require a physical trip to HR or an unpleasant session with SAP.
A lot of professionals, depending on what area they are in, need to run tools that work best when locally installed (even though I saw some interesting things going on with CAD over web interfaces that'll end up being like Google Docs in terms of collaborating over complex designs). Besides, it makes it possible not to have a ridiculous 17" laptop heavier than most boat anchors and still run the heavy stuff on a beefy server somewhere else. Locally installed software is also a bit of a pain for the user, as they need to jump through different hoops to keep everything up to date, something that is simply not there with web-based software.
When computers got high speed always on connections, distributed computing became the norm. Kind of the same we did with X11 in ages past (and I'd gladly do again - I just love my IBM RS/6000).
I think Nadella took Microsoft for a turn no one had expected, especially tackling open source software so differently that they now drive the leading open source hub on the web. Given this, I'd say this article is an interesting historical document that bears little relevance today. It's one that would probably hold true if Microsoft had never reacted and still tried to drive their company mostly through Windows and Office sales.
The one point that I think still stands though is that "No one is afraid of Microsoft anymore" -- this is true especially because they couldn't enter the mobile market like they intended and that's where computing is radiating from today in so many respects (and especially those of which where Microsoft has traditionally often operated in).
But they're absolutely alive and kicking!
Sure, developer's perception of m$ improved, but the what I find surprising is then buiding Azure / Teams.
If Microsoft introduces a new product today, a new browser, a new toolset, a new standard -- even a new OS -- it Just Doesn't Matter to most people. You can be perfectly content ignoring them entirely and if it eventually rises through the market naturally, maybe then give it a bit of attention.
In Microsoft's halcyon -- smaller revenues but exponentially more influence -- Microsoft's every move shifted industries. You'd sign up to every beta program and read every tea leave to know what they'd do before it kills your product or renders your work futile.
That Microsoft is very much dead and buried.