SMST (Defiance Daily Target 2x Short MSTR ETF) could be a rough equivalent.
As the other poster mentioned though, many miners won't be using oil-based energy sources, so it does make one wonder about cause and effect. Maybe a dip in BTC would've done it regardless of oil?
Yeah, there's basically nothing explaining why the need more funding, and what they will do with it. Hosting? Salaries? Admin? You'd hope for a bit more context than this.
> How will my gift be used?
> Thunderbird is the leading open source email and productivity app that is free for business and personal use. Your gift helps ensure it stays that way, and supports ongoing development.
Mostly to "technical staff" who work on product and infrastructure. I just don't think the point of the donate page was to be an information warehouse but instead just a dead simple donate page. The other info is googleable if you're looking for it.
People who sell lottery tickets, on average, do better than those who buy them. The same applies to stock options. Which is why "bonus" options are fine, but "buying" them by taking ESOP over potential salary, can be a bad choice.
I think it depends on the ESOP, the companies i've worked at ESOP happened at 10-15% discount of the real price at the buy time and those stocks are instantly sellable. They can be taxed differently yeah but depending on how much you are buying and sell its capital gains tax which can be lower than income tax.
Edit: I am conflating RSUs and stock options never worked somewhere without RSUs so there might be a gap in my experience
Options are a bit riskier than RSUs. If you have RSUs issued at $100 and the stock goes down to $50, then your RSUs are worth half. If you have the option to buy stock at $100 and the stock goes down to $50, then that option is worthless.
I'm kind of getting at the fact that people tend to optimistically overestimate the likelihood of positive outcomes. This is true for lottery tickets, and stock options (every startup is definitely going to the moon).
From the company's perspective, options/equity are great for creating alignment. From an employee perspective, employees need to understand that they are making a bet and have limited control over the outcome of said bet.
I agree with that aspect, but I still think there's a difference. You can't effect the outcome of lotto ticket. To some extent, you can with stock. The incentive probably helps the company more than it helps the individual, but that's the nice part of the feedback again.
The other thing that keeps coming up is the github-code-is-fine-but-the-release-artifact-is-a-trojan issue. It really makes me question if "packages" should even exist in JavaScript, or if we could just be importing standard plain source code from a git repo.
I understand why this doesn't work well with legacy projects, but it's something that the language could strive towards.
> I understand why this doesn't work well with legacy projects, but it's something that the language could strive towards.
Why wouldn't that work well with legacy projects? In fact, the projects I was a part of that I'd call legacy nowadays, was in fact built by copy-and-pasting .js libraries into a "vendor/" directory, and that's how we shipped it as well, this was in the days before Bower (which was the npm of frontend development back in the day), vendoring JS libs was standard practice, before package managers became used in frontend development too.
Not sure why it wouldn't work, JavaScript is a very moldable language, you can make most things work one way or another :)(
Yes - the postinstall hook attack vector goes away. You can do SHA pinning since Git's content addressing means that SHA is the hash of the content. But then your "lockfile" equivalent is just... a list of commit SHAs scattered across import statements in your source? Managing that across a real dependency tree becomes a nightmare.
This is basically what Deno's import maps tried to solve, and what they ended up with looked a lot like a package registry again.
At least npm packages have checksums and a registry that can yank things.
You can just git submodule in the dependencies. Super easy. Also makes it straightforward to develop patches to send upstream from within your project. Or to replace a dependency with a private fork.
In my experience, this works great for libraries internal to an organization (UI components, custom file formats, API type definitions, etc.). I don't see why it wouldn't also work for managing public dependencies.
Plus it's ecosystem-agnostic. Git submodules work just as well for JS as they do for Go, sample data/binary assets, or whatever other dependencies you need to manage.
> But then your "lockfile" equivalent is just... a list of commit SHAs scattered across import statements in your source? Managing that across a real dependency tree becomes a nightmare.
The irony is that this is actually the current best practice to defend against supply chain attacks in the github actions layer. Pin all actions versions to a hash. There's an entire secondary set of dev tools for converting GHA version numbers to hashes
This is where attestation/sigstore comes into play. Github has a first-party action for it and I wish more projects would use it. Regarding javascript specifically, I believe npm has builtin support for sigstore.
The AI bubble feels like it's already starting to burst. Sooner or later the market will see that AI has improved productivity by 20% (or whatever figure) and realise it's much less than the 1000% improvement they've been pricing in.
one of the apps I built is an app that you give it a website, it scrapes it, then places the google ads.
Over time it tries to improve the ads.
Right now it is showing a 5% click through rate over a few weeks. I have no idea if that is good or not, but it saved me the hassle of having to worry about google ads for another app
If the marketing platform works, then it would drive traffic to itself.
As the other poster mentioned though, many miners won't be using oil-based energy sources, so it does make one wonder about cause and effect. Maybe a dip in BTC would've done it regardless of oil?
reply