19 lines
1.8 KiB
Plaintext
19 lines
1.8 KiB
Plaintext
|
devRancid said Phillips/Slotted/Hex belong in the trash
|
||
|
Pozidriv is a bit better but most ppl damage it with a Phillips screwdriver because "it looks the same"
|
||
|
Torx is superior to all but very rarely used for some reason,Definitely. First sentence gave it away,Java did the same years before
|
||
|
|
||
|
Fuck auto-generated function references, they're not a replacement for proper hand-written documentation
|
||
|
It achieves the exact opposite: looks like shit and is unusable (no logical grouping, introduction or examples), less devs are willing to spend time because "the magic tool generates everything",What a joke lmao
|
||
|
Ugly ass list of names + generic copy paste description. Not even an argument list or return type unless you click on it,It's truly astonishing how rust fanboys defend a steaming pile of shit
|
||
|
How about you drink less soy milk and use a real language (C/C++), or is your pea brain too small to write bug/vulnerability-free code?,> You can't just "@Steven text me, here's my phone"
|
||
|
|
||
|
You can just "@Steven encrypt your phone number with my public key: .... and post the result here",@cprn there are websites where you only have to copy paste it,You can count the Allman style as a mental disorder as well
|
||
|
Along with tab indentations,Do your statistics exclude all the crypto spam bots?,- "waaaah I only want the library once but the version isn't compatible"
|
||
|
- "waaaah why does it have to install X different versions, so much bloat"
|
||
|
Choose one
|
||
|
|
||
|
This applies to package management everywhere, not only npm,@retoor
|
||
|
Use a GUI (in the editor preferably) for staging specific files/ranges instead of the CLI to avoid going insane
|
||
|
E.g. Ctrl+enter in vscode stages+commits automatically
|
||
|
|
||
|
If you think it's stupid and always stage all, you don't understand git and probably half your commits contain unrelated changes```
|