Building on this, I recommend zoxide instead of only fzfing or regexping.

For people who like to keep everything they ever create, like college students, you can use z 18.04/1 to get to a directory like ~/hw/random-school/fresh-1/analysis-18.04/pset1.

Lets you nest without fear.

(Also, about your question: I’ve personally used ~/git/<projname>/ and ~/git/<org>/<projname> at the same time – e.g. ~/git/aur/fuzzel-git)

Wow, you’re right, autotools dev work started a decade prior to Linux 0.01’s release. And looking deeper into ./configure, there looks to be checks running here that only matter on old Solaris systems…

At least it’s not node_modules

They call it a polyfill because it polyfills your disk

Terrible bait

Is that considered bait? I’ll remove it, I don’t mean to be hostile.

What do you mean by “more powerful” wrt CMake? Are you referring to, say, integration abilities with other projects (since know CMake is really widely-used)?

Thanks for the advice and the example!

Yeah I was considering using one of these two, out of curiosity.

I’ve heard complaints about CMake… on pre-2015 forums, so I don’t know where it’s at now.

I’ve done very little from the developer side of Meson but I do recall having tried a sound theme that, inexplicably, had a Meson-based installer. (It was just .ogg files iirc.) That’s probably a good sign if someone picked it over an install.sh

Though you’re right, there’s probably little advantage in me not using a Makefile here, except again, curiosity

Lots of good answers here but I’ll toss in my own “figure out what you need” experience from my first firewall funtime. (Disclaimer: I used nftables – it should be similar to ufw in terms of defaults though).

• Right off the bat, everything unneeded was blocked. I “needed” no configuration, except for maybe…
• Whatever CUPS runs on (when I use it)
• Sometimes I ran python -m http.server – I unblocked port 8000 for personal use.
• I chose to unblock port 53 (DNS). I wanted to connect to another computer via hostname IIRC (e.g. connecting to raspberry-pi.local. I might be misremembering this though).
• At one point I played with NGINX – that’s port 80 (HTTP) and port 443 (HTTPS).
• SSH was already permitted (port 22 – you need root access to enable traffic through ports below 1024 anyway so this wasn’t an issue for running typical apps)

I didn’t use WireShark back then, really. I think I just ran something like

sudo lsof -nP -iTCP -sTCP:LISTEN

which showed me a bunch of port traffic (mostly just harmless language servers).

You don’t have to dive to deep into all the “egress” and “ingress” and whatnot unless you’re doing something special. Or your software uses a weird port. (LocalSend lol)

Oh I love the “walk me through what I’m about to do” concept. Dry runs should be more common – especially in shell scripts…

The world would be a better place if every install.sh had a --help, some nice printf’s saying “Moving this here” / “Overwrite? [Y/N]”, and perhaps even a shoehorned-in set -x.

Hope your r/w wasn’t eaten up by the subfolder incident (that I presume happened) :P

The depth of a dive is always delightful! Does K8s have a solid use-case for the project or did you just sK8 for fun?

Round two, hell yeah.

The aesthetica of a stack of notes, born from a “dead end”, is secretly an odd motivator. You look back and see

Here is the breadth of what we did wrong.

and then beyond you, the effort lays itself out in a pretty trusswork.

__{or_maybe_i_just_think_well-used_notebooks_are_pretty}

Hah, stochastic parrots.

Makes me wonder. Every laziness I’ve had with the vector guessers, I’ve seen an exact counterweight.

One, you can invoke more often (throw ChatGPT configs against the wall until it doesn’t error); the other you can invoke more deeply. So I can’t help but wonder – when we cancel out all the terms – if the timesaving sum is positive or negative. ¯\_(ツ)_/¯

Yeah, it’s pretty funny how distros just passed each other by like that. Back then it was Debian that was regarded as the hyper-poweruser distro:

The reason I havn’t used Debian is because I can’t install it. “This guy is totally clueless” you might think. My only response is that I’m writing this on a Gentoo box that I have installed myself.

And then now there are plenty of people reading this thread who liked Windows 7. As time passed, their grade on the ease-of-use of A passed the don’t-get-in-my-way of B, and a load of Windows 10ers jumped ship to Linus & Friends, the last place their Windows 7 selves would have expected to go. Always a reminder that the end of history isn’t now.

Bending the question a little but my second “first impression” of Arch’s “simplicity” surprised me the most.

I was running Gentoo for a while before deciding to move back, and I was surprised that somehow I had

• saved space
• gotten faster at doing new things (…)
• didn’t lose any boot speed or anything like that

Granted, I had jumped on Gentoo because of misconceptions (speed, ricing, the idea that I needed USE flags), but going back, I saw things more clearly:

• the AUR being basically a shell script download + 300 MB of base-devel was simpler and more space-efficient than /var/db/repos (IIRC – since the portage and guru ebuilds were all held locally anyway after syncing, an on-demand AUR saved space).
  • the simple automatic build file audits on Arch felt more clean to me. I like checking my build files; had to make a script for the guru ebuild equivalent (but maybe there’s a portage arg i missed somewhere – wouldn’t be the first time)
• Arch repos separating parts of packages in case you don’t need some part (like splitting some font into its languages, or splitting a package into x and x-doc and x-perl) was almost a simple USE flag-ish thing already
• /etc/makepkg.conf was Gentoo’s make.conf. And its build flags looked similar to the CFLAGS I manually set up anyway.
• My boot time (btrfs inside LUKS with encrypted /boot) was the same with systemd vs. openrc
• I realized I liked systemd (because of the completeness of my systemctl muscle memory, like with systemctl status and journalctl, or managing systemd-logind instead of using seatd and friends).

Not bashing on Gentoo or anything, but it’s when I realized why Arch was “simple.” Even me sorely missing /etc/portage/patches was quelled by paru -S <pkg> --fm vim --savechanges.

And Arch traveling at the speed of simplicity even quantifiably helped: Had to download aur/teams the other day with nine-minute warning.

¯\_(ツ)_/¯

Successful GitHub pulls are rare; more often, patches live like this. You’re better off contacting the maintainer of the subsystem you’re editing. See the official submission guide.

Not to be dejecting!

Fun investigations (tac and factor), things I never bothered to check the existence of until now (install -s), and fundamentals I glossed over ([). Pretty fun read.

And of course,

And that’s why the ‘$cmd’ command is my favourite Linux command.

Stunningly simple, solely a shift. I love MVPs… we can possibly even remove the -P completion func switch :P

At a level that the user doesn’t have much control over, I fear both stock systems are about the same in terms of privacy.

According to an analysis by Köllnig et al. (2021) on 500k+ free Google Play/App Store apps, tracker libraries such as Google Play Services/Apple’s SKAdNetwork/cross-platform libraries are used in about equal percentages on both app stores’ free apps. These free apps’ trackers are generally not configured to follow GDPR data-minimization practices, even for kids’ apps, but it’s to be noted that Android has a disadvantage in that advertising ID is more used in Android apps than Apple apps. However, Apple has disadvantage too: the researchers noted that Android’s intent system and different permission model makes apps seem “more privileged” than Apple’s, but Apple makes accurate analysis of their apps’ reach difficult, judging by the larger failure rate in app decompilation as well as the more opaque approach to permission disclosure. Although the paper might imply Apple has improved over time, since it mentions Apple’s implementation of opt-in tracking in 2021, after the study, as a limitation, keep in mind Apple’s new movement towards advertising as a form of revenue, as discussed by Apple Insider (Owen, 2022) and Bloomberg (Gurman, 2022).

Of course, Köllnig’s study only reflects tracking in “curated apps” for either platform. It does not discuss hardware/firmware/system app-level privacy, which users have little control over (Leith, 2021 – easier reading with TomsGuide). Leith found that either OS phones home (lol) every ~4.5 minutes, and even though Google may send more data (even from the clock app!), Apple profiles your social network via MAC addresses on your Wi-Fi as well as location geotagging, which the TomsGuide article called “quality vs. quantity”. This builds on the idea that Apple might seem more private, but only ostensibly so, judging by these more particular looks at their data collection and the trend of their increasingly data-focused business model.

Does that mean the choices between stock OS don’t matter? Well, no – as for me, who can’t afford a Pixel anytime soon, I’ve chosen Android on account of freedom outside of curated app stores. Yes, PrivacyGuides may not recommend F-Droid, but the opportunity cost in security there may be negligible compared to the convenient and easily-handled privacy received in exchange*, at least for typical less-savvy threat models like my own. (This favorability is illustrated in a forum debate here (Lukas, 2023), though in a context less relevant to stock OS comparisons.) Ignoring the facet of freedom with stock Android, the possibility of large privacy advantage one way or the other, strictly in terms of stock Android and stock iOS operating systems, is marginal if it even exists.