1,850 karma · joined March 1, 2013
Hmm...
2. Support Fish too. Having one language that can generate zsh (macOS default), Fish (power users default), and bash would be really nice!
This seems too simplistic of a description of how money would work in such a world. Money is just a way to distribute your power to influence people. You never pay for machines or software. Think about buying anything, say a pen. You do not really pay for the metal in the pen. You pay the cost associated with extracting and processing the metal by humans along the production chain. If there were no humans along the chain, the cost could go down to zero.
So far, there are no “AIs” being paid.
I also think Saturn's rings don't wobble that fast.
You’d need at least some hash of sources + test results, and check that it matches that (in CI).
And you’d still deal with environment differences.
A. Either it will remain obscure and not see any real use
B. (Less likely) It will get abused to hell before it is shutdown.
Claims of removing violating content “immediately” seem unrealistic under decent usage, unless that $600 can grow unbounded.
Convex does this well, replacing SQL (somewhat yaml-like sucky old declarative language) with JS/TS but in a well-locked-down environment with limits to ensure one mutation or query doesn’t take down the whole DB.
(I know why: for a platform it’s simpler to parse a yaml than to run code, but it’s almost never a good idea for anything that needs to scale in complexity)
UI is constantly inconsistent. You have to keep reloading the page to hope to see what’s up with your MR. Doesn’t help it’s super slow to load.
The backend infra is super unreliable, with actions failing to start, merge trains being stuck, their webhooks being overloaded.
GitLab and Azure are a daily source of pain for us.
Jira is garbage (frontend, backend). Tough but true.
It’s like saying clothing manufacturers are paying the “loom tax” tax when they could have been weaving by hand…
No idea if this feature fixes this.
Edit: Hopefully `gh stack sync` does the rebasing correctly (rebase --onto with the PR A's last commit as base)
PR/MR is an "atomic" change (ideally the smallest change that can be landed separately - smallest makes it easier to review, bisect and revert)
Individual commits (or what "versions" are in Phabricator) are used for the evolution of the PR/MR to achieve that change.
But really I have 2 use cases for the commits:
1. the PR/MR is still too big, so I split it into individual commits (I know they will land together)
2. I keep the history of the evolution of the PR/MR in the commits ("changed foo to bar cause its a better approach")
(the “angry” comments are so tiring)