I’m with the person you’re replying to, what’s an example? I haven’t had a problem working with filenames with spaces in at least ten years on windows, Linux or Mac…
gayhitler420
joined 1 year ago
Lol at how controversial that comment was.
I didn’t read any of that but Wayland doesn’t work with xscreensaver so I’m not gonna switch to it.
Thousandths of a hogshead gang represent.
boot the damaged system using a media with the chroot command, use it, do whatever is needed to fix the damaged system from inside it.
If it’s photoshop that programs been solid for about a decade under wine.
Idk about the other stuff.
Nothing. But once Wayland supports xscreensaver or vice versa I’ll switch.
What I’m trying to push back on is your assertion that everyone can do it.
Security auditing is an extremely complex and specialized field within the already complex and specialized field of software development. Everyone cannot do it.
Even if it were as straightforward as you imply, just the prevalence of major security flaws in thousands of open source packages implies that everyone doesnt do it.
If I were to leave piles of aggregate and cement, barrels of water, hand tools and materials for forms, a grader and a compactor out and tell the neighborhood “now you can all pave your driveways” I’d be looked at like a crazy person because presented with the materials, tools and equipment to perform a job most people still lack the training and experience to perform it.
Idk what the person you’re arguing with is trying to say, but as a prolific user of open source software, there are thousands of serious vulnerabilities discovered every time some auditing company passes its eye over github.
Malicious commits are a whole nother thing and with the new spaghetti code nightmare that is python nowadays it’s extremely hard to figure out which commits are malicious.
Open source software is not more secure by default and the possibility of audit by anyone does not mean that it’s actually getting done. The idea that anyone who can write software can audit software is also absurd. Security auditing is a specialized subset of programming that requires significant training, skill and experience.
If you really want the short version:
Systemd was half baked literally when it came out and figuratively as an idea, so much so that there’s already a replacement for it in the works.
A longer version:
Systemd replaced the init script style of boot and process management, which had been in place for decades. init scripts were so simple they could be understood just by looking at the name: the computer is Initialized by Scripts. Systemd was much more complex and allowed many more tools to interact with the different parts of the computer, but people had to learn these tools. Previously all a person had to understand to deal with the computer was how to edit a text file and what various commands and programs did. After systemd a person has to understand how to use the dozens of invocations of systemctl and it’s variants and if they are dealing with a problem, —you know, the only reason a person would ever be dealing with initializing services— they gotta know what’s going on with the text files that systemd uses to run different commands and programs.
So a person who already understood what was going on might rightly say “hey, this systemd thing is just the same shit with different file locations and more to learn”.
People complain about the creator and maintainer of systemd, lennart poettering . Poettering is also the person behind pulseaudio, an powerful but complex audio management daemon in Linux whose name you only recognize because it’s caused you no end of trouble. Pulseaudio was also replaced relatively quickly by pipewire.
The argument could be made (and probably has) that poetterings work is indicative of the problems with foss developers working as employees of major companies with their job responsibilities inclusive of their foss projects. The developer in that situation has an incentive to make big sweeping changes, they’re being paid for it after all, instead of being more careful and measured.
When every big foss maintainer is trying to find a way to justify being paid for it, their projects are never done.
At least poettering is working for Microsoft, ruining windows now…
E: oh my god I forgot about the binary log files! So before (and now), the universal format for log files was plain text. You know, because it’s a log that’s text. Systemd uses binary log files that need a special tool to open and parse. So if you want to look through them on a computer without that tool you’re kinda screwed. Now systemd isn’t the only software package with binary log files, but many people have made the very persuasive argument that it’s not a trait to copy.
E2: actually spelled the man’s name right. Thanks @floofloof@lemmy.ca !
In addition to all that @MystikIncarnate@lemmy.ca said, implementing an am or fm receiver on an existing device is as easy as plopping down one of the existing bga chips that has an antenna input and an audio output. here’s one of the bigger ones that needs a killer 3mm x 3mm land pattern. It’s also only $1.79 or so, which is expensive for an ic, but in the context of a phone wouldn’t contribute significantly to the cost of the device.
The need for an 1/8” out would be the worst part because ironically, phone jacks suck for uhh… phones.
Escape characters and autocomplete exist.
It’s also really good practice to account for weird characters in programs and shell scripts you write because then you don’t have injection vulnerabilities or unicode problems.
Seriously, what’s an example of spaces in filenames causing a problem?