Even if it was open source (it isn’t, because no model is really open source ultimately) and even if it let you review what it says it’s gonna do, AI is know for pulling all kinds of shit and lie about it.
Would you really trust your system to something that can do this? I wouldn’t…
I look forward to not installing it.
No: the waiting time is more like 9 months and fully-loaded, you’re looking at north of €1,800 :)
The point of MNT machines isn’t value for money, but openness and sovereignty over what you own. They’re not for everybody, but my kids are out of the house, the house is paid for and so I have the means to put my money where my convictions are.
But no matter: the point was that Linux ARM laptops really are nothing new.
“Pave the way for ARM64 laptops?”
I have an ARM64 laptop as my daily driver right here on my desk and it’s happily running Debian 13. The road is quite paved already.
It’s different this time around.
The previous attempts were about freeing themselves from an abusive unprincipled data-hungry big data monopoly,
This attempt is about freeing themselves from an abusive unprincipled data-hungry big data monopoly operating in a fascist country and in cahoots with the regime.
I reckon it’s serious this time.
poettering is an absolute good guy here
Agreed. But he’s also an abrasive know-it-all. A modicum of social skills and respect goes a long way towards making others accept your pet projects.
pulesaudio protocol is used within pipewire and it works just fine.
I wasn’t talking about the protocol, I was talking about the implementation: PulseAudio is a crashy, unstable POS. I can’t count the number of hours this turd made me waste, until PipeWire came along.
I totally agree. I used to hate systemd for breaking the traditional Unix philosophy, but the reality is that a tight init and service-tracking integration tool really was required. I work with and appreciate systemd every day now. It certainly didn’t make things simplier and easier to debug, but it goes a long way towards making a Linux system predictable and consistent.
Poettering can go fuck himself though - and for PulseAudio too. I suspect half of the hate systemd attracted over the years was really because of this idiot.
Youtuber Johnny-come-lately gets way too much attention.
In complex cases where speed is less important than maintainability, I tend to agree.
In this case, a simple comment would suffice. And in fact nothing at all would be okay for any half-competent Python coder, as testing if lists are empty with if not is super-standard.
They’re quite simple. Just convert the values to binary and apply the applicable truth tables. Just remember operator precedence when you use them, and in doubt, don’t trust your luck and apply parentheses generously 🙂
But what is an example of where I can use it?
Aside from operations on bitfields, a bitwise operator can be useful in several “non bits” cases. For instance:
value & 1 evaluates to 1 if value is odd (and will evaluate to True in an if statement)
value >> 1 divides value by 2 (integer division)
But usually bitwise operators are for when you want to manipulate bits in values. For instance:
value | 5 returns value with bits 1 and 3 set to True
value & 0xffff returns the 16 least-significant bits in value (usually you do this to make sure it will fit in 2 bytes in memory for example)
value & (0xffff ^ 5) returns the lower 16 bits of value with bits 1 and 3 set to False
Etc.
Much to unpack here…
coin == 25 | 10 | 5
…will evaluate as True if coin is equal to the bitwise OR of 25, 10 and 5 - i.e. 31. In other word, it’s equivalent to coin == 31. That’s because the bitwise OR has precedence over the == operator. See operator precedence in Python.
If I replace the ‘|’ with ‘or’ the code runs just fine.
It probably doesn’t. If you replace | with or, you have the statement coin == 25 or 10 or 5 which is always True in the if statement because it’s evaluated as (coin == 25) or (not 0) or (not 0) in an if statement.
coin == 25 | coin == 10 | coin == 5
…will evaluate as coin == (25 | coin) == (10 | coin) == 5. Again, operator precedence.
What you want to do is this:
if coin in [25, 10, 5]:
or
if coin in (25, 10, 5):
or simply
if coin == 25 or coin == 10 or coin == 5:
Don’t create problems and confusion for the next guy who reads your code for nothing. Simple and readable are your friends 🙂
That’s the most accurate article on the subject I’ve read in years.
With shell scripts, I’m not sure.
With Python scripts, you want argcomplete.
I’m glad one more person discovered Linux is good in 2025.
I’m a random person too and I discovered Linux in 1993. Where’s my 15 minutes of fame?
Oh right, I’m not a Youtuber…
Have remembered to set the reboot in future command since
That’s not a bad idea actually. I’ll have to reuse that one. Thanks!
This is a server I was setting up. It’s not doing anything useful at all at the moment, hence the lax work practice. The only reason I drove back to work is because it’s needed tomorrow and I wanted to finish setting it up tonite.
In my defense, I just installed the machine. I was configuring it from home after hours.
This is suspiciously specific 🙂