[-] tyler@programming.dev 8 points 2 months ago

If you’re in the U.S. you can use Privacy.com. No need to ever give name, address, or real credit card info ever again. It’s pretty nice.

[-] tyler@programming.dev 8 points 4 months ago
[-] tyler@programming.dev 8 points 4 months ago
[-] tyler@programming.dev 8 points 4 months ago

I’m very confused what the nightmare is here.

[-] tyler@programming.dev 8 points 6 months ago

I’m also a millennial and I was taught how to use a computer so of course I edit my messages.

[-] tyler@programming.dev 8 points 9 months ago

Holy shit. That is terrible.

But it doesn’t really matter how bad it is, if you asked them to do something and they ignored it that’s inexcusable unless it’s illegal or breaking code. Doesn’t matter if you asked them to use a fucking 30” old growth log.

I don’t know what common practice is regarding that adjustable support. We have one similar that’s holding up our entire basement ceiling lol, but it looks like it was built that way with the house. Doesn’t look good but I’m guessing it’s fine.

[-] tyler@programming.dev 8 points 1 year ago* (last edited 1 year ago)

No I’m really tired and I think I backspaced and fished it up. OK I’m leaving that autocorrect cause it’s funny

Edit: updated and fixed to say “it’s way slower than fish”

[-] tyler@programming.dev 8 points 2 years ago

discarding changes does not discard uncommitted new files. The VS Code button did a git clean which is completely unexpected. Git even refers to a git clean with completely different terminology.

git reset -> "Resets the index and working tree. Any changes to tracked files in the working tree since are discarded."

git clean -> "Cleans the working tree by recursively removing files that are not under version control, starting from the current directory.". This command also requires you to specify a force option to actually do something, else it quits with an error.

Note that git clean never once refers to discarding anything, and git reset never refers to removing untracked files. VS Code was doing an idiotic thing. Running git reset --hard AND git clean. There is absolutely no reason to be running git clean from an UI button ever. If you want to remove a file you can explicitly remove it.

Imagine that the button said "Discard all changes" and then it ran rm -rf --no-preserve-root /*. Would that make sense as a button? No. It definitely would not.

[-] tyler@programming.dev 8 points 2 years ago

Maybe equestrian racing. Buy an already trained horse and then it mostly knows what to do. And there’s like 50 plus competitors.

[-] tyler@programming.dev 8 points 2 years ago

Everyone that doesn’t have access to those is using gpus though.

[-] tyler@programming.dev 8 points 2 years ago

That’s lossless…

[-] tyler@programming.dev 8 points 2 years ago

Can’t tell if you’re joking. The first three aren’t even the official docs and the official doc links are to an incredibly old version.

view more: ‹ prev next ›

tyler

0 post score
0 comment score
joined 3 years ago