I brought it home and plugged it in. Everything came up, looking good. Then I got this
And there it is! For a moment they had me believing I would not be experiencing the regular disgust at the pathetic quality of their products. More money than anyone. More resources, more know how, more failure! WHY?! You could have made it work Microsoft! I know you could! Oh what I would give for you to make something that works!
Oh yes, it's connected to the internet alright. The failure belongs to Microsoft. I'll probably wind up having to update it manually. You know I've never had to do that with any of my Sony products, which I will gladly continue to pay for. I believe that makes the score PlayStation 4, Xbox 0. So much promise and so little delivery, this is why I hate Microsoft today. How about you?
Despite what the name may imply, this is not a Microsoft hate site! Microsoft does some really good things. My purpose here is to shame Microsoft into fixing the absurd things they let go unaddressed. Broken links in help files, fixed-size windows too small to read the information they contain, and any other quality control failure they could've gotten right if they just had a little bit more money.
Showing posts with label Broken by default. Show all posts
Showing posts with label Broken by default. Show all posts
Wednesday, August 19, 2015
PlayStation 4, Xbox 0
I've always been a PlayStation guy. Given the theme of this blog it shouldn't be hard to figure out why I would avoid the Xbox. I just can't bring myself to support a platform that could be the best but is just so disappointing. However, for free I might just use an Xbox. Recently, a friend from church gave me an Xbox 360 so I could play games with him. Sure, I would need to sign up for Xbox Live and buy a couple games, but that didn't seem like a big deal if my friend wanted me to play badly enough to give me an Xbox.
Thursday, August 6, 2015
Broken By Default
A web application of mine started timing out waiting for a SQL query to return results. The query ran in less than a second in enterprise manager, but took more than 30 seconds when called from the web server. I was amazed to discover after Googling I was amazed to discover that to get the query to return in less than one second from the web page you have to put the words SET ARITHABORT ON in the stored procedure.
I'm not terribly surprised given Microsoft's track record that the default setting for ASP.NET pages causes them to break but why would it be different in enterprise manager than it is for applications? It sure does make troubleshooting take longer!
To break it down, just for you, Microsoft --
I'm not terribly surprised given Microsoft's track record that the default setting for ASP.NET pages causes them to break but why would it be different in enterprise manager than it is for applications? It sure does make troubleshooting take longer!
To break it down, just for you, Microsoft --
Problem #1: ARITHABORT is set to off by default for ASP.Net applications. This causes applications to work initially and then fail some random time later.
Solution: Set ARITHABORT on by default. Thanks for assuming that I wanted my query to take as long as possible, but I'd really like it as fast as possible.
Problem #1: ARITHABORT is set to different settings in SQL Enterprise Manager and for applications.
Solution: Set them to be the same! It sure would be nice if those troubleshooting didn't have to look for a secret switch to flip before the SQL behavior becomes consistent.
Solution: Set ARITHABORT on by default. Thanks for assuming that I wanted my query to take as long as possible, but I'd really like it as fast as possible.
Problem #1: ARITHABORT is set to different settings in SQL Enterprise Manager and for applications.
Solution: Set them to be the same! It sure would be nice if those troubleshooting didn't have to look for a secret switch to flip before the SQL behavior becomes consistent.
Subscribe to:
Posts (Atom)
