Earlier quoted context omitted.
[flagged]
> JShit doesn't belong anywhere Or, as I prefer to call it, Kiddiescript.
Windows GUI – Good, Bad and Pretty Ugly (2023)
191–200 of 203 posts
Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#192Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#193One underappreciated thing about Windows 8 is that even if the start menu was ugly and blocked the entire screen, you could press the windows key, immediately start typing, and then press enter to somewhat deterministically pick the top app. This made it feel quite fast. Now on more recent windows editions, I find that I often need to wait for the menu to visually appear before it will accept any keyboard input, and…
It works SO much better than the abomination that the Start Menu has become...
You can even type "%appname" to focus an already running app.
Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#194Earlier quoted context omitted.
Does the end user care that the system is made with React? What is the tangible negative impact? My start menu doesn’t have ads, it really isn’t hard to manage that sort of thing. OneDrive is fully uninstalled, Copilot is fully uninstalled, I find my system to be quite clean. And if you don’t like the start menu, there are ways to replace the start menu entirely with something else. Good luck replacing entire major e…
I care that it's made with React/React Native or other garbage web frameworks. By definition adding layers between native C/C++ Native Win32 will make it slower and use more RAM. Stop justifying laziness and mediocrity. Microsoft does this just so they can hire cheap javascript monkeys out of colleges. AKA people who shouldn't be writing code and the reason a chat application now uses 1GB of RAM and nobody seems to c…
https://news.ycombinator.com/item?id=44124688
It is supposedly still mostly Windows native XAML. Allegedly, even the components that use react are using react native for windows and are therefore not rendering any sort of resource-wasting web view.
I wrote my own react native phone app and it’s only a 30MB download. Your random comparison to a bulky chat app with an extensive feature list (the most popular culprits like Slack and Discord are not written in React Native, by the way) consuming a GB of RAM is irrelevant. Have you measured the start menu consuming 1GB of RAM? Unless you have, your argument is a whataboutism.
If you think it’s bad that Microsoft is using stuff that makes it easy for them to develop windows you should explain to me how it would be better for them to have extreme difficulty in making improvements like how the old control panel basically couldn’t be updated with any reasonable development cadence for decades while macOS ran circles around Windows for their clean settings experience, versus the new settings pane that Microsoft can actually iterate on and improve.
You can criticize the new settings panel for maybe not having 100% of what you want in it but you can’t criticize being a scary nightmare for novice users like the old version.
It is in the users’ benefit if Microsoft can actually hire people who are real humans and not just myths.
Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#195Earlier quoted context omitted.
“A noticeable sub-second delay” lol. I guess you never ran Windows 98 on a pentium 2 like I did. If I had a dime for every sub-second delay I experienced on that machine… Settings > Accessibility > Animation Effects > Off 5-10 seconds to start a screenshot, yeah man now you’re just lying. You sure you didn’t leave the delay timer on? Are we going to gloss over the fact that the screenshot interface in old windows ver…
> I guess you never ran Windows 98 on a pentium 2 like I did. If you have to compare to a 20+ year old processor to look good, your system has problems. But since we are comparing old computers, Finder opens quicker on a 30 year old Macintosh 512k than Explorer opens in Windows 11. > 5-10 seconds to start a screenshot, yeah man now you’re just lying. Nope. I actually just updated that number up to 20 seconds after te…
So even this base assumption that a slow heavy bloated experience is on offer is just hearsay. The only section that uses React is the allegedly recommended section, the one that can be disabled entirely with a single settings toggle.
Anyway, again, the 5-10 second screenshot thing, I’ve been testing it live and could never get it to be slower than 2 seconds between invoking the shortcut key to file on the disk. Keeping in mind that this includes me physically reacting as quickly as possible to click after the shortcut keys to initiate the capture. It’s about one second between clicking capture and observing the file appear in file explorer. My CPU is 5 years old, my RAM is DDR4, and I use an off brand nvme SSD, for your reference.
I will also add to this that the main competitor to Windows, macOS, adds an intentional delay to their screen capture where the screenshots aren’t added to disk until after the little preview disappears or is manually dismissed. In Windows the preview notification and file being written to disk happen simultaneously, and the system automatically copies the image to clipboard which Apple doesn’t do, saving further time.
Your network share issue could be something misconfigured at your work, I have no way to verify whether that’s something your IT department messed up. My personal Windows and Linux systems are both connected to my SMB shares at all times through their graphical file managers and I don’t notice any difference in performance.
Last rebuttal: your finder experience in Macintosh classic (System 3.0 when the 512k debuted) is fast because there’s no multitasking, when you are at the desktop of a Macintosh the only application open is Finder and it’s already in RAM. Open any other application and then close it. You’ll notice a relatively long delay (10 seconds in my testing, although I don’t have real hardware) after closing the application before the desktop and finder are responsive again. You can try this on your preferred Macintosh emulator online.
Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#196I remember hacking the "Start" button in 95 through 7 to say "Whee!" instead of "Start". Childish and silly, but I liked it. I miss being able to make little hacks like that.
Sadly though, this kind of hacks doesn't satisfy me the same way it did 30 years ago, when I had all the time in the world to tinker.
It's the same story with things you can customize, today I rarely bother spending more than a few seconds on clicking around to choose the next best thing.
Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#197Earlier quoted context omitted.
It is, strictly going by looks, one of Microsoft's ugliest UIs. I will never understand how people tolerate it, let alone defend it publicly. Shameful, absolutely and thoroughly shameful!
It was the style at the time. There are a lot of programs from that era with stupid, oversized nothing standard ui's, windows xp was a study in restraint compared to many applications. I think computers had just gotten powerful enough to have large bitmaps in the ui and the designers got a little crazy with their newfound power, as they tend to do. Our "modern" superflat look is probably the remnants of a reflexive r…
cough Liquid Glass cough
Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#198Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#199Earlier quoted context omitted.
You're talking about Windows 3. Windows 2 predates Presentation Manager.
It doesn't seem to be the case: https://en.wikipedia.org/wiki/Presentation_Manager#History
Re: Windows GUI – Good, Bad and Pretty Ugly (2023)
#200Earlier quoted context omitted.
Preinstalled OS doesn't mean free OS. You already paid for it when you bought the computer. You shouldn't see ads. Ever.
The software on the computer would cost more if it was ad-free and consumers have made the clear choice that they prefer not to pay for OS updates. We know this because the updates used to cost money. Apple was charging over $100 just for a point release, and they charged hundreds for updates to bundled software like iLife and iWork. Everyone would love it if the NFL had zero ads but most NFL fans wouldn’t pay $XXX/m…