![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Sometimes. Most of the times. Not always.
Sometimes. Most of the times. Not always.
I blame all these polyamorous relationships with barely any rules.
My bets are on spiders and racoons.
Now this is a much more reasonable default. Like me. I managed to close a bunch of tabs and a window this week.
Please don’t use the duplex again.
Thinkpads were never cheap around here. Asus are cheap. The quality is many orders of different.
I need proper and maintained bindings for languages that can and know how to talk to the only portable interface, which unfortunately is C ABI.
With proper docs not referencing and jumping around to unreadable Cpp docs or sources on other places or not giving enough info inline and defering to the weird Qt docs and their custom compiler plugins.
Give me proper ways to build apps integrated without having to jump around and learn 3 technologies I absolutely despise and have no interest on interacting with.
This is my want to be able to create apps on kde.
Although the blog is about all the ways one can contribute with their experiences to the project, I still feel this would bring a lot more eyes and apps to the platform.
Self learner in a vibrant constantly moving company.
The kind of “people” that are ok with killing most of the others.
There’s some good info out there from the good people that know how things should work that created the reuse tool - https://reuse.software/ - and basically the conclusion is that nobody should be updating the years on the copyright line just because it’s a new year. The only useful info and what should be done is put the year when the file is created and that’s it.
Edit: took me a while to find the proper thing I wanted to link - https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code
Had to go first to the recent curl blog where the author wants to go the weird way of not having useful info at all on the files.
If you suspend the laptop when moving locations instead of shutting down or hibernating to disk then disk encryption is useless.
Always existed on firefox at least. It’s super old feature but modern interfaces seem to have mostly dropped or ignored it. On firefox depending on the distros it would be disabled, changed, etc. It conflicts with the middle click pasting from the second buffer feature. It’s like the backspace button going back, depending on the place it either works or is changed to meaning something else. At least these 2 were almost always different on firefox when using windows vs Linux and probably the first thing a user using Firefox moving from windows to linux would notice.
Yeah, but tailscale forces you to use logins from proprietary platforms, which is the reason I don’t use it. It doesn’t support a simple account creation and login with just an email and password.
It’s transparent for end user basically, but protects the laptop at least when outside and if someone steals the computer. As long as it was properly shutdown.
I had so many problems and had to constantly manage other distros before Arch that it was a lot of anxiety. Everytime new release of popular linux distro I knew it was gonna break if I tried to upgrade. Almost centrainly. For fear of that I had frankstein monster distro for work using lts version full of weird ppas with a more recent kernel and some more recent software that I need because everything was always old all the time. It was horrible to maintain and keep working.
Arch is just simpler, easier and much more stable. It’s just pacman -Syu all the time, have fresh software, recent kernels for the hardware improvements which is extremely important for when you buy new laptop and overall never crashes. It’s just a matter of reading the news, sometimes change a config that got deprecated, or replace some software that got abandoned or now there’s better alternative, etc. Sometimes things get some regressions for some weeks until things are bug reported and fixed upstream and eventually reach the system, but that’s waiting some weeks or rarely months. There’s always alternative to get involved in helping fix the problems with bug reports and patches if needed, but that’s extremely rare and only if you really are desperate.
Anyway, those problems were much worse on other “stable” distros, because if there’s something seriously wrong on the system you are only lucky to get fixes after a major release which may happen only once a year.
If the system is really critical and cannot fail me during work week I delay updating to the weekend sometimes. Even if I need to it’s just a matter of evaluating the risk. You do pacman -syu and see what’s comming. If it’s just some apps updating then it’s ok to do it. If it’s core system stuff like kernel, systemd, dbus, graphics drivers, maybe I’ll avoid it.
Overall it’s simpler and easier because there’s really only 1 or 2 things to keep in mind and all the rest just falls into place.
Using archlinux for more than 15 years on personal machines and maybe 5+ years on work computers.
The article needs a lot more explaining what it is about. Took too long to read to understand that it’s something about containers but understood nothing about what/why this matters.
Dark and moist.
Wait until people find out america bans certain cryptographic things to help them out.