[QUOTE="StormyJoe"]
[QUOTE="lhughey"] Huh? M$ hires some of the best programmers in the industry, bar none. Take some time and learn about their interview process or talk to some of their developers and find evidence otherwise. Also take some time and read the book "Code Complete" which is an excellent guide to best coding practices. When you do, you will learn that the industry average for bugs found in software is about 10-15 bugs per 1000 lines of code. In released M$ products it is about 3 bugs per 1000 lines. Also, many of the things you listed are issues you personally have with products and not a problem with the CODING of them. You can blame some dislikes about programs on marketing decisions or interface design, but these things have nothing to do with programming. lhughey
Look, don't even get me started on some of MS's stupid bugs. My problem? Please. What about SSRS not rendering in FireFox and Chrome correctly, and MS's official stance is "Use IE"? What about the EDMX not recognizing return parameters from stored procedures? Or how log-shipped servers freeze at random? How about the GUI designer in .Net still - after 7 years of it being on the market - is rendered useless if you use master pages? How about how SQL Server never releases system resources?
Look, I like MS - especially .Net and Direct X... but putting them on the pedestal you are is a bit of a stretch.
It would be ridiculous anyone to say that a company was able to develop things without bugs. Just to understand the discussion properly, let me summarize whats happening. I stated that they have some of the best programmers in the industry (along with their QC department) and release products with LESS bugs than the average. Then you countered with 6 pointed "bugs" from products that are comprised of millions of lines of code (if not tens of million). The interesting thing is that most of the things you've listed aren't even bugs.
Your comment about SSRS not rendering correctly is probably related to the issue of IE and Webkit browsers displaying divs differently and have since the start. Not a big deal in the intranet environment (where SSRS is run).
GUI designer in .NET issues with Visual studio when using master pages? Is this really a big problem? Seriously? It seems to work just fine for me except CSS isn't propagated through from the master page to the page you're working on as you're designing it. But don't really recommend visually designing anyway. It usually ends with ugly code. But if you must, can be resolved temporarily by putting your css directive in the control you're designing with.
Not sure what you mean about log shipped servers?
Entity Framework not recognizing output parameters from sp's? People seem to be doing it just fine. But it seems like you have to do a small amount of extra work. http://stackoverflow.com/questions/9367688/output-parameter-with-entity-framework . I don't do a lot of work with EF. I prefer my guys work with LLBLGen. Its more elegant.
SQL Server never releases system resources?????? I find this to be laughable at best. SQL Server is the 2nd most used DB (bhind Oracle). We run on SQL Server and process a load of financial transactions every day. My days would be pretty rough if there was a big resource problem. It would be a hard sell for M$ to charge 7000.00 per CPU core if the product didn't work. Your issue sounds like its case of poor coding to me.
I don't like my developers using the EF either; but sometimes I lose that battle. As for the output parameters, it doesn't work - hence the bug. It is supposedly fixed in next EDMX release.
As for SQL Server, I know exactly what I am talking about. Try it yourself: load a big table as a table variable, and then go check your server resources. The amount of RAM allocated to SQL Server uses will go up, but never be released. I'm an MCSE in SQL Server.
Log in to comment