This might come in handy as a VM.
De-Bloated Windows 11 Build Runs on 2GB of RAM
181–190 of 415 posts
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#182I had a similar experience with GrapheneOS on my pixel 6 pro. It got multi-day battery life out of the box, which is far in excess of what Google advertises for that hardware. Once I installed google play services (which have zero end-user benefit, other than enabling compatibility with apps that have bundled google spyware), battery life more than halved, bringing it in line with what Google claims. I suspect anti-t…
Maybe you are Ok with paying for every app or making do with open sources ones that do not benefit from ad revenue stream. Plus, you don't need maps, pay or cast support. But many other people like this features and if they don't, isn't it great that there are working AOSP builds for Pixel 6 Pro so that they can roll their own ROMs on top of that? No need to hack like for Windows 11.
maps work perfectly fine on my no gapps phone, so does Whatsapp or signal
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#183Let’s pause for a bit and dwell on the absurd amount of RAM it takes to run it even after this exercise. Anyone here remember when QNX shipped a demo in 2000 with a kernel, GUI, web browser and an email client on a single 3.5” floppy? The memory footprint was also a few megabytes. I’m not saying we should be staying within some miserly arbitrary constraints, but my goodness something that draws UI and manages process…
> Let’s pause for a bit and dwell on the absurd amount of RAM it takes to run it even after this exercise. I agree and I find the apologists to be completely wrong. I run a modern system: 38" screen, 2 Gbit/s fiber to the home. I'm not "stuck in the past" with a 17" screen or something. The thing flies. It's screaming fast as it should be. But I run a lean Debian Linux system, with a minimal window manager. It's defi…
The low-end requirements for Debian GNU/Linux (assuming a graphical install and an up-to-date version) are not that low. They're higher than the low-end for Windows XP when it first came out, and probably close to the official requirements for "Vista-capable" machines. So yes, it's a very efficient system by modern standards but it does come with some very real overhead nevertheless.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#184Earlier quoted context omitted.
Are you seriously suggesting that accessibility support in modern OSes is less complex than in Windows 95?
Yes. At least in Windows 10 is a disaster. Without high contrast, which looks terrible, it draws gray colors on light background making it difficult to read.
Microsoft should copy the Zukitre theme from GTK2/3 as the inspiration. It's flat yet it has some contrast.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#185Earlier quoted context omitted.
> HDR, fluid animations, monstrous resolutions, 3D everything May I remind of https://www.enlightenment.org/ 20 years ago, there were "live cds" that could do most of what you mention, at maybe 512 MB ram.
I ran e16 and then e17 as my main desktop back in the day for a good while. I'm sorry but what we had back then was nowhere even near what I'm talking about. It definitely was pretty for the day, though.
Then, OSX. A G4 with 512MB of RAM could perfectly do that at 1280x800.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#186A regular Windows 11 will also run on 2 GB of RAM. The official requirement is 4 GB because it'll stutter a lot otherwise, but there is no software block against it. This article claims the de-bloated Windows 11 will run "great" on 2 GB so I guess there's that... But I have to wonder according to which definition of "great" with a lack of benchmarks compared to the official requirements...
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#187Earlier quoted context omitted.
> Accessibility includes interaction design, zoom ability, audio commands, action link ups, alternate rendering modes, alternate motion modes, hooks for assistive devices to interact with the system. It goes far deeper into the system than just labels for a screen reader. I wonder where the current status quo lies in regards to both desktop computing and web applications/sites. Which OSes and which GUI frameworks for…
> Which OSes and which GUI frameworks for those are the best or worst, how do they compare? Hands down macOS/iOS are the leaders here with Cocoa/SwiftUI/UIKit etc (ultimately basically the same). The OS also has many hooks to allow third party frameworks to tie in to the accessibility. Windows is second in my opinion. Microsoft does some good work here but it’s not as extensive in terms of integrations and pervasiven…
I switched from windows to macOS, which I’ve been using as my daily driver for the last year or so. Using the touchpad (or maybe the Magic Mouse) is basically a requirement to use “vanilla” macOS. Yes, you can install additional programs to help with window management, etc., but in my experience macOS is absolutely horrible when it comes to accessibility, from this standpoint. Maybe it’s better for colors, TTS, etc.?
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#188Sure, and you could strip an average car down to its shell, steering wheel, throttle/brake controls, a seat, and probably get away with a 75 hp engine. Neat!
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#189Earlier quoted context omitted.
Accessibility is much more than just labels for a screen reader. Please stop trivializing anything that you don’t use directly, it’s a common thread between all your comments, and it’s a disservice to both the points you’re trying to make and the people who actually use those things . Accessibility includes interaction design, zoom ability, audio commands, action link ups, alternate rendering modes, alternate motion…
> Accessibility includes interaction design, zoom ability, audio commands, action link ups, alternate rendering modes, alternate motion modes, hooks for assistive devices to interact with the system. It goes far deeper into the system than just labels for a screen reader. I wonder where the current status quo lies in regards to both desktop computing and web applications/sites. Which OSes and which GUI frameworks for…
> it seemed straight up broken because it couldn't reach my site: https://wave.webaim.org/
It worked for me, it found lots of color contrast problems (white-on-light purple has low contrast). https://wave.webaim.org/report#/https://kronis.dev/
WAVE is also available as a browser extension.
Accessibility checkers can be helpful, particularly for catching basic errors before they ship. The large majority of accessibility problems a site can have cannot be identified by software, humans need to find them.
Current Bootstrap is not bad if you read and follow all of their advice. I'm not claiming there are no problems lurking amongst their offerings.
If you search for "name-of-thing accessibility" and don't find extensive details about accessibility in the thing's own documentation, it probably does a poor job. A framework can't prevent developers from making mistakes.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#190Earlier quoted context omitted.
> Which OSes and which GUI frameworks for those are the best or worst, how do they compare? Hands down macOS/iOS are the leaders here with Cocoa/SwiftUI/UIKit etc (ultimately basically the same). The OS also has many hooks to allow third party frameworks to tie in to the accessibility. Windows is second in my opinion. Microsoft does some good work here but it’s not as extensive in terms of integrations and pervasiven…
I switched from windows to macOS, which I’ve been using as my daily driver for the last year or so. Using the touchpad (or maybe the Magic Mouse) is basically a requirement to use “vanilla” macOS. Yes, you can install additional programs to help with window management, etc., but in my experience macOS is absolutely horrible when it comes to accessibility, from this standpoint. Maybe it’s better for colors, TTS, etc.?
Did you enable Full Keyboard Access and learn how to use it?