I worked on a project that used yarn from the early days all the way up to v3, it's slow as hell, but it works. They also have the supply chain protections.
Eventually we snapped and migrated to pnpm. Installs (both in CI and on local dev machines) are significantly faster. Turned out to be about a day's work to migrate with an LLM's help.
I don't doubt that 3.x probably has worst perfs (it's almost two years old now), but just to clarify we closely track performances and Yarn and pnpm and pretty much on similar level:
Going to give the benefit of the doubt here. I know what lockup period means.
365day lockup isn’t a universal standard. For example for SpaceX 20% of insider shares can be sold in the first few days. 100% within the first 3 months.
Without a public S-1 filing we don’t know what the lockup for Anthropic will be
the best part is Downdetector is inaccurate as hell - if AWS is genuinely down, folks get curious and search other providers, causing Downdetector to mark them as down too
When you search for a service you get the current status and you get the option to report a problem.
The minimal you expect from such a service is to keep track of how many % of users are searching also reports an error. There might of course still be errors but that alone surely can't be it. But please correct me if I'm wrong.
I don't have any proof but it sounds plausible; they also have an interactive button (does not require any login), so it could be that they rank the interactive event higher, but still count plain views as something. I'd say it's a fair indicator at least on a basic level.
Charging by the hour was one of the worst things for my career (was just starting out). Never realised at the time that I was subconsciously doing a slower job and not trying to make it faster or really improve until I left.
reply