There's double trigger RSUs and so on that allow you to have reasonable tax treatment, due to the theoretical threat of loss if liquidity isn't available. I worked at a company that had this at least while I was there.
In theory they provide market liquidity such that for anyone who REALLY wants to go, at any time prior to and potentially even during the event, there remain some options available for purchase; as opposed to basically spinning the lottery on whether you get to go or not, especially for oversubscribed events.
For Zed specifically? It cuts directly against their stated goal of being fast and resource-light. Moreover, it is not acceptable for software I use to automatically download and run third-party software without asking me.
For node.js in general? The language isn't even considered good in the browser, for which it was invented. It is absolutely insane to then try to turn it into a standalone programming language. There are so many better options available, use one of them! Reusing a crappy tool just because it's what you know is a mark of very poor craftsmanship.
It shouldn't be as tightly integrated into the editor as it is. Zed uses it for a lot of things, including to install various language servers and other things via NPM, which is just nasty.
You might not be old enough to remember how much everyone hated JavaScript initially - just as an in-browser language. Then suddenly it's a standalone programming language too? WTH??
I assume that's where a lot of the hate comes from. Note that's not my opinion, just wondering if that might be why.
JavaScript is actually fine as the warts have been documented. The main issue these days is the billions of tiny packages. So many people/org to trust for every project that uses npm.
The fact that the tiny packages are so popular despite their triviality is, to me, solid evidence that simply documenting the warts does not in fact make everything fine.
And I say this as someone who is generally pro having more small-but-not-tiny packages (say, on the order of a few hundred to a few thousand lines) in the Python ecosystem.
The point is that Zed's developers have chosen to include prettier, which probably transitively includes many other NPM packages.
Node and these NPM packages represent a large increase in attack surface for a relatively small benefit (namely, prettier is included in Zed so that Zed's settings.json is easier to read and edit) which makes me wonder whether Zed's devs care about security at all.
I guess some node.js based tools that are included in Zed (or its language extensions) such as ‘prettier’ don’t behave well in some environments (e.g., they constantly try to write files to /home/$USER even if that’s not your home directory). Things like that create some backlash.
Slow and ram heavy. Zed feels refreshingly snappy compared to vscode even before adding plugins. And why does desktop application need to use interpreted programming languages?
Notionally, opening new banks and/or buying an existing one that lacks current customers is feasible. Presumably once you do that, you could easily plug into FedWire/FedACH/FedNow, which would allow you to process electronic payments on behalf of whomever you choose to bank, as long as you comply with all the KYC/AML and other finance regs. You might not be able to process visa and mastercard, but virtually any of your customers' customers presumably still have financial accounts that are enabled on Fed rails, which will not be as likely to discriminate. Requiring end-customers to initiate payment (push) as opposed to doing pull, would also reduce transaction reversal risk.
I don't really the ultimate purpose of the position taken by either side here, but it does seem to me that there's a path by which both can coexist, even if difficult.
I think GP's point is that you should always seek to apply the law correctly, hopefully setting precedent for its correct application for everyone in the future.
I mean, certainly - if you store both GPS time and derived coordinates from the same sampling, then you can always later interpret it as needed - whether relative to legal or geographical boundaries etc as you might want to interpret in the future.
AIUI the font vendor has a list of customers, each of whom are required to provide an exact list of the domains they will host it on and the domains they will display it on. So the crawlers, upon identifying a matching font, simply have to check that both the displaying and hosting domains match.