And what do the companies take away from this? “Cool, we just won’t leave you any other options.”
And what do the companies take away from this? “Cool, we just won’t leave you any other options.”
Which features do you mean? Not disagreeing with you, I’m just curious.
So basically Arch?
They’re free to change the licence of future versions.
Only if they are still the only contributor. Once you have more contributors, it gets far tougher to change the licence.
It would be just as (un)popular as the Steam Machines if it wasn’t for Proton, that’s my whole point.
They already tried that in the Steam Machines era. It clearly wasn’t working.
An int&
reference is just as much of a variable as int* const
would be (a const pointer to a non-const int). “Variable” might be a misnomer here, but it takes just as much memory as any other pointer.
never mind, I looked it up. It’s a “reference” instead of a pointer. Similar, but unlike a pointer it doesn’t create a distinct variable in memory of its own.
I’m almost sure it does create a distinct variable in memory. Internally it’s still a pointer, specifically a const pointer (not to be confused with a pointer to a const value; it’s the address that does not change). Think about it as a pointer that is only ever dereferenced and never used as a pointer. So yes, like the other commenter said, like an alias.
How many email accounts do you have? It might be a huge factor. I have about 7 accounts I need to check regularly and I cannot imagine doing it manually for each. I can see it working for one or maybe two though.
It… isn’t poop?
Even if it’s supported, it doesn’t mean it needs to be installed in every system. If the user wants to use a Musl-based system, the software working only on glibc needs to be patched. At least that’s how I understood these statements.
Presumably so it can work with either libc implementation.
Or frontdoor checkbox for that matter, given that it’s the literal device owner that takes the action tripping their “security” tripwire.