Not to be confused with “Panzerschokolade” (tank chocolate), distributed in the 1940s, which was chocolate with meth.
she/her
Not to be confused with “Panzerschokolade” (tank chocolate), distributed in the 1940s, which was chocolate with meth.
You are twisting words beyond recognition here, and for what? The guy was an IDF soldier. How is that not “working along IDF soldiers”? It’s not saying “working for the IDF”, which seems to be your criterion.
Next you’re going to complain that it says soldiers, plural, I assume? That would at least be a valid criticism in your quest to… archive what, exactly?
Many students, specifically PhD students, also work for the university. I didn’t say “work under”, I said “work with”, as in, work at the same faculty, i.e. they are coworkers.
She called him out publicly for volunteering for a foreign military currently enacting a genocide. It’s a big stretch to call that “outing” or “public harassment”.
And nowhere does the headline claim something different.
I genuinely don’t understand what point you are trying to make.
He volunteered for the IDF. That makes him an IDF soldier.
He’s a Professor at her medical faculty. That means she has to work with him to get her degree.
She refused to do that.
The university suspended her.
If NASA was in the habit of exploding babies, you’d’ve been well within your right to not want to have any contact with your HS teacher either.
Only tangentially related, since I don’t think NBD uses FUSE, but may I present Harder Drive
Samba (and NFS) require you to set shares up on the server’s side. With sshfs, you don’t need anything but a ssh login to your server. Black magic
Where do you get that idea from? Tht G stands for GNU
They have the same momentum (the marble will kill you)
Could be, but this type of ASCII art usually is hand-made. Diagonal lines are hard and look off, easily
It’s fair to want to learn (and it’s certainly a good skill to have), but the question is what you’d rather see in a large, production environment. Guard rails are usually there for a reason. As for the control: you actually can program memory-unsafe (and in kernel development you often have to!) in Rust. The difference is that in Rust it’s explicitly marked by an unsafe block:
unsafe { ... }
That way you get the same, fine-grained control over low-level processes, but someone else reading your code can at a glace spot where potential memory bugs may be.
In the end, languages are a tool. Especially for personal projects, everyone should just go with what’s fun to them. I personally think it makes sense, logistically, to slowly transition legacy C-based projects to Rust, because it makes onboarding new developers easier, while keeping the same memory safety that requires years of experience otherwise, basically for free. But there’s really no rush to rewrite anything that’s working well in Rust