I like systemd sometimes. Other times it confuses me. Particularly the way cgroups work. The way splicing works. Why oracle mem usage is still uncontrollable when I set user splice restrictions. Idk, I’m still learning it. I don’t like the terminology it uses sometimes too like “snapshot.” When I first read about systemd snapshot I was like oh cool you can snapshot the system. No. Also some esoteric things it supposedly supports don’t work sometimes. I find the idea of systemd targets and fstab having anything to do with each other anathema. Idk.
1. didn't know how Colorado already does it
2. doesn't know how hard it is to get humans to count without errors
3. doesn't know how expensive having that many temp staff count ballots is.
You already can sorta, llms do math better when you write it in latex (assuming it is the kind of math written about in latex more often) but even for early stage math latex is close to how people denote it already so it tends to perform well
Yeah, as others mentioned, uploading pictures is a way, writing in latex is another way. Upload pictures costs more than latex but is more convenient. Both of them works well
I find it amusing how you answer your own "question" before asking it. Why would they target the marketing material at people who already know they aren't going to need to upgrade?
Roopepal did someone piss in your coffee this morning?
I had no questions. I’m merely saying that it’s funny they’re comparing to old technology instead of last year’s.
It’s a valid criticism.
Take a breath.
Apple knows an M4 is a hard sell for M2/3 owners. Except if you have specific workflows that can take advantage of the newer silicon, you'll spend a lot of money on something you probably don't need. I have an M1 32GB with multiple software packages running, and I see no reason to replace this machine.
This is why Apple is comparing against M1: M1 owners are the potential buyers for this computer. (And yes, the marketing folks know the performance comparison graphs look nicer as well :)
I’m not sure if this is the right graph, but I read somewhere, household size has been going down over time, so using household income is a bit misleading actually.
I’ve had that POS SELinux block me from logging directly into the console with root (nothing wrong with the pwd). Thank VMware for snapshots. I hate SELinux.
But the job requires it.
As for people who seem to love it so much, they probably don’t have to deal with it all the time.
The problem is that when people don't know how to use it and instead turn it off they're immediately deluged from every side with pathetic nerds screaming that YOU DONT HAVE TO TURN IT OFF ANYMORE RUN THIS ARCANE SEQUENCE OF COMMADS THAT YOU DONT UNDERSTAND AS ROOT AND THAT WILL FIX THE ONE ISSUE YOU HAVE without understanding that not every computer system needs to be locked as tight as a server that's being shared with a bunch of untrusted users who are running god knows what.
Why use RHEL if you don't want one of the main advantages it offers? There have been numerous exploits that RHEL has been protected against because of SELinux and their policies.
Sure, not all servers need to be secured, but why use RHEL then? Why not use Debian or some RH fork that doesn't have it on by default, or even SuSE?
The people who disable it out of convenience are generally bad admins, and generally being lazy and/or incompetent.
Thank goodness you're here to tell them that. It would really be a shame if they did threat modeling and determined it was not necessary for their use case. That would make you look goofy and kind of a jerk.
Heh. Yeah, people mostly disable SELinux because they did threat modeling and determined it made sense, and don't just switch it off due to laziness or incompetence.
I think claiming that is a pretty goofy argument, personally.
Followed by "surely the year of the Linux desktop is at hand!"
I'm not going to link it here given his disdain for this site but jwz at least got the CADT development right. If you stop fucking rewriting things every couple of years then maybe the average user could catch their breath and catch up but if you keep changing things that don't need changing (ALSA -> PulseAudio -> pipewire -> whatever is already in the works to replace pipewire) instead of ACTUALLY FIXING THEM then you lose the right to be surprised when someone just trying to use their computer just gives up.
> but if you keep changing things that don't need changing (ALSA -> PulseAudio -> pipewire -> whatever is already in the works to replace pipewire) instead of ACTUALLY FIXING THEM
This is possibly the dumbest thing I read in a while...
1. PipeWire was written to fix PulseAudio and is a drop in upgrade. How do you think things get fixed otherwise?
2. Why would anyone rewrite PipeWire at the moment, why would you think that?
1. PulseAudio needed a redesign, there was no fixing to be done. It was utterly impossible to support low-latency audio, the protocol was not right, the client API was wrong, the backend was not right etc.. Also, ALSA is the wrong place to add more things, it should just be a driver abstraction.
Also note that PipeWire reuses the most complicated/fundamental part from PulseAudio: the device probing and mixer management. This code took 10 years to tweak and is taken directly from PulseAudio.
As a side note, there was a lot of investigations if things could be written on top of JACK2 but that also was infeasible (mostly the IPC protocol and API needed a rework, no security with memory sharing, support for Video. The scheduling ideas were taken right from jack2, though).
2. This is true but PipeWire is not just a random new rewrite. It was written with a deep understanding of both pulseaudio and JACK (later in the developments) internals and design. Many (of the good) ideas from those projects survived in PipeWire. This is actually a perfect example when a rewrite is a good thing.
Now, what is even easier than writing PipeWire is not understanding why things are done the way they are done and then complaining about it.
I don’t want to diminish others experiences, because I’m sure they’re just as important as mine.
All I can say is anecdotally I haven’t had any issues with disputes…in fact the dispute experience for me has been better than other cards. The app makes it quite simple.
