C++ programmers always let their friends access their private members, so …
No relation to the sports channel.
C++ programmers always let their friends access their private members, so …
If you’re looking for commercial games on Linux, Steam has pretty much solved this with the “Steam Play” compatibility feature, which uses a customized version of WINE to run Windows games. For example, Baldur’s Gate 3 runs perfectly. It should work anywhere Steam does.
Ubuntu on Desktop I can understand.
Not anymore. A whole extra, unneeded, proprietary, locked-in package system. Ads in the default install.
There’s Mint, Pop!, and plenty of other options that actually respect the user.
Remember SOAP? Remember XML-RPC? Remember CORBA?
Those were not very good.
If you can’t tar to a pipe into ssh to a remote host and untar into an arbitrary location there, are you really using Unix?
I’m reminded of the character names that show up in MIT CS textbooks, like Alyssa P. Hacker (“a Lisp hacker”) and Eva Lu Ator.
I hear he lets all his friends access his private members.
1993 or so, before kernel 1.0. Slackware on floppies, then Debian, then Ubuntu, then Mint, now Pop!_OS.
I got a rather profitable career out of it: went into IT during/after college, then got hired into a big Silicon Valley company, stayed in that area for several years, then quit during COVID.
Then it’s probably just more
. Again: your post did not contain enough information for anyone to provide an answer to your question.
Antivirus doesn’t do what it promises. The only general solution for a compromised system is a clean reinstall. (This is true in Windows too.)
A process can change its name. If I wanted to make sneaky malware for Linux, I’d have it call itself more
or something innocuous too.
The correct answer is “this is not enough information”. Why should a real more
process eat ¼ of a core for any substantial amount of time?
If you log out of websites & delete your cookies on Windows, random browsing may be more inconvenient there.
Just be sure to pause for garbage collection occasionally.
Fake headline.
That’s the main advantage of parted
over fdisk
+ mkfs
, really.
Sure, but if I were recommending a Linux OS to a first-time user, I wouldn’t recommend today’s Ubuntu as it is likely to lock them into a proprietary single-vendor system, which is contrary to one of the main points of promoting free software.
The first-time user might not immediately notice the difference, but it’s (unfortunately) bad for free software to have more new users starting on today’s Ubuntu.
This is pretty sad because Ubuntu used to be the obvious choice to recommend to new users.
Mint and pop are basically ubuntu.
Big difference: Pop, at least, does not push Canonical’s proprietary “Snap” nonsense. You can use it if you really want, but it’s not installed by default. No snapd
on my system, thanks.
This is what Debian is for.
I’m pointing at the architecture, not the specific implementation. Build something like Spanner, not something like a blockchain.
1a. I must have misunderstood the problem report.
1b. No wait, holy shit, how did this ever work!?
2a. The director reminded us, at the last all-hands, that we should escalate to senior members of the team if we don’t know how to check our work.
2b. … yeah, they’re at Burning Man.
3a. Remember, they knew I didn’t have a CS degree when they hired me. Dammit Jim, I’m a chemist, not a compiler engineer.
4a. It could be worse. I could be back in academia.
5a. There are more cute people in academia.
6a. HOW THE FUCK DID THE THREE-HOUR COMMIT QUEUE NOT CATCH THIS BUG BEFORE IT WAS PUSHED ON FRIDAY AFTERNOON?
6b. (looks up author of broken commit) Oh, we need to send more whiskey to that team on Friday mornings. That’d shut them up.
7a. … yeah no, imma run the regression tests another time against an unchanged repo
7b. … resync and run them again
7c. … fuck, this is fucking voodoo but imma do it anyway WHY DID IT BREAK NOW
8a. Wow, fixing that took, um, four actual bytes of delta?
8b. Everyone should slow the fuck down and see if they can fix all their bugs in four actual fucking characters of change to the actual fucking source code.
8c. What the fuck do I know. Megan committed 924 LOC last week that fixed lfile caching, and caught the btqmixer bug.
9a. Sleeeeeeeep.
You don’t kill zombies; a zombie is already dead. You wait for or reap zombies. (A zombie process is just a process table entry with its exit status; it goes away once the parent process has read that exit status.)