[
is a binary (sometimes a symlink) in /usr/bin
. It’s /usr/bin/[
🤓
[
is a binary (sometimes a symlink) in /usr/bin
. It’s /usr/bin/[
🤓
Sadly that’s true. I’m in that range and most of my friends use the same password for almost everything. Also nobody does backups.
Then at least make it an option. Just because someone’s grandma doesn’t want to use TOTP or any other reasonable 2FA doesn’t mean nobody else does.
That sounds more like breaking up.
As long as we put that “exclusive content” crap aside, every one of them can potentially offer every song if they agree with the artist. That’s where the video streaming services are different. Disney+ and Netflix had many overlapping shows until the shittification started.
Yes and no. It’s both electromagnetic waves but the frequencies are very very far apart. So far, the techniques we use to emit and receive them is fundamentally different. Their propagation and transmission characteristics are also very different. Also, the data transmission rate (in theory) only depends on the bandwidth of the transmission channel, not the absolute frequency. But there’s more “room” for large bands at higher frequencies, of course.
It’s the amount of legacy it’s carrying on that drives me crazy. Many of the implicit default implementations are confusing. That’s where all these “rule of 3”, “rule of 7”, “rule of whatever” come from. The way arguments are passed into functions is another issue. From the call-side you (sometimes) cannot tell if you’ll end up with a moved value or a dangling reference. The compiler will not stop you from using it. Even if the compiler has something to tell you, it’ll do it on the most cryptic way possible. I’m grateful we have C++, it paid lots of my bills. But it’s also a pain in the ass.