pivot_root

ZZ? ZC? Come on now, copilot. You have more options than simply killing it.

Hey now, someone doesn't need to be an abusive piece of shit to get a gummy. They could just really be into grandma.

They’re not awesome when your workflow revolves around the command line and you’re stuck choosing between wasting days trying to layer your configuration on top of the project devcontainer or giving up and using the unconfigured bash shell included.

The Darwin kernel is based on BSD… sort of. It’s a monstrosity hybridization of an ancient version of BSD and the Mach kernel.

I did say before the memory crisis. It’s not a bad deal now comparatively with everything else being overpriced, but that doesn’t change the fact that Apple hardware is itself overpriced.

isn’t expensive Bullshit. Upgrading from 1 TB of internal storage to 2 TB on a laptop is not a $250 expense. Before the memory crisis, I could have bought a brand new M.2 SSD with the full 2 TB for less than that.

I can’t remember if I was wearing it before, but I’m not wearing it now. It’s probably fine. I think. Maybe.

The blogger in question doxxed the owner/maintainer of Archive.today who in return doxxed the blogger.

Did you actually read the two articles posted by the blogger? The archive.today owner wasn’t doxxed. No personally identifying information was provided; it only aggregates already-known info including a couple of fake aliases. The most it concludes is that the guy is Russian or operating out of Russia.

https://gyrovague.com/2026/02/01/archive-today-is-directing-a-ddos-attack-against-my-blog/

https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/

Well, that explains a lot about the product quality. Their entire development workflow is a complete fucking mess.

• Long-lived feature branches.
• Creating merge commits to main just for the sole purpose of tagging them as releases while also maintaining separate release branches.
• Force-pushing tags to incorporate post-release hotfixes instead of releasing minor patch updates.
• Taking bugfixes from releases and merging them back into the development branch (have they not heard of cherry-pick?)
• Always using merges even when a rebase would be easier to follow and keep the history more straightforward.

Oh, no. I’m saying Microsoft owning your operating system and using it to push their browser as a default browser is a monopolistic practice, whereas using Chrome by is just reinforcing an existing monopoly. The same goes for Mac and Safari. Neither browser is good, but it’s a step in the right direction to punish a corporation for their active attempts to subvert competition in a bid to establish their own monopoly in place of the current one.

If you have to pick between two monopolistic corporations, using both of them but giving each a little less of your data and attention is a way to mitigate the risks and damage. If Microsoft can harvest data on how I use my computer, I can at least make it a bit harder for them to harvest my browsing habits too by not giving them browser telemetry too.

There’s plenty: Not supporting monopolistic practices. User preferences. Diversifying your software so you don’t get trapped in an ecosystem. Not having Copilot stuffed down your throat. User preferences. Making it possible to rip Edge out of Windows for the purpose of debloating.

That was something they could actually market to the consumer as a necessary upgrade, though. “Sure, you need a new cable, but component video has cleaner edges and less color bleeding.” “Sure, you need a new cable, but HDMI has better resolution and no fuzziness.” Going from HDMI 2.1 to DisplayPort 2.1a doesn’t offer anything other than higher bandwidth, and not even high-end PCs are capable of pushing resolutions at high enough framerates for that bandwidth to have been the limiting factor for games. Even though DisplayPort is objectively better than HDMI, the optics of replacing HDMI on consumer devices that are meant to be connected to TVs isn’t good. It will come across to consumers as an unnecessary, arbitrary change meant to push their TVs towards planned obsolescence. They’re going to complain about it, the media will pick up on the story and try to turn it into a scandal, and then legislators and regulators will step in and make decisions based on limited understanding of the technical reasons. By that point, one of the console manufacturers will have been pressured into backing down and promise to keep HDMI in their next-gen console, and the other ones will have followed suit because they don’t want to lose sales over it.

As long as the manufacturers are competing against each other, that’s never going to happen. The “gamer” consumer demographic has some of the most whiny, entitled vocal minorities. They’re going to endlessly complain about the next generation of console needing a special cable/dongle to connect to their TV, one of the manufacturers are going to fold, and then the other one is going to walk back the lack of HDMI because they don’t want to lose sales to their competitor.

Mac is very similar to Linux in that it comes with bash (these days zsh) and a lot of the command line tools you’d expect on Linux, including gcc No it doesn’t. The gcc command is a wrapper for clang, and the clang command is a stub that runs an executable used to install the “Xcode Command-Line Tools” It also uses the BSD coreutils, rather than the GNU coreutils present on most Linux distros. The two are only compatible up to functionality defined by the POSIX standard, and anything beyond that is an inconsistent mess. Windows is more difficult. The command line is very different (it inherits from DOS instead of Unix like both Mac and Linux). It doesn’t come with Python pre-installed If you limit yourself to not using WSL, sure. WSL 2 runs an actual Linux kernel with the same Linux executables you would find on any other distro. It’s still Windows and full of telemetry and AI garbage nobody wants, but it somehow manages to have better Linux compatibility than macOS.

They make entire SOCs. None of them are x86 because of the duopoly that Intel and AMD have thanks to their cross-licensing agreement, but they still have functional CPUs with a common ISA.

AMD: “Our partners will fry your expensive CPU on some boards.” INTEL: “Our software will fry your expensive CPU on all boards.”