I recommend giving dnf the -C flag to most operations, particularly those that don't involve downloading packages. The default behavior is often similar to pacman's -y flag and so the metadata sync ends up slowing everything down by orders of magnitude.
zarenki
joined 9 months ago
I've long known about it. I don't seriously use it, but I would if only my Wi-Fi router was fully supported. It's an Asus one (that I got for free from T-Mobile a decade ago) so I installed Asuswrt-Merlin on it instead.
Following the recommendation of homelab communities, I got into OpnSense (a BSD-based firewall system for x86 hardware only) last year, still keeping my Wi-Fi router as a dedicated AP. In hindsight I somewhat regret that choice and probably would've been better off buying a new OpenWRT-compatible router and using it to handle firewall/routing/AP all in one device instead of wasting the power draw of another separate N100 system. I like having wireguard and vnstat in my router now, which Merlin didn't offer, but I know OpenWRT has those too and I don't have any other needs that warrant a higher-power router.
As someone who used to use Arch a decade ago: I still use pacman for devkitpro at least, and I do miss how fast its parallel downloads get, but the tool I use to manage packages is far from the most important difference between distros to me, even if you assume not needing AUR.
On Switch, no game cards support writing of save data or anything else. It's a departure from 3DS and all previous Nintendo cart formats for as long as games have supported saving at all.
That change is probably done to help tie saves to user accounts, enable cloud saves even when the card is not inserted, accommodate variable-size user data features like level creation, and mitigate the risk of game save based exploits like Twilight Hack spreading from user to user.
Unfortunately that (plus inability to put saves on SD card) means that backing up your own save data requires either being able to run homebrew on the system that has the save or having another Switch that can and relying on Nintendo servers to perform the transfer. Either way, having a Switch that runs homebrew means you don't need this dumper.
I've been using it since it felt usable enough in GNOME to me. Around 2015-ish, give or take a year. GNOME leading on Wayland support is a big part of why I switched to it from Xfce back then. Nowadays KDE and others have plenty good Wayland support too (better in some ways like allowing server-side decorations and global shortcuts) but I just haven't felt like trying to properly experiment to see what I like.
I've always avoided Nvidia on my desktops. Stuck with either radeon or intel and never had any exceptionally big issues with them on Wayland. Though other things like hardware accelerated video decoding have had a history of being spotty on some drivers/GPUs.
I've avoided RGB-lit stuff for everything else, except for my wireless headset. A Logitech G733. In every other respect I love it, but it has bright lights on the front that drain the battery and reflect in my glasses. They default to constantly changing random colors until host software sends a command to control the light. Thankfully there exist tools to control it on Linux (HeadsetControl) but adjustments reset on every power cycle.
The mouse in OP (M510, I've had a few of them myself) doesn't have those problems. There does exist specialized software to manage device pairing for the included "unifying receiver" but it comes by default pre-paired so the software is only particularly helpful for the niche use case of having other wireless logitech devices and wanting to save USB ports by making them all share one receiver.
The readme file, gitmodules file, and other links within that repo all still reference the now-dead gitlab links. The builds don't seem to be present at all.
That will all probably be fixed soon enough but right now that mirror which seems to have just been pushed as-is isn't entirely usable.
The first I tried was Ubuntu 7.04 but I didn't stick with it and went back to XP. Until I ended up with a hardware setup that wouldn't work on Windows XP (widescreen monitor + Intel graphics driver with no widescreen mode options) but worked perfectly on Ubuntu 9.10. I never truly went back to Windows since.
Tried a few other distros in 2011 then switched to Arch for a couple years, Xubuntu for a couple years, Ubuntu GNOME for 7-8 years, and finally switched to Fedora last year.
The act of tipping itself is a cultural thing it needs to be addressed culturally. If you can’t tip someone for something, complications in the law arise that may disallow giving money to people in general. For example how do you distinguish between tipping a server for a meal and giving the server a dollar as a gift?
If you are a customer at a food or retail business and opt to give one worker there a cash gift while they are on the clock, how can that not be a tip? Current US laws like FLSA already have a very clear definition of tipped wages which would include anything matching that description.
Even if you want to allow that sort of cash "gift", eliminating tips for credit card payments should be enough to shift the norms and expectations. Namely, prohibit payment terminals from prompting for a tip as part of the same credit card transaction and prohibit the tip lines on receipts. Majority of Americans don't pay with cash. If a business says they accept credit card, customers clearly aren't expected to give a decent tip and by extension the advertised meal prices and wage amounts should reflect what the customer is expected to pay and what the staff should expect to earn independent of customer whims.
You joke, but it really exists: the company that acquired uTorrent 17 years ago now sells an ad-free version of their current torrent client as "BitTorrent Pro" for USD$20/year, or alternatively as part of a VPN service bundle for $70/year.
Needless to say, stick with FOSS clients like qBittorrent/Deluge/etc instead.
Nonfree media codecs like HEVC/h265 are affected by US software patents. Distributing them from US servers without paying license fees to MPEG LA can put the host at risk of lawsuit. VLC, deb-multimedia (Debian), and RPM Fusion (Fedora) all avoid that by hosting in France, but even with those sources enabled patent issues can break things like hardware acceleration. Free codecs like AV1/VP9/Opus avoid all these problems.
Microsoft is US-based and can't avoid those per-install fees. They could cut the profit from every single Windows license but apparently chose not to.
Not every work environment is the same.
When I first started with my current employer I was given a system with RHEL preinstalled and I replaced it with Fedora on my first day. I was told to use LUKS and given a normal OpenVPN profile but otherwise they don't control or monitor anything about my workstation. No matter how many years or decades I stay at this company, it's extremely unlikely I'll ever touch an OS that isn't Linux-based during work time.
Every previous job I've been at also had me use Linux for my primary workstation, because my field of work more or less requires it, but some have needed me to access a separate Windows system/server/VM on rare occasions.