Relevant Columbo: https://www.youtube.com/watch?v=NnDe2u5M7e8

Face it, Linux is just the kernel. You use systemd as your operating system.

Interesting that they bothered to make this considering KDE Connect already works on Windows

On other distros I don’t have to read the wiki to look up the syntax of installing nvidia drivers, or rustup, or neovim, or home-manager (the package manager that lets me install programs as a user The NixOS Way™ and if you use nix-env instead you’re doing it wrong (the instructions on the wiki for installing home-manager do not work anymore, and also involve nix-channels which you are apparently never supposed to use ever, and even after managing to get it installed and reading 3 articles about it I am still not sure what it does)) because no two of those are installed the same way

You forgot to put Windows 10 in “Maliciously Bad”

You will use Windows 11 or you will not use Windows at all

Me either but I’m tired of clearing my schedule to read wiki pages every time I want to make any change to my configuration

She asked a question. It was answered.

You spelled NixOS wrong

IPv6 is already backwards compatible though. There’s a /96 of the IPv6 space (i.e. 32 bit addresses) specifically for tunneling IPv4 traffic, and existing applications and IPv4 servers Just Work™ on IPv6 only networks, assuming the host operating system and routing infrastructure know about the 6to4 protocol and are willing to play ball.

I learned a lot about it from this video: https://www.youtube.com/watch?v=e-oLBOL0rDE

Another day of GNOME developers doing everything they can to convince me I made the right choice sticking with Plasma

What DE/WM do you use? Works great for me on Plasma.

I’m currently using Plasma Wayland on Arch with the 1080p monitor built into my laptop and an external 4K monitor right next to it at 175%, and it works flawlessly. When a window is half on one monitor and half on the other it actually looks how it’s supposed to. I can drag a window back and forth between the monitors and watch it rescale itself to run at that monitor’s native resolution. Some apps, you don’t even see the transition. The current scale is passed through to the applications, so text looks nice and sharp.

Fantastic! Love to see FOSS companies winning! Maybe someday soon Puri.sm will come out with a phone that doesn’t massively suck

I AM NOT! A! MORON!

Watch, hold on, I’ll prove it! I’ll perform a feat of brute strength in a blind rage that will end up hurting me in the long run! Then later when I find out that massive fall didn’t actually kill you and you fought your way back up through 2km worth of test chambers powered by sheer spite to come and confront me, I’ll act like nothing happened and beg you for your help because I have no idea how to run this place and it’s falling apart and the robot test subjects I built don’t work at all!

Huh? Could a moron do that?

update: i just looked it up and they are not. Visual J++ is a predecessor to C#. Nevertheless, the name “Visual J++” in all its Microsoftian goodness(?) is as good a descriptor as any for what C# turned into

In the early days of C#, before it was called C#, Microsoft gave it the most Microsoft name ever conceived for anything ever: Visual J++

Yes. You can specify tar -C somedir if you want it to extract them somewhere else.

As a rule of thumb, I always extract my tarballs in a newly created, empty directory, just in case whoever packed it didn’t put all its files in a subdir

They really, really aren’t. Let’s take a look at this command together:

curl -L [some url goes here] | tar -xz

Sorry the formatting’s a bit messy, Lemmy’s not having a good day today

This command will start to extract the tar file while it is being downloaded, saving both time (since you don’t have to wait for the entire file to finish downloading before you start the extraction) and disk space (since you don’t have to store the .tar file on disk, even temporarily).

Let’s break down what these scary-looking command line flags do. They aren’t so scary once you get used to them, though. We’re not scared of the command line. What are we, Windows users?

• curl -L – tells curl to follow 3XX redirects (which it does not do by default – if the URL you paste into cURL is a URL that redirects (GitHub release links famously do), and you don’t specify -L, it’ll spit out the HTML of the redirect page, which browsers never normally show)
• tar -x – eXtract the tar file (other tar “command” flags, of which you must specify exactly one, include -c for Creating a tar file, and -t for Testing a tar file (i.e. listing all of the filenames in it and making sure their checksums are okay))
• tar -z – tells tar that its input is gzip compressed (the default is not compressed at all, which with tar is an option) – you can also use -j for bzip2 and -J for xz
• tar -f which you may be familiar with but which we don’t use here – -f tells tar which file you want it to read from (or write to, if you’re creating a file). tar -xf somefile.tar will extract from somefile.tar. If you don’t specify -f at all, as we do here, tar will default to reading the file from stdin (or writing a tar file to stdout if you told it to create). tar -xf somefile.tar (or tar -xzf somefile.tar.gz if your file is gzipped) is exactly equivalent to cat somefile.tar.gz | tar -xz (or tar -xz < somefile.tar – why use cat to do something your shell has built-in?)
• tar -v which you may be familiar with but which we don’t use here – tells tar to print each filename as it extracts the file. If you want to do this, you can, but I’d recommend telling curl to shut up so it doesn’t mess up the terminal trying to show download progress also: curl -L --silent [your URL] | tar -xvz (or -xzv, tar doesn’t care about the order)

You may have noticed also that in the first command I showed, I didn’t put a - in front of the arguments to tar. This is because the tar command is so old that it takes its arguments BSD style, and will interpret its first argument as a set of flags regardless of whether there’s a dash in front of them or not. tar -xz and tar xz are exactly equivalent. tar does not care.

If you download and extract the tarball as two separate steps instead of piping curl directly into tar xz (for gzip) / tar xj (for bz2) / tar xJ (for xz), are you even a Linux user?

deleted by creator