The most stable rolling distro.
The most stable rolling distro.
Zip is fine (I prefer 7z), until you want to preserve attributes like ownership and read/write/execute rights.
Some zip programs support saving unix attributes, other - do not. So when you download a zip file from the internet - it’s always a gamble.
Tar + gzip/bz2/xz is more Linux-friendly in that regard.
Also, zip compresses each file separately and then collects all of them in one archive.
Tar collects all the files first, then you compress the tarball into an archive, which is more efficient and produces smaller size.
mod+shift+q
so you wouldn’t close hours of work by accident (e.g. when typing other mod+_
keybinds)
Half of the linux ecosystem is personal projects.
Linux itself started as
just a hobby, won’t be big and professional like gnu
It’s not useless as you can learn from it.
Almost. It doesn’t try to solve all the problems, though. I’d say it’s a passion project like Haiku and TempleOS.
From interview: it started as a research project. The author wanted a distribution that uses the least system resources with maximum performance.
He started with archlinux, moved on to gentoo and to go even deeper - found the infamous “linux from scratch” and started to shape his own distro.
Ok, because of this post - I decided to bite the bullet and try wayland again. And it was much better experience this time:
I’ve installed sway “pattern” on OpenSuse-Tumbleweed and:
waybar absolutely supports clicking tray icons.
I confused it with swaybar, that’s installed with sway by default and should be an i3bar-compatible. Waybar doesn’t seem to support i3bar protocol, but anyway, after I configured it - it’s like 95% there from what I want.
I could switch tomorrow if I could do my current setup:
Last time I tried Wayland in December, I had issues with waybar not supporting clicking tray applet icons. Also I’ve ported my dropdown terminals script to support sway - and it worked half the time, like, literally every second key press was ignored.
On one hand I have X session that currently has no downsides for me, on other - wayland that has no upsides. Tell me, why would I switch?
It’s also a good filter for useful videos vs ‘content’.
In theory this issue can be solved with LD_PRELOAD trick. E.g. redirect all/most/some fopen
calls to “$HOME” to some other directory. But before I try to tackle it myself: is there already a similar solution like that?
I don’t understand.
How is it hard to remember: “eXtract File” = “tar xf …”?
If tar is gZipped - it’s “tar xzf …”.
I don’t think I’ve ever seen tarball that wouldn’t work with one of these two commands.
For one - the error handling. Every codebase is filled with messy, hard to type:
if err != nil {
...
}
And it doesn’t even give you a stack trace to debug the problem when an error happens, apparently.
Second reason - it lacks many features that are generally available in most other languages. Generics is the big one, but thankfully they added them in last half a year or so. In general Golang’s design principle is to implement only the required minimum.
And probably most important - Go is owned by Google, aka the “all seeing eye of Sauron”. There was recently a big controversy with them proposing adding an on-by-default telemetry to the compiler. And with the recent trend of enshittification, I wouldn’t trust google or any other mega-corporation.
I have all apps I use daily in the appimage format. Yesterday I decided to try btrfs for my root partition and did my annual Linux reinstall. All my apps were already there and ready for work from the start.
I also have a usb flashdrive always on me with the same appimages. Just in case I’d wipe a hard drive by accident and wouldn’t have an internet connection or something like that (in case of emergencies). You can’t do this with flatpaks or snaps.
IMO, go’s gopher is ugly, not cute. But, anyway, there are better reasons not to learn Go.
There is so much that I would want to do that requires time to be “flowing”…
If we’re talking about physics-accurate superpowers, please add partial blindness - photons are frozen in place, they can’t reach your eyelids, unless you walk into them. And suffocation due to completely still air.
And … now you can’t even nap in peace 😐.
I have pretty minimalistic setup.
Three dropdown terminals, managed by a bash script: top for quick commands, left and right for nvim.
Bar is i3bar, with a custom status program written in Nim language (can display any command output with conditional colors).
1 - bloat
2 - click-bait title
Just tell me actual errors like a professional OS would.
Professional OS:
Flatpaks and Snaps become more efficient in terms of storage usage the more you use them…
I’m not disagreeing with that, but how many apps an average user requires that he can’t find in the distro’s repository? And how many snaps he should have installed, so it’d be more space-efficient than appimages, 10? 20? 30?
hint: for me - one is too many.
Flatpak and Snap share dependencies while Appimage doublicates all of them…
On the other hand, appimage only includes the libraries actually required by an app. Where Snap/Flatpack install big fat runtimes.
I’ve recently made a very simple gtk4 app and packaged it with all dependencies into a 10mb appimage you can just download and run. The very same app would rely on 250+ mb gtk4 runtime with snap.
And I could be fine with that; but no, it’s not that simple, you’ll have x3 gtk4 runtimes on your system. Because snap keeps 3 last versions of every snap pkg and it’s dependencies. I don’t know what flatpack installs, but it’s not efficient in that regard either.
2-3 gigs of libraries a program might not even need. It’s just wasted space for an average linux user. And if I was fine with that, I would be using Windows right now.
For a lot of people Ubuntu is the linux. Canonical is just good at marketing. For all it worth, Ubuntu is not the bad choice for average user who’s not into ricing and not bothered by bloat.
I’ve been using Arch and Manjaro for couple years each and in my experience they both break regularly. But, for some weird reason, Arch Linux is praised, when Manjaro is shamed upon.
Aren’t we all?