Live data from Hacker News

Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

howtogeek.com

381–390 of 567 posts

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#381
post #4

Tell me again how Microsoft has changed and it isn’t the same company anymore, and how EEE is ancient history.

Literally true of Edge's relationship with Chrome. I believe we're now on the "extinguish" phase.

I think it's more likely Edge gets extinguished. It's like a blip on Chromium forks radar.

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#383

Earlier quoted context omitted.

That gives me four years for the tools that lock me to Windows to decide to port to literally any other OS.

I'm not old and I have lived to see this sentiment come and go at least twice before. We're still on Windows.

i'm not. i've moved to Ubuntu linux

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#384
post #64

Linux Desktop feeling extra good today, my sound often doesn't work but I don't have to deal with Microsoft nonsense.

Pipewire has made all of my audio issues on Linux go away, at this point. Maybe it's my hardware (a high-end Dell Latitude that is Ubuntu certified) but it just f*cking works! I'm on Arch, so I find I tend to have fewer issues than with Ubuntu (due to the latter always being on some ancient version). Seriously though when I switched from Pulse to Pipewire... I rebooted and I've never had any issues since! Now, my big…

I actually contribute to PipeWire development in some small aspect (reporting bugs, debugging issues), and PipeWire is far from trouble-free. The recent 0.3.41 contained a bad commit which causes PulseAudio apps (RetroArch, QEMU, Orca) to infinitely buffer audio in xrun or something (fixed in git). And PipeWire has some issues switching profiles when you plug and unplug devices, and sometimes picks the wrong speaker/headphone port(?) when rebooting and then enabling a device, and the latency algorithm has issues as well (under default settings, it takes up to 0.6 seconds to hear certain libcanberra notification sounds). And it reuses IDs exposed to PulseAudio apps, which causes race conditions (eg. crashes, incorrect stream-to-app mappings in plasmashell) in PulseAudio apps. "Write" race conditions (eg. changing app volume) are unresolvable due to the Pulse protocol, though apps can be fixed to avoid "read" race conditions by ignoring stale data from IDs which have been deleted and recreated.

I still use PipeWire because routing app audio is cool (and not possible AFAIK on PulseAudio), and I can usually avoid the bugs well enough in practice. But it's not "just f*cking works" in many cases.

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#385

Earlier quoted context omitted.

> Settings app is now uses a more traditional left pane navigation instead of a list of large boxes for touch Serious question: why didn't they just do this in the first place? It can't be hard to check if the user has a touch input and dynamically resize buttons / list items, then size them back down when the user is done. They do exactly this for "Tablet mode"[0] in Windows 10. This, and the pitch black dark mode t…

I can see minimizing changes to the interface across devices as being good but as to why they didn't do this compromise of larger navigation entries instead of full touch first I'm not sure but it would have saved so much grief. It might have had to do with Windows Phone still being a thing at the time. Regarding dark theme the dark app background is 12.5% gray and the lighter offset backgrounds are 17.5% gray. If it…

> Regarding dark theme the dark app background is 12.5% gray and the lighter offset backgrounds are 17.5% gray. If it appears pitch black it's not because the theme is made for OLEDs rather your displays are miscalibrated and completely crushing blacks.

Hmm, are you sure about this? From a quick search, I'm able to find plenty of people complaining about the dark background being pitch black[0] (there's also a Feedback Hub item linked in there, not able to open it as I'm on Linux). I might be wrong, but I am fairly sure my display is not mis-calibrated, as I actually spent a lot of time calibrating it when it got here (have only had it a handful of months). The only downside of the monitor is that blacks really smear when you move them around, whereas dark greys are substantially better.

That's one of the reasons I really dislike the pitch black mode, anyway. It also just looks horrible on anything that isn't AMOLED, IMO.

> If you enable transparency effects the color of your background will blend with these and raise/lower them accordingly.

That's only for surfaces with blur enabled though, like the sidebar in Settings or the taskbar. Non-blurred surfaces are pitch black.

[0]: https://old.reddit.com/r/Windows10/comments/6nzs34/any_way_t...

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#387

Earlier quoted context omitted.

I have alt-backtick mapped to my favorite terminal app in Linux, and control-backtick mapped to a new browser window. I'd be buggered if I ever switched to Mac!

These keybinds are relatively common on Linux too, they're Gnome defaults.

They're also customisable.

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#388

Windows 11 was an absolute downgrade to my Windows 10 experience. To the point that I went back to windows 10 in less than a day of Windows 11. 1. I can't ungroup the taskbar windows. So now I have to hoover the taskbar to see multiple instances of the same software; 2. Who the hell thought it was a great idea to couple all the commands like WiFi, power energy, etc under the same menu? On Windows 11 I needed to click…

It’s Windows Millennium Edition 2. Break things that worked fine, add things that add no value, recategorize everything to confound expert and novice users.

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#389

Earlier quoted context omitted.

It could be worse. You could be on MacOS where Cmd-Tab switches between apps not windows. I currently have 13 browser windows open (each with 3 to 15 tabs) and another 9 windows of other things (terminal, vscode, etc....) and IMO The Cmd-Tab vs Ctrl-Tab vs Ctrl-Up vs Ctrl-Down suck compared to Windows. I really want to easily switch to the previous window, not the previous app. Command + backtick doesn't work either.…

I have to use a Mac for work, and I've been using WindowSwitcher as a cmd+tab replacement. I liked it enough I paid for it at the end of the free trial. It's excellent, except I wish the mouse interacted it on click instead of mousover. Still better than the default. (another tool along those lines I use is uBar, which is a Windows-style taskbar for macOS)

Contexts is pretty good too (another cmd tab replacement).

Re: Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

#390

Earlier quoted context omitted.

You don’t uninstall snap if you use Ubuntu?

Uninstalling software isn't the same as installing new, different software that didn't even come in your distribution's repositories. And, besides, a lot of people don't run Ubuntu, perhaps to get away from snap, perhaps to get away from systemd, or perhaps just because they can..

Do people still want to "get away from systemd". I thought most people had realized that systemd was a good thing by now :p.

There's not a single popular Linux distro these days that isn't systemd by default. Even """hardcore""" distros.

Post reply on HN