I know tar zxf and xjf off by heart. I probably do 100x as many extracts as creates. Tar is a stupidly antiquated command though.

Concerning logs:

1. You can still log to text if you want by configuration (e.g. forward stuff to syslog) and you can use any tools you like to read those files you want. So if you like text logs you can get them. You can even invoke journalctl to output logs on an ad hoc / scheduled basis in a variety of text formats and delimited fields.
2. Binary allows structured logging (i.e. each log message is comprised of fields in a record), indexing and searching options that makes searches & queries faster. Just like in a database. e.g. if you want to search by date range, or a particular user then it’s easy and fast.
3. Binary also allows the log to be signed & immutable to prevent tampering, allow auditing, intrusion detection etc… e.g. if someone broke into a system they could not delete records without it being obvious.
4. You can also use splunk with systemd.

So people object to systemd writing binary logs and yet they can get text, or throw it into splunk or do whatever they like. The purpose of the binary is make security, auditing and forensics better than it is for text.

As for scripts, the point I’m making is systemd didn’t supplant sysvinit, it supplanted upstart. Upstart recognized that writing massive scripts to start/stop/restart a process was stupid and chose an event driven model for running stuff in a more declarative way. Basically upstart used a job system that was triggered by an event, e.g. the runlevel changes, so execute a job that might be to kick off a process. Systemd chose a dependency based model for starting stuff. It seems like dists preferred the latter and moved over to it. Solaris has smf which serves a similar purpose as systemd.

So systemd is declarative - you describe a unit in a .service file - the process to start, the user id to run it with, what other units it depends on etc. and allow the system to figure out how to launch it and take care of other issues. It means stuff happens in the right order and in parallel if it can be. It’s fairly simple to write a unit file as opposed to a script. But if you needed to invoke a script you could do that too - write a unit file that invokes the script. You could even take a pre-existing init script and write a .service file that kicks it off.

Kind of sad there are still people raging over systemd. When it flares up in discussions there is the usual debunked nonsense:

• it only logs information to binary and this is somehow bad. Except it it can be configured to log to text as well and it uses binary so it can forward secure sign records to prevent tampering as well as offering database style query operations.
• it’s insecure because the repo has millions of lines of code. Except that they compile into hundreds of small binaries running with least privilege, and often replacing the task of far more dangerous processes (e.g. there is an NTP client in systemd which sets the time and nothing else).
• various rants about the primary author

What is more bizarre is the nostalgia and hearkening back to sysvinit scripts when systemd didn’t replace sysvinit! Systemd replaced upstart which replaced sysvinit. Because writing 100s of lines of script to stop/start/restart a process sucked - insecure, slow, didn’t scale, didn’t capture dependencies and everyone knew it. Upstart was the first attempt to solve the issue and was used in Debian / Ubuntu, Fedora / Red Hat, openSUSE and others until systemd came along.

I worked in IBM for a bit before Notes and it was even worse. Everyone was given terminal software that connected to some mainframe to read email. The terminal didn’t even refresh so if you wanted to see if you had gotten email you had to refresh it manually. Fortunately I was only a contractor at the time so didn’t get much email although I did get one from an employee apologizing for cheating on me, and a followup saying the message was meant for someone else lol

I think JIRA is okay. I’ve used MUCH worst bug reporting software. The worst thing I can say about JIRA is that it is designed to implement scrum and IMO scrum is cargo cult programming.

The best that can be said of Sharepoint, is it could be worse, you could be using Notes.

I’ve been in the industry some time but here are some of my most hated software I’ve been forced to use:

• IBM Clearcase. Absolutely the worst dogshit source control system ever to exist. Complex, fragile, arcane, slow, network intensive. The company had to employ people fulltime on each of its sites whose only job was creating branches and mirroring repos on other sites. The operational & licensing costs of running it must be insane. Some defenders might claim “but it’s so powerful!” or “look how we can create fancy layered views” as if that excuses it for being terrible in the most basic ways. Fixing it must have been intractable because IBM Clearcase eventually produced a faster remote client that talked to a proxy of the view running on a server somewhere. More expense and complexity.

• IBM/Lotus Notes & Domino. Another complex, arcane, slow, unintuitive, frustrating product by IBM (though owned by HCL now). Originally a content management system with an email / calendar with its own terminology and workflows completely divorced from any other email / calendar system in existence. Various iterations attempted to rework the front end to appear more user friendly but it was illusory - click button or two and you were confronted with dialogs that hadn’t changed in 30 years.

• Internet Explorer. I’ve worked in company after company that had some really awful in-house expenses system or clock-in/clock-out or some enterprise junk that NEEDED Internet Explorer and no other browser would do because it was so badly written that it couldn’t render properly or it used an ActiveX control.

• HP/Microfocus ALM. Another over-engineered, arcane, unintuitive piece of enterprise software. This time for tracking bugs, features, testing etc. Complicated and slow, heavily dependent on Internet Explorer and other deprecated Microsoft tech.

