You’re absolutely right on that count. If you switch fast enough, everything has a capacitance. That’s why with CMOS designs once you go above a few kHz you start worrying about fan out.
It’s also why, once the ceiling is reached, everything starts using modulation tricks previously used in RF. Ethernet started with 1GbE, USB with 3.0, DSL did it from the start, with PCIe even gamers have probably seen eye diagrams in riser tests, and coax is the very definition of pushing RF over a wire.
Yes, of course there is error correction. Also, while the SSD is on power, it’ll constantly go through all data and fix the areas that are starting to deteriorate.
But this does mean an SSD left without power will slowly lose data over months and years.
This also means that writing data is much slower and the SSD can handle far fewer writes. But the tradeoff is that TLC and QLC SSDs can handle 2× and 4× more data than MLC SSDs for the same price.
That’s why MLC SSDs are primarily used for professional use and TLC and QLC is primarily used for gamers.
Some TLC and QLC SSDs even allow you to choose how much of the SSD should be used as SLC/MLC space (4× less data, 4× faster writes, 4× more endurance) and which part should be used as TLC/QLC (4× more data, 4× slower changes, 4× less endurance).
SSDs aren’t just that simple. All of them have at least some SLC area, usually as cache, that’s in base 2. But the rest of the SSD can be SLC base 2, MLC base 4, TLC base 8 or even QLC base 16.
And overall it’s still base 2 because each SSDs pretend one block of base 4 is just two blocks of base 2, and accordingly they pretend a block of base 16 is just 8 blocks of base 2 storage.
ESS is a product built on top of a precisely tuned synapse with custom additions, but it’s still synapse underneath.
You need to be able to have multiple nodes in one LAN access ports on each others’ containers without exposing those to the world and without using additional firewalls in front of the nodes.
That’s why kubernetes ended up removing docker support and instead recommends podman or using containerd natively.
There’s no alternative for 0.0.0.0 and a firewall if you’re e.g. using kubernetes.
That assumes you’re on some VPS with a hardware firewall in front.
Often enough you’re on a dedicated server that’s directly exposed to the internet, with those iptables rules being the only thing standing between your services and the internet.
In some languages, it’s actually common to say US-American to clearly specify what is meant.
Even half an hour next to the PA without special ear plugs is enough to permanently harm your hearing.
What you’re describing used to be right under X11, but under Wayland the compositor handles all rendering itself. For Gnome that’s mutter, which is also maintained by the gnome project.
Seriously, stop being an asshole. Coil whine is a well-documented behaviour that creates a loud, high pitched noise.
As coil whine is at the very limit of what human hearing can accomplish, it doesn’t take much until you’re unable to hear it. So you’re likely too old or went to too many concerts to be able to hear it.
Good ears? the question is when, not where, and the answer is half a lifetime ago.
Don’t SteamVR tools work on linux as well? Not that it’d help in your situation, where you’re stuck with proprietary GPU drivers and proprietary VR tools.
Why so? AMD supports Wayland just fine, while having good enough performance. As a VR dev, AMD still including a USB C port on GPUs should actually be even more convenient for you.
Considering that reading source code can take a long time
You’ll get faster over time, until reading code is faster than reading documentation, as code will always represent what’s truly happening, while docs are frequently outdated.
In a language the user isn’t familiar with
If you’re not that familiar with the language, it’s likely you won’t be contributing to the project. Open source projects usually to have quite limited resources, so they tend to optimize docs and dev UX for people who are likely to contribute.
Also note that even a dual boot system is leaky. A kernel level anticheat has enough power to do firmware upgrades on peripherals or the UEFI, so a badly behaving kernel level anticheat could easily take over your entire system in a way that can never be gotten rid of.
So how do you juggle having to see dozens of windows at the same time then?
I’m a software dev as well.
But I often layer multiple windows in the same tile of the screen. e.g. I may have the IDE with the software I’m working on in one tile, the IDE with the library source code I’m working with in the second tile, and a live build of the app in the third tile. But I’ve also got documentation, as a website, in the same tile as the IDE with the lib’s source.
Now when I switch between the IDE with the lib’s source, and the browser with the lib’s documentation, I only want that tile to change. No problem, with KDEs taskbar and window switcher I can quickly do that.
But when using the applications menu on Gnome I get a disrupting UI across all screens that immediately rips me out of whatever I was doing.
That’s definitely wrong. You should follow danielle’s mastodon, she’s working on elementary all the time.