It’s just a brace on same line/new line stylistic choice with extra steps.
About that, I used to also think that brace on new line is clearer, but after seeing a lot more code I have switched sides, both are clear enough to me, so I’d rather have fewer lines
Finally boolean path effect supports holes!!!
Aaaa, all the nondestructive editing you can do with this omg 🥹
Lol, from the title I thought that 486 models of specific CPUs were going to be affected, that sounded way more impactful
Now that’s my kinda thing!
There is only solace in chaos
Hey no bother at all, I think it’s just because I’m an admin in my instance
live to help you declutter
Me ready to clutter even more 😈
So what was the right shortcut for the screenshot in the end?
It’s just an analysis of the state of things, I’m sure they don’t say that to mean “everything should be done as I like it”, but observing how poor the decisions of a wave of devs have been in regards to licencing, most likely for the simple reason they just go with what feels more open, rather than delving into how and why copyleft is a better safeguard for the good of the entire community
.bashrc greeter? ;-;
Not saying that neofetch going away was a good thing tho
Holy shit, red(hat) spy in the base‼️‼️