GTK 3 support just in time for GTK 4 & 5

Sometimes when I’ve torrenting from a public wifi I’ll get a malicious .scr file - but since I torrent from an Android phone it can’t do anything to me.

I’ve been using it on and off since 1994. I still have a slackware dist on CD with the 1.1 kernel. I think Linux is great although I still prefer to use Windows, and Linux via WSL which is my optimal set up these days.

That’s more or less it. Linux Torvalds hates the different package managers and dependencies in different dists and versions of dists. He claims it’s virtually impossible to ship products that just run on some random dist and cites his own sideproject which is a sea diving app where he builds binaries for Mac OSX and Windows but can’t for Linux. He also praises Valve for using containers.

In theory it means slightly larger binaries, but the flipside it means Steam for Linux runs on a lot more dists, and so do the games and it’s far easier to test they actually run.

Ubuntu. There are mixes of it but out of the box Ubuntu is about as straightforward a dist to install as possible and it is well supported.

That said “new laptop” and Linux are not always a match made in heaven. You might try it from a boot stick and confirm that things like the GPU, touch screen, touchpad, fingerprint reader, USB C / Lightning all work properly.

And downloading updates is a good thing. Means that the fresh installation isn’t vulnerable to something that was fixed between when the USB / DVD was pressed and the time the person installed it.

Linux has made leaps and bounds with usability and ease of installation but it’s no better than any other modern OS - which is a good thing. Installing Windows from a USB stick is not difficult - the simple path is literally, pick a language, select your wifi, choose who is logging in, click install and go grab a coffee. About the only difficulty if you can call it one is that some installs will ask for a serial number because it’s a commercial product.

Also, the number of questions & buttons during installation is one thing but the certainty of a functioning system is another. Linux is better at supporting old hardware, Windows is better at supporting new hardware. Choose accordingly if that matters.

I don’t even know what this graph is even supposed to mean. Bitch about Windows all you like but the installation process is typically very simple.

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.

Spotify and other such services almost certainly sound worse because they are compressed. But it’s not really a like for like comparison with vinyl. Spotify is streaming audio for people who want to play music casually in cars, earbuds etc. It offers convenience, not perfect sound fidelity. FLAC / CD on the other hand could be compared to vinyl and would win hands down for better frequency and range. The only reason they wouldn’t is if the CD master sucked and the vinyl master didn’t.

And vinyl is very lossy in its own way. The (digital) master of each side undergoes dynamic range & frequency compression to fit the limitations of the format (e.g. to reduce sibilance, track width). Then the master is cut into a lacquer disc from which a “father” is made, from which “mothers” are made, from which stampers are made and from which the vinyl record is made. So the vinyl in someone’s hand is a copy, of a copy, of a copy, of an altered digital master. The stamper too wears out so if someone is unlucky they get a pressing right the end of its life. And playing the disk can cause wow, flutter, distortion and general wear & tear can cause hiss, pop, dullness and scratches.

So vinyl will never sound better unless it received a better master than other formats.

In the 70s and 80s there were kids toys which played injection moulded plastic discs with a stylus that tracked the groove. I think you might be able to achieve something similar out of a printed record if it was spun fast enough but it wouldn’t sound great.

I had the misfortune to have some PLA snap just before and after the direct drive in my Bambu P1S and it took ages to get it out. I think age and moisture can affect filament, especially it blended with wood dust, sparkles or something which undermines it even further. I’ve resorted to packing my AMS with silica beads to hopefully mitigate for the issue and I threw out the filament that caused the issue. Ironically this is one of the few places a bowden extruder is any benefit - if the filament snaps just push it from behind through a heated nozzle until the blockage clears.

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.

Still people raging over something that reliably and securely powers millions of Linux installs.

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.

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.