November 17, 2022

The lack of vision, guidance, and respect in North American IT is frightening

The lack of vision, guidance, and respect in North American IT is frightening

Anyone who has experience running even a small business, making payroll, and paying for goods, service, and taxes knows this simple truth: everything has its price, everything comes with a cost, and resources wasted cannot be recovered, unless one is a global monopoly that can simply resort to twisting customer's hands into obedience. So, let us take a look at waste.

Microsoft is indisputably a global monopoly on the OS, DB server, Office, collaboration, and now cloud. MS regularly scraps the technology that it has, revamps it totally top to bottom, and comes up with a completely new way to do things. So happened with its .NET that has been revamped several times already. Reasonable developers curse the learning curve of WPF that replaced WinForms. They also curse shortcomings of Entity Framework that replaced ADO.NET. I can go on and on about this.

Some believe that our society is going through recession. I do not know. Maybe it is, maybe it is not. I think that it is economical to go up and down, but what do I know? But if it truly is in a recession, then it lasts since at least 2000. Since then I have not seen a day when people did not lament difficult situation in the economy.

So, why, I want to ask, why do you waste billions on revamping? Why do you make millions of developers around the globe go back to school, figuratively speaking, every few years? Why do you scrap and build from scratch instead of evolving your products?

Everyone who has been around computers knows that in the OS domain MS mostly redesigns the icons. Seriously, every next version of their products is the same old crap but with icons that no one recognizes and has to re-learn from scratch. I want to slaughter their graphic artist and their boss for that when I am forced to use new Office, Teams, Windows 7/8/9/10/11/12 whatever (they promised no more numbers after 10, by the way. Where is their promise now?).

Consistency, anyone? When one submits a bug report into MS tracker, their Chinese support closes it with 'unable to prioritize'. It means too busy to fix it. We know what they are busy with: redesigning icons.

The velocity of them machine-gunning new C# standards is terrifying. They come up with a language that is totally revamped, for all practical purposes, almost once a year. When we look at changes we can see that they are totally unnecessary. Yes, now developers can save a few keystrokes but they have to go back to school and learn what the hell MS changed the syntax to. Multiple return values save everyone the declaration of a Touple(). Big effin deal! await async saves us from typing Task.WhenAny(). Whole lotta easier! => saves us from {}. A huge saving! Nullable types are more of an annoyance then benefit. null! is going to make our lives so much simpler. All while complete showstopper bugs and intentionally introduced bottlenecks and shortcomings exist for decades. Only recently they introduced .Shared, to simplify multi-threading. About effin time! Like, 2 decades too late, if you ask me.

Do not get me started about glorious entity framework that is the fad of the day! Writing DB contexts must be so much easier and more clear than a few SQL DDL statements that everyone is craving for DB contexts with their decorations: un-debugable, un-testable, write-and-pray piles of C# garbage. Ever thought about expressing your entire database in one C# class? Your dream comes true with EF. Congratulations!

When multi-trillion $ global monopoly all it does is waste, someone should take a sober look at them and realize that something is wrong. Anyone?

Posted by: LinuxLies at 11:00 AM | No Comments | Add Comment
Post contains 644 words, total size 4 kb.




What colour is a green orange?




17kb generated in CPU 0.0084, elapsed 0.0814 seconds.
35 queries taking 0.0763 seconds, 127 records returned.
Powered by Minx 1.1.6c-pink.