• Trend antivirus. Almost every corporate antivirus is bad but this one has been the bane of my existence. I write code which does stuff like encryption and compression/decompression and this piece of shit would constantly trigger warnings and delete binaries I was trying to build and develop. When it wasn’t interfering with my work, it would just be constantly hogging CPU and slowing down disk activity.

• Enterprise software in general. This crap is sold like Kirby vacuum cleaners - a pushy salesman convinces a clueless CTO to buy junk that can seemingly do everything and a sign contract for $$$. And then this stuff is there FOREVER. Management will ignore complaints and the obvious shortcomings of the system because its paid for and the sunk cost fallacy kicks in.

It would be better to “git clone” a repo under threat of removal than fork it in Github. That way an entire copy of its history is preserved. It’s possible the forks still exist for now, even if Yuzu removes their official repo, but if Nintendo serves Github the legal paperwork then the forks will get blasted.

That said if someone clones the repo, they probably ought to think twice before putting it back in the cloud without sanitizing / reconstructing the branches & history absent of the bits that got Yuzu into trouble in the first place.

Yuzu gave them the opening to sue though. If they had been more circumspect - “Oh this is to develop homebrew / indie games nudge nudge” then maybe Nintendo wouldn’t have unleashed the lawyers or done so ineffectively. After all it wouldn’t be Yuzu’s fault if some wicked website corrupted their pure intentions by releasing device keys or patches that allowed their emulator run commercial games. But they were more blatant than that.

Also from an empathic perspective, of course Nintendo were going to sue. Yuzu should have known they would since that’s what console platforms do when something interferes with their profits. Yuzu is doubly bad since it interferes with hardware sales and game sales unlike custom firmware / cartridges which only affect game sales.

Of course the genie is already out of the bottle. Yuzu’s source code and binaries were on github for anyone to clone / fork. All the games are out in the wild. The piracy will carry on. I think it’s fair to say the NSP is effectively dead as a platform at this point. If a NSP2 turns up this year, as rumored, then I expect it will have revised anti-piracy measures and potentially a heavy online service aspect to go with it - it’s far easier to detect pirates and wield the banhammer when a device is online.

If a server were an obvious conduit for disinfo then other servers could defederate from it. But if it was different accounts on different servers mixed in with authentic users then it’s almost impossible to remove. What tools does mastodon / lemmy even provide to spot inauthentic behaviour? And because we’re talking different servers run in different ways there is no clear picture from above that can be formed in the same way that a centralized social media platform might have - identifying suspicious clusters of nodes or traffic.

As for federation’s future we’ll wait and see. Both bluesky and threads are talking of providing federation protocols - threads using activitypub and bluesky it’s own API. As for Mastodon & Lemmy I see a lot of positive interest in these things. The fact we’re commenting on Lemmy instead of Reddit says a lot.

I do fear that as federation grows, then so too will potentially the same threats that happen on centralised social media. The fediverse is going to have a lot of vulnerable servers who won’t moderate or detect trolls & bots and over time the issue could become extremely onerous.

All large news orgs and NGOs need to do the same - federate their server which becomes the source of truth, and then mirror the content over other social media which is not federated. This may or may not include Twitter. I imagine that over time having news and reporting across social media will diminish any advantage Twitter possesses and then news orgs / NGOs might decide if they want their content on a platform like Twitter that cannot be bothered with things like stamping out bots, trolls, inauthentic actors, or supporting a free and fair press.

I don’t think any solution is ideal but imo it’s better than dual booting.

It works great too. Day to day I’ll be building Linux code, running IntelliJ under X, installing docker containers and doing other stuff all from a Windows desktop.

You can use Linux and Windows at the same time with WSL. Works extremely well for people who develop Linux but also need Windows stuff.

If you look at any modern desktop application, e.g. those built over GTK or QT, then they’re basically rendering stuff into a pixmap and pushing it over the wire. All of the drawing primitives made X11 efficient once upon a time are useless, obsolete junk, completely inadequate for a modern experience. Instead, X11 is pushing big fat pixmaps around and it is not efficient at all.

So I doubt it makes any difference to bandwidth except in a positive sense. I bet if you ran a Wayland desktop over RDP it would be more efficient than X11 forwarding. Not familiar with waypipe but it seems more like a proxy between a server and a client so it’s probably more dependent on the client’s use/abuse of calls to the server than RDP is when implemented by a server.

It’s a rotten analogy. Comparing Linus having a go at some volunteers is not analogous, or comparable to a father abusing kids.

Because of it, quite obviously.

I define effective by the fact it was self evidently effective. No need to split hairs or dissemble here. Linux is objectively, indisputably the most important piece of code in the world. Everything else, such as a the context free boo hoo about some times when he has had a go at people is just noise.

The logic is simple. This is s his style and it demonstrably worked. I’m sure you could point to someone else’s style that also works in another context but that’s irrelevant.