Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Should they have, though?

I agree they should have been penalized (ideally more harshly than they were) for their legendary anticompetitive behavior, I'm just no longer as sure that partitioning the company out into distinct divisions would have been a net gain for the consumer as I used to be, especially against the specific behaviors they were accused of.

How, for example, would breaking up Microsoft into distinct divisions prevent, say, the OS division from enforcing the same anticompetitive requirements on companies licensing the OS?

I also think consumer perception of what's reasonable in an OS has shifted since then. I don't think any of us would argue now, for example, that shipping a desktop OS with no browser installed by default would be a reasonable choice. (Likewise probably a media player.)

Should it be impossible to uninstall? Maybe not, but there's a not-unreasonable argument to be made for preventing someone from winding up in a situation where they have no browser installed at all and can't look up how to fix it. (Having no media player installed is obviously less catastrophic.)



If you were a competitor at the time, the Halloween documents were NOT NEWS to you, they were just a frightening admission of what everyone knew MS was already doing.

Yes, they absolutely should have been broken up into fragments, if not crushed and handed out to the rest of America for free.


> How, for example, would breaking up Microsoft into distinct divisions prevent, say, the OS division from enforcing the same anticompetitive requirements on companies licensing the OS?

That kind of breakup wouldn't have solved that anti-competitive problem, but it would have solved others (e.g. the Office Team being able to use undocumented OS APIs to get an edge on competitors).

Though, personally I kinda think a breakup of a tech monopoly should be more extreme, for instance by breaking it up by division and splitting some of those divisions further into competitors (e.g. split the OS division in two, each with their own Windows fork to sell, and all the Windows trademarks go to some independent interoperability consortium).


> it would have solved others (e.g. the Office Team being able to use undocumented OS APIs to get an edge on competitors).

I mean, it might have prevented learning about and using new undocumented APIs going forward, but it would be in none of the newly-broken-up companies' interests to break the existing usage.

> splitting some of those divisions further into competitors

Even that I'm skeptical of - first, because you'd need enforcement to prevent them from simply merging again after a while (glares at Ma Bell breakup companies reforming into a few huge companies which usually deliberately avoid competing in markets), and second, I'm not convinced that deliberately fragmenting Windows into 2 distinct codebases is beneficial for consumers?

Even assuming you could avoid one of the two competitors simply winning the vast majority of the marketshare after one round of OS upgrades, you'd likely end up with mutually incompatible API surfaces, thus breaking one of the main reasons people like Windows - compatibility.

(I still claim, though, that given two initially equal products and equal resources, that one will probably relatively quickly eat the other's lunch. Look at what's happened almost every time a large open source project has had a high-profile fork - look at egcs and gcc, or OpenWRT and LEDE, or libav and ffmpeg.)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: