@dunbar422@j0fdw @OneWholeRhubarb @KMc_head@_Credible_Hulk Equity doesn't usually compound. You have 1 share that stays as 1 share. If you cash out then the share might be worth more cash when you sell than when you bought, but that only applies when you cash out (which apparently billionaires never do).
@alexellisuk@coreh@awakecoding Sure, but if you are in a situation where some tool just doesn't work then a discussion about why that tool is helpful obviously can't be productive.
"Why do people wear bike helmets instead of space suits? You can't wear a bike helmet on the moon."
@thdxr I have been on a "Frontend Tech Debt" team for the last 7 years doing this. It is the best.
It is definitely harder to stay motivated against the surge of slop, though.
Can someone tell the folks at GitHub that this is not a large diff, and I would like it to not be collapsed by default?
It is pretty important to review the code that is being merged, and this "collapsed by default" pattern is not helpful.
@QuantumMentat@ipwanciu Prefixed IDs can also be used to audit that you aren't leaking certain types of auth-bearing info into logs (like a share link that grants access to a resource), since that will have something like "inv_" show up somewhere.
@ccccjjjjeeee Rebasing and squashing are fundamentally different operations that can't be used interchangeably. You can rebase AND squash, or you can rebase and not squash, or can squash and merge, or not squash and merge.
@saltyAom@ljharb The best you can do is to give the user the signal and say "if the signal is aborted then the returned Promise will be ignored, and any resources that are expected to be available may be disposed."