At first I thought your comment was a bit harsh but actually now I think about it the Xbone is buggy as fuck compared to the 360.
I'm hopelessly addicted to COD3, and if I had a quid for every time that game has crashed on me I'd have a lot of pound coins. The OS is indeed slow, and the network setup I've had to create for games to work reliably is less than ideal. The OS is clearly trying to do a lot, but does all of it slowly and unreliably.
It's not as awful if you compare it to the gen 1 360 (RROD anyone?) but it's still arguably worse. Granted this one doesn't destroy itself during standard operation, I killed two of the gen 1's myself before getting an Elite, but while the hardware is definitely good the OS is just absolute garbage. The network stack was written by monkeys, it's the only explanation.
We had a couple friends over to Legendary crawl the Halo MC Edition campaigns and we had to power cycle the units three separate times over the course of the 3 and 4 campaigns because the damn things just would not see each other. Insanity.
Edit: A LOT of it's issues I think come down to how dependent the One is on Live compared to the 360. Live was a big part of the 360 too but it could function just fine without it, but I remember in Christmas of 2014 I had bought the wife her XBox One which came with AC: Black Flag. That week when lizardsquad or whatever took down XBox Live, I had to PHYSICALLY DISCONNECT the One's cable to allow it to login properly, it just could not handle the idea that it had Internet access but Live was down. That kind of omission from the handling speaks volumes as to what the rest of the code must look like.
It's not as awful if you compare it to the gen 1 360 (RROD anyone?)
Eh? I had (well, it's still in the garage) a launch day box. It did the RROD under the extended warranty period, sent it in and got it refurbished, it ran until the Xbone launched. A one-time problem with a one-time fix that had a quick turnaround. Your mileage obviously varies, as did that of others, but for me over the course of nearly ten years, it was a minor inconvenience.
In comparison to the Xbone, the foibles of which I endure nearly every time I turn it on. I dropped my Xbone in the DMZ and called it good, and that works well. But that does me little good with my friends as we ask, "why can't I join? Why doesn't chat work?" My personal fave is the "it says my NAT is 'strict', but it was 'open' yesterday and I haven't changed anything." That even happened to me once. Now how the network stack thinks that a machine with its own IP address, sitting wide-open exposed to the Internet at large, is behind a NAT befuddles me.
The failures of the foxconn 360's were incredibly erratic, some died after a month, others are still working. A company that produces hardware that fails with such a range is somewhat more worrisome than one that produces it where it fails consistently.
And yeah I too noticed oddness with DMZ. For a long time the only way to have two in the house was to have mine in the port forward (since we used mine as a media center and it needed access to the other bits of the network) and to have the wife's DMZ'd, but neither worked terribly well and we would run the gamut from Strict to Open with zero predictability. UPNP seems to keep them happy though, so whatever works.
I'm hopelessly addicted to COD3, and if I had a quid for every time that game has crashed on me I'd have a lot of pound coins. The OS is indeed slow, and the network setup I've had to create for games to work reliably is less than ideal. The OS is clearly trying to do a lot, but does all of it slowly and unreliably.