Firefox doesn't actually load all tabs on startup (only the selected one) and it allows you to unload tabs, so you can be fairly efficient about it.
That said, it can easily use a couple dozen GiB after an intense research session or a few weeks of regular usage but that's manageable with even just 32G and, as I said, you can always unload tabs (or restart; effectively unloading all tabs) to reduce usage at any point.
There's currently a bug with AMDGPU wherein aggressive power management causes constant micro-stuttering and that also appears to break VRR for me.
Set power management to 3D_FULL_SCREEN or VR on the GPU.
Noch kleiner!? :o
Gewicht und Zerbrechlichkeit sind auch Faktoren. Ich würde mir niemals eine Glasflasche in den Rucksack tun oder auf dem Rad mitnehmen.
The 710M will give you trouble. Like, pain in the ass. See if you can disable it in BIOS; you won't be using it for "serious" gaming anyways.
Distro doesn't much matter. It's fully up to personal preferences. Try them all (using Ventoy like @b9chomps@beehaw.org recommended. Some distros make the installation and management of the Nvidia driver easier than others but you should ideally be disabling that GPU entirely.
I personally recommend Fedora to newcomers but as I said, that's personal preference.
Note that if some piece of hardware (i.e. wifi) doesn't work in one of them, it most likely won't work in any distro.
It has the option of UEFI but the GeForce (I think) doesn’t support it.
This doesn't make much sense to me. The GPU plays no role in that part of the boot process.
I’m planning to upgrade the RAM to 8 gigs and upgrade to an SSD
Get an SSD now. Even a dirt cheap one. 4GB is tenable with careful management but a hard drive will make everything excruciatingly slow, even on Linux.
You don't need to think about your DE choice w.r.t. performance on their class of hardware. It can run the heaviest DEs just fine.
Umm, all of them? :$
Can I make Firefox count them somehow?
Edit: Shift click to select them and then right click. 857...
That's because GNU/Linux uses open, generic interfaces to communicate with (often fairly generic) hardware.
Android/Linux usually uses specialised closed black-box interfaces to communicate with hardware and those usually only work on one specific device or at best a small family of devices.
This model is dictated by the vendors of the hardware.
android is FOSS the same as Darwin (the system under iOS) is.
Not at all. The Darwin kernel (XNU) is semi-FOSS (as in: Apple throws source code over the fence every year or two) but nearly none of the rest is.
Not only is this practice not even close to Linux' fully open development model, XNU is quite a minimal kernel; it's more of a microkernel design. You need the other parts in order to have a usable system.
The Android userspace is fully FOSS. Android Framework, system libraries, system services and even the UI are fully FOSS with a fairly open development model.
I patch my Android framework to disallow apps from ever dictating how my screen should be rotated for example.
The Evil Corp. has been pulling more functionality into the proprietary GMS crap lately but it's not very many features and alternatives exist for FOSS apps (i.e. Firebase push notifications: UnifiedPush).
OEMs take this fully open code and might make changes; mostly of cosmetic nature. Those usually aren't published.
Many Vendors ship the regular Android userspace with little to no modification however.
Android FOSS but not Libre. Don't confuse the two.
Only the kernel of Android is Libre. (XNU is not Libre btw.)
the same is true with iOS and Darwin.
In iOS, almost the entire userspace is proprietary.
In Android most userspace funtionality is FOSS too.
This only concerns the kernel which is rather unimportant when it comes to Android updates. You can keep using an ancient kernel for an insanely long time but upgrade the Android userspace. The vast majority of LineageOS devices use the original kernel they released with (+bug fixes, usually).
Only when Android has a hard requirement on a new kernel feature do you need to actually upgrade it. This is usually end of the line for a device in custom ROMs because it is infeasible to do in most cases.
Take the Oneplus One (bacon) for example. It was released oven 9 years ago with kernel 3.4 and only lost LineageOS support with Android 12 because that requires eBPF for firewalling apps which is a relatively recent addition to the kernel.
The shims for the HAL you mentioned are in userspace. The original BLOBs they shim use the original OEM kernel interfaces in order to do their magic. It's just that Android might require newer/different interfaces from the HAL BLOBs; that's what the shims are for.
I was researching a wrist watch for myself the past few days but I want/need an (apparently) very niche and rare complication: A timer. You'd think this should be a fairly basic feature to put into a technologically advanced watch but apparently not.
See https://lemmy.ml/post/3754708
I've found that bookmarks don't really work for me because they're A. clunky to manage and B. don't retain context. I often branch off from one tab to multiple others or open a new tab next to one on the sub-topic I'm researching. It's hard to describe but it's a workflow I've gotten rather used to.
I'm aware of tree-style-tabs but haven't found the motivation to set it up yet and am a little unsure whether I want to let an add-on handle functionality so core to the browser.