![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/028151d2-3692-416d-a8eb-9d3d4cc18b41.png)
What if I know it will compile for several minutes so I leave it alone to go office chair jousting? It would be fair to lock up the UI in this case.
What if I know it will compile for several minutes so I leave it alone to go office chair jousting? It would be fair to lock up the UI in this case.
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
You both are wrong! I wrote my own distro with opinionated modifications and it is superior to both of your distros!
Masks don’t only protect from airborne viruses…
Oh, that makes warnings errors and does not mean “ignore errors”. I’m not too familiar with compiler flags. You could do some mental gymnastics to argue that the unused variable causes the compiler to exit and thus the code is not functioning and thus the unused variable is not a warning but an error :^)
I for my part prefer it that way. Makes sure the code stays clean and nobody can just silence the warnings and be done with it. Because why would you accept useless variables that clutter the code in production builds? Imagine coming back after some time and try to understand the code again. At least you have the guarantee the variable is used somehow and not just “hmm, what does this do? … ah, it’s unused”
Unused variable is an error which fails to compile.
And half of them are “curated list of X”
I want to add that Gmail is a bit of a dick when it comes to SMTP.
Hmm, I see. The perfectionist in me would want to shed that processor load though ^^
Without any judgement: why are your servers running X11? Just because you dislike SSH’ing to them?
Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.
Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE
part of your SQL command (or analog statement of the query builder)? No fucking thanks.
Yep, it’s a repost of this one.
One could even think this OP is an alt account.
absolute galaxy brain moment
The stalebot is most times useless. The only scenario where I can see use of it is a maintainer waiting for the reporter to add information. But closing issues because no maintainer checked on them? That’s garbage and discourages bug reports.
Ducking Medium again. No I don’t want an account with you. The article can’t be that interesting.
You forgot the package hollywood.
That’s the garbage in part of the GIGO process.
I’m a sucker for jetbrains Mono when I need a monospaced font. It just looks nice to me.
The XDG default location would be
~/.config/autostart/
. It contains.desktop
files for programs to start automatically.