I’ve heard an ex microsoft employee said in a blog once that the windows team has no seniors. Anyone who has worked there for one or two years has left for better employers. Nobody knows how to refactor or maintain old codebases, so instead, they just write new things on top of the old things. The windows kernel has hardly changed since XP.
This makes sense, most of that explanation in the screenshot reeks of novices working with something they don’t understand.
Copying and pasting a current example and changing the names… yep.
Instead of making it worse you could extract it to a new file. Make an interface. Write a unit test. Anything.
The guy wonders why the file is 15k lines long and then describes exactly why.
Right? Like my dude, bare minimum at least write down those steps in a text document so you can reference it the next time you have to add something. Bonus points for putting it on some shared internal wiki or whatever Microsoft uses.
I don’t think anybody gets paid enough to write that down. In fact, they might get punished for wasting company time. They could open source it and people would automatically fix these things. Who knows.
Or write a tool that can do all these steps for you, reliably!
This sounds 100% credible, based on the outcomes we can see
The windows kernel has hardly changed since XP.
Windows NNT when? Surely from a business/competition perspective they can’t let Linux get that many years ahead of them in terms of kernel optimisations?
thats what happens when short term profit is king I guess
So that’s why they shipped like every past systems’ control windows with every new version. Not for people’s convenience. Because of spaghett
Nobody toucha my spaghett
Which control panel? There’s like 20 of them and a new worse one gets added every other year.
… This seems like standard GUI stuff. The interface component defined by some markup, with a hook to some programmatic behavior, and perhaps a corresponding resource ID
I have no way of verifying this is real, but I wholeheartedly believe it.
pretty much every windows GUI framework is trash or a pain in the ass to deal with except for Avalonia (my beloved), but it’s more cross platform.
I’m not sure if this is 100% real but it very well could be. although imo makes me think of skill issue (not because the system makes sense, but these problems don’t really seem like problems to me, just minor set backs)
I haven’t done much with UI in general, but the one time I thought of making some UI stuff in windows I gave up.
Even modifying an existing .net program someone else made for a feature I wanted was a nightmare.
Yep, I was shocked to see that there is no defacto 1st party framework and during my time searching online I found lots of “use x, use y, no y is dead and none uses it, no x is terrible” which is how I found Avalonia.
I still don’t think there’s a solid Windows gui framework, but I haven’t looked in years.
This is why everything is a goddamn web app now.
well, no. everything is a god damn web app because everything runs browsers.
so why write native (device) applications if the device can run a browser ? just write code for the browser, which also runs on desktop. now you have a cross platform app without needing 5 different teams
Thanks Ballmer for QA.
Then you have to go into a resource file and find a very specific resource ID for your control panel string, and create a new resource ID to me it to.
Ah yes the joys of working with Microsoft Foundation Classes (MFC), Back in the day I supported a VS6.0 application, you have room for 65535 UI elements in an application (Including DLL’s) I had to split the ID’s up in ranges to enable adding new elements in a sane way.
The “True Facts About Microsoft” and Zefrank reference got me :D
OH MY F… GOD! I knew it is witchcraft but I didn’t knew that is is so awful!
At least control panel is better than “Settings” trying to find shit in that is hell.
I wanna believe that this is fake.
But I expect it is not.
I’m now wondering if microsoft still even has the legacy control panel code.
Well that was interesting to read
Can confirm. I worked as a contract program manager for Microsoft with O365, Azure Gloval Ecosystrm, and yes, the dreaded Windows team. I wakk out out my last two Microsoft jobs in the middle of a shift. I would do it again.
