Meanwhile the electron app you’re trying to run
Meanwhile the electron app you’re trying to run
It’s a shame that snaps are forced to use Canonicals closed source backend because they are really good, and a fully snap system is a very compelling idea for immutable systems
And the wording is fucking terrible as well
I usually to in the developer tools and manually disable the thing preventing the paste action. It’s usually a string to remove some JS or something or an Event that you need to uncheck
Fedora hat and gloves and a half hour and a half hour and a half hour and a half hour and a half hour and a half hour and a
OMG I SHOULD HAVE DONE THAT TO JETBRAINS AND MICROSOFT FOR TEAMS
There’s other reasons to dislike Aral but these ain’t them. My list is more like:
Yes. This 1000x. I hate it at work when I come across code that was written 3 years ago that has literally no traces of why it’s there and a quick summary of what it does. Especially because that code is always the most abbreviated spaghetti you’ve ever seen. People should stop thinking (their) code documents itself because 99.999% of programmers cannot do it right.
I really like the Google way of coding: assume the person reading the code is the most 1337 programmer ever, BUT that this person knows absolutely nothing about the project
You’ve perfectly captured twitter tech bro energy it’s kind of incredible actually
At least that’s actually easy and quick to do and is the only way of doing it. Centering a div however has 81639393 ways and it seems the one that works is different every time
At first I only noticed the indent. Wtf
I think the same, I often find that people overestimate their ability to write self documenting code and with the added mess of automatic formatters it often becomes hard to read and understand. In my department I am one of the few who actually writes comments and readmes that explains the reason behind some decisions. I am very junior, less than a year of experience, so maybe I will be able to better understand code that other people write in the future. But for the time being I write my documentation and my comments in a way that someone who doesn’t know anything about the project can understand, because I hate having to call coworkers because I can’t figure out how the project handles x and y (bear in mind that is also caused by Java “best practices” with 45 abstraction layers)
I’m the total opposite, my documentation is very thorough, my code looks like it was made by a monkey
I wish my handwriting was this good, it still looks the same as when I was in 3rd grade
nvme0n1p1
Poettering and Systemd are amazing and Linux would not be as good as it is today without them. Whether you like it or not, we can’t have a fragmented ecosystem and expect people and companies to adopt it (see the 14 competing standards XKCD). Having one solid base that works the same on every client is like literally the base requirement for making a product for the said client. Systemd, flatpak, xdg-portals, pipewire and immutable distros all solve this.
Wayland gets so many more of the basics so much better than X11 it’s not even funny anymore. X11 is stuttery, unsecure, unmaintaned, can’t really be updated for new features that are pretty important in 2024 (VRR, HDR). For now with my usage, the only big disadvantage I saw from Wayland is that you can’t restart it like X11 when something goes wrong, but that’s the thing, I haven’t had to restart it like I had to often with X11. Even on Nvidia Wayland is better now, except maybe for gaming but that’s Nvidia for you.
Good to know, thanks for the info!
And hitting high memory pressure is really not fun on Linux (on Fedora at least), it simply locks up and slows down to a crawl and does nothing for minutes until the oom killer finally kills the bad program. I’ve kind of solvd this by installing a better oom killer on my laptop, but my desktop was easy: buy 32GB of additional ram for like 90$: problem solved