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.
The “True Facts About Microsoft” and Zefrank reference got me :D
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.
I don’t think this is legit because even as I was reading it, I was expecting it to sound a lot worse than it ended up sounding. Like, it didn’t sound great or anything, but it didn’t sound nearly as fucked up as I would expect firsthand descriptions of piled-on legacy code to sound after almost 50 fucking years.
Seriously, it doesn’t sound great, but it sounds about what you might expect wiring up a new UI widget in WPF or whatever the latest thing for native Windows is. Sounds like what would happen if you started developing a Windows app using the Microsoft scaffolding and never applied any kind of software architecture beyond that and it just grew and grew into a big ball of mud. Exactly what I would expect given the quality of so many of their frameworks, and I say that as a professional dotnet software engineer.
But did you read the last line? This isn’t classic control panel, this is the new control panel.
Sounds like classic junior engineer shit. “Let’s do a big rewrite!” Followed by everything going to shit because they don’t how to create good maintainable software architecture and for whatever reason there weren’t enough senior engineers around to show them the way.
Same shit trying to implement with systems on the backend older than a lot of people using them today I’d imagine
And “the specific resource ID” is almost certainly for localization of the text
What cracked me up was all that copying blocks of code “because no one knows how anything works”.
That reeks of novices copying code without bothering to read it well, and since this work method is horrendous, no one stays enough to stablish a proper knowledge base.
Yeah this is classic legacy code.
Complicated code is when 700 projects are all entangled and when you add a 3D bar for measuring purposes (it was just a bar like 100 nanometers long so you could get a feel for size in 3D scans, in the 3D viewer), the up (not the down) mouse scroll stopped working for sliders in all the 2D GUIs…
That is crappy code and I was there when we got that bug (Avizo software).
Yea, this doesn’t sound horrible for what it is. Plenty of Linux systems are this bad.
…maybe it’s better that the Windows source code remain closed.
At the same time, I’d love to see the developers of the world glimpse at that eldritch cognitohazard and collectively go insane.
Maybe we’ve been misunderstanding what Closed Source really is this whole time?
It’s a codex holding back “eldritch cognitohazard” horrors that the technopriests of Microsoft have captured and tamed into an operating system. Releasing the source would release the beasts into our reality, much like the plot of John Carpenters In the Mouth of Madness.
Well, figured out one good reason for closed source, I guess. Let’s not solve this LeMarchand’s Box.
At least modern hardware runs the spaghetti code much better than Windows XP used to run.
i view it less as spaghetti and more as a rat king
Thanks Ballmer for QA.
I need more IRC screenshots in my life.
and people complain about wayland.
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.
Is this real? It’s funny af, even if it’s not real, but does anyone know if it is?
There is/was a new Windows 10 Control panel? I thought that was just the Settings app.
The settings app is the new control panel. There’s just also the legacy control panel that they’ve been trying to remove for years. It’s such a shit show that I’ve memorized the run string for the applets I have to use frequently, because it’s a fucking nightmare trying to remember where they moved this in which version of the os.
Man, the Device and Printers one is long as hell lol
shell:::{A8A91A66-3A7D-4424-8D24-04E180695C7A}Try
Control printersMuch easier
The thing with the Control panel (speaking as a former Windows user up until a year ago) was its consistency. Since the Aero era things have remained in more-or-less the same place. Sure, some things got added, some renamed and some deleted, but the basics I needed (mouse sensitivity, battery settings on the laptop, the Add/remove software page, search indexing, printers) has all stayed in more or less the same place.
Then 10 happened. And sure, Settings was great for a lot of stuff. But when Settings didn’t have the option (or I lost my nerves trying to find it), Control Panel was the way to go. I’d find what I needed pretty much instantly, since was always one of the same 20-odd things I need.
Even then, everything just seemed faster in Control panel. Was it more responsive? Were there less animations? Were more things crammed into one screen so less clicking and scrolling was involved? Is it just my imagination?
Honestly, I don’t know.
By the time I got used to the new Settings app, one of the big Windows 10 makeovers happened and jumbled up about 10% of Settings. Objectively not much, but just enough to irritate.
And now with 11, they not only made Settings unrecognizable, they also cranked the spyware up to, well, 11. And there’s no Control Panel to default on when in doubt (or fuming with rage).
All in all, while Control Panel wan’t what kept me on Windows, 11 losing it did ease the transition, since it meant having to learn a new way of doing things either way. Might as well make it a way that hopefully won’t change once a random design exec decides “this is ugly and it has to go”.
Honestly, KDE Plasma’s Settings are where it’s at. It’s right between the functional and informstional density of Control panel and the simplicity, visual appeal and saner structure of Settings. Shame it uses Qt, which from what I hear, is god-awful as far as UI toolchains go.
I have worked with Qt, it’s not that bad to be honest.
Keep them memorized. The old tools just work, even if MICROS~1 tries to hide them and replace them with useless crap apps.
deleted by creator
Well that was interesting to read
