Re the first route, what is the network mode of your container and which ports are exposed?
How familiar are you with Docker networking? Docker docs are here and may be enough on their own to help you out. If not, there are a ton of guides and tutorials out there that can help.
Another user commented that gnome boxes is setup in a way that isn’t conducive to what I want, setup as a qemu user bridge mode.
My knowledge of docker is novice at best, I’m only familiar with a handful of commands based on some hand hold levels of tutorials. Thank you for the resource, I’ll research it more to see if I can get a better handle on it.
To the people who switched to it from latex for technical documents (involving equations), how much adjustment did it need? I’m in the process of writing some papers/presentations and I’m fairly comfortable with latex but sometimes I do wish it was simpler
It’s much easier to get started than latex if assuming no previous knowledge of either, to the point I can actually recommend it to people in humanities and non-STEM in general. Syntax-wise it’s very different, so you’ll need to get used to it and look up the docs. I’ve been writing latex for ~5y before Typst and I think Typst’s documentation is FAR better than any latex source I came across: no messing with random outdated packages that are incompatible with your template’s, and don’t get me started on that bibtex/biblatex hellhole.
In Typst, most error messages are actually useful to describe the issue; you won’t waste time setting up your local build if you want to typeset offline; and the output is generated FAST - pretty much as you type it - which helps a lot with learning what works and what doesn’t.
The downside is that because it’s not as popular yet, it’s harder to find that magic stack overflow answer that solves your problem. So if you’re in a hurry with a deadline approaching, go with latex and practice some Typst on the side.
You don’t have to use Snap (except for LXC, I think?). It’s not enabled by default, but you can enable Flatpak and everything will work fine. Flatpak has Firefox and Chrome and all the other applications thst Canonical foolishly moved from their apt repos to their Snap repos.
There are some frustrating things about Snaps (loading all of them at boot time rather than at runtime, for quicker app start but slower boot, for example, and that stupid snap folder that can’t be moved) but honestly I don’t really see what the fuss is about as an end user. Nobody sets up a purely Snap based system anyway.
The problem with Snap is an ideological one. If you don’t care who runs your software store and if you don’t care about having the ability to add more software stores then the default, you’ll be fine with Snap. If you’re ideologically driven towards Linux, you’ll probably dislike the way Snap is set up.
Like it or not, Ubuntu is still one of the best supported distros out there. If you want drivers from any manufacturer, you get to pick between drivers tested for Ubuntu or Fedora. Every other distro repackages those drivers using their own scripts and compatibility layers because nobody over at Intel is going to spend company time specifically getting Garuda to work when its customers don’t sell hardware with it preinstalled.
Software like Discord and VS Code having the “.deb, maybe .rpm, or you figure it out yourself” approach of official distribution is pretty standard, I’d say, for better or for worse. It also helps that a lot of entry level Linux questions and answers online are about Ubuntu. Askubuntu may not be as vast and up to date as the Arch wiki, but at least the askubuntu people aren’t going to tell you off for not knowing advanced Linux stuff.
There are upsides and downsides to any Linux distro. You’re not “supposed” to think anything, try it out, keep an open mind, and pick what works for you.
strictly speaking, NixOS doesn’t have repositories.
NixOS has “derivations” (rules are written in the Nix language to generate a script that builds a package, which is called a derivation - yes, everything is built from source to the extent possible/reasonable) and “platforms” (the system that builds the derivation OR the system the derivation is built for). A “platform” is e.g. the CPU architecture, the libc used, the target kernel (there’s most support for Linux and Darwin, which is the macOS kernel, but e.g. FreeBSD is supported to some extent too). The derivation code may well be shared across platforms, though often platform-specific workarounds are required.
Of course, different platforms have different support. Some platforms have derivations from nixpkgs (the NixOS git repo) regularly built for them and put into the official binary cache (which stores the derivation outputs, i.e. ready-built packages for a certain set of inputs, which generally match what you would’ve built from source because Nix strives for reproducibility, you’re still free to override a package’s inputs and build it from source). linux-aarch64 is one of such platforms. Other platforms may only have a small set of core packages like gcc built for them, or simply require building absolutely everything from source.
The reason nixpkgs is not a repository (though I guess you could call it one) is because it only provides rules to build a package, but not the package itself. Some derivations (e.g. for Gog games) even require you to add some non-redistributable files to the Nix store manually. The derivations may or may not build correctly for each platform they’re supposed to work on.
The reason the binary cache is not a repository is because it’s just a cache for nixpkgs - it stores every derivation’s output (if the build doesn’t fail), even if that derivation is one that downloads a package’s source code (yes, that’s a derivation too), even if the derivation is from many years ago (which has historical value, as you can revert nixpkgs to an old version and still be able to download prebuilt versions of packages).
Together, they form something like a repository, but it’s still way too different. For example, unlike on Arch, I can stay on the same nixpkgs version for a long time without updating, which I really prefer because I have to build 3 kernels on each update, since I’m syncing the nixpkgs version of my 4 NixOS devices, only 1 of which doesn’t require a custom kernel config. Or I can always revert back to an older version of nixpkgs if a new one breaks something and it will still work. Or I can fork nixpkgs and change some stuff, and the stuff with changed inputs will have to be rebuilt locally, with stuff that didn’t change still available from the binary cache.
yes, if that AUR was in a centralized git repository, and kept track of inter-package compatibility, and centrally cached prebuilt versions of the packages for every single update, and you could also easily modify any of the packages, and there was a way to autogenerate build scripts, and and and…
I’ve played around with (only played around with, I haven’t done any actual development with either but I’ve heard they’re similar) GTK, QT and Tk (actually tkinter from Python), and QT seems the most intuitive. It just feels right to me, compared to the others.
I don’t have extensive experience, but I have been using the tiling in pop os consistently for a year and have really found it to improve my productivity and oganization on tasks I need many windows open for. Its not perfect and I’m starting to consider looking for options that give me more layout control, but was an excellent first option. It has a toggle right in the task bar to switch between windows or tiling, but once I spent an hour learning the keyboard shortcuts for the filing, the windows mode just feels so slow to set up good layouts in.
I hate suggesting another distro as a solution but if your main intention is gaming then you may be interested in nobara. It’s fedora but with gaming tweaks applied.
I don’t think you need 32GB of RAM. 16GB should be enough, and 8 will still do for light tasks (though modern apps and websites are starting to push that, which is terrible). Your OS uses any RAM you don’t use to cache files, which speeds up your system, reduces power consumption, and could save you some SSD wear by caching the writes.
If you haven’t already, you can mount a tmpfs over your browsers’ cache directories (a bunch of them in ~/.cache or ~/. config). It used to really speed up browsing back in the HDD days. I doubt it’s still necessary, but hey you’ve got plenty of RAM, right?
If you really don’t do anything but browsing, you could boot your entire OS into RAM and have a 0 SSD latency browsing experience.
You could also use the RAM to run a bunch of VMs or containers. I used to run a separate Pihole VM, for example; virtual machines are nice and isolated, so you don’t risk ruining your /etc directory with a billion different configured services. The big downside of running such stuff on your machine is that you quickly end up with a whole bunch of duplicates (I have like four versions of postgres running on a server somewhere because I’m lazy) but if you have RAM to spare, that doesn’t matter.
One container that may be worth looking at is Waydroid (or Anbox if you’re on X11) to run Android apps on your desktop. I find that a bunch of different services have web interfaces thst just don’t work as well as their apps, and running those can be nice. How much of a difference this makes will depend on the services you use, of course.
Lastly: don’t underestimate the advantages of plenty of RAM when programming. It’ll depend on what language you use, but many compilers will generate a million tiny files that will all be written to disk and read back. SSDs are fast, but random reads are still nowhere close to RAM speed. Your OS will hide most of this overhead, but I definitely felt the difference going from 16GB to 32GB because of file system caching alone.
The text editor that’ll be coming with Cosmic looks pretty slick! I’ve got a loooong way to go with learning rust so maybe I’ll take a look at the iced/pop libraries when Cosmic comes out 👀
You can start with the libcosmic repository, and the examples contained within. We’re going to work on revamping our design demo application soon, which will be a learning resource for COSMIC application development
Does a single board computer counts as a phone? Then a Orange pi zero 3. (Not like theres anything else to do other than read/lurk online communities, code and the occasional cloud gaming nowadays, so eh.)
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.