Plus, I don’t find slack super competitive in terms of features & usability.
I remember having a much better experience with mattermost.
Plus, I don’t find slack super competitive in terms of features & usability.
I remember having a much better experience with mattermost.
I think I was thinking about desktop apps when I answered, but I feel out of context now 😬
Isn’t it about a web engine being roughly 60MB? 😕
Sadly I kept it private because it exposes a bit of my company’s network structure (with encrypted secrets, but still…) :/
It’s not the best experience though : the pencil doesn’t work as well as in Fedora (GNOME doesn’t detect tablet mode, which only seems to affect buttons behavior) and it recompiles the kernel everytime it needs to be updated (very often, so I pinned a version).
I’d say arch is a great distro if you love to tinker a lot and/or want to learn a lot about the Linux ecosystem. If you don’t recognize yourself in previous sentence I’d probably stick with fedora 🤷
I briefly used Fedora (Gnome) on my SP7 which worked super well. Then I moved to NixOS because I’m a nerd 🤓
I recall that the Rust book is awesome, it should cover everything essential! I don’t know the other two, but rustlings probably follows the same path and might be a good sidecar for exercising :)
Good luck in your journey!
Hell? I don’t see what you mean, that’s a fairly simple concept!
https://doc.rust-lang.org/nomicon/subtyping.html#variance 🫣🔥🔥🔥 (the table in this section sometimes haunts me in my dreams)
It also has the best learning resources I’ve ever found for a programing language, which are free BTW.
I’ve tried to found a Python course for a friend (paid or not), and I couldn’t find anything that looked close to the quality of the Rust book. Some paid online courses have to be awesome but they are all paywalled before the first relevant chapter 🤷
I moved to NixOS this year and it really felt like something new. You need to learn a little functional language for configuration (nix) and can manage your whole computer on a descriptive and reproducible way.
There is also an awesome side effect : packages (and OS configurations) are built the same way as you build your configuration. For me, it meant that it was the first time it was obvious how my distribution works and how I could contribute. It took me about one hour to submit my first ever PR to update a package : https://github.com/NixOS/nixpkgs/pull/290710
Also note that you can experience nix (the package manager) on any distro, if you want a safe try you could for example have fun with home-manager to handle your dotfiles.
I have a channel on my team’s Slack were I just vent off on these kind of situations 😬
#windows-is-the-best, inspired from #gitlab-is-the-best, the chan were everyone vents off when the CI refuses to pick up workers 😅
I’m not that surprised, a lot of people around me dot have a clear picture of what is the relationship between MacOS, Linux and Unix is. So I suppose some of them would guess that Linux is a modern fork of Unix and MacOS based on Unix.
It reminds me I published this Rust library a while ag o 🤣 https://crates.io/crates/prog_rs
(Not ambitious or maintained, rather use indicatif if there are Rust developers around)
The gen
keyword is too much teasing, I know it’s not round the corner but I’m gonna explode 🥺
Road to 2027 then?
But they were still created from the actual innovation of pagerank, straight out of public research, right?
The point of Arch is not that it’s hard to install the point is that it’s modular and you can choose exactly what you need. So in order ton maintain it you may need to know about pipewire, bluez, Wayland, synaptic, tlp, …
Once you know the name of most modules and graphical application it’s indeed pretty easy because Arch’s wiki is great. But I don’t think it’s a great way to discover the ecosystem and you would probably not benefit from Arch specificities compared to another distro.
I think the only person I would recomand this to would be a computer scientist who needs to learn as much as possible about Linux in two months.
println!("{comment}");
C’mon, it’s 2025!