Normal_gaussian
Joined 10 years ago
Joined 10 years ago
Raising prices risks churn, reducing free tier risks lowering customer acquisition rate.
> why don't you submit some PRs to help them improve?
Is often a non-starter. If you believe a codebase is poor quality, any changes to improve it have a strong risk of making it worse and/or wasting your own time. In the case that you aren't a key player in said codebase already, it is even more likely your attempts to make changes will fail. Its not impossible to improve these repositories however doing so is quite a different skill-set to identifying their failings.
This is a real problem for acquiring customers. CI/CD / Actions in general has a low initial perceived value and a high perceived value after use while being primarily a commodity product (serverless compute). To acquire customers they need to offer a free tier, to make money they need to charge their heavy users more, but because it is a commodity their heavy users will self-host runners or jump ship.
Action minutes is a really good proxy for value gain from cloud git services, where repo count, user count, file count/size, etc isn't.
Its a fun pricing puzzle.
There's definitely a tradeoff, but IME it's not as drastic as you first think.
Honestly, while I see firecracker replacing docker on the horizon I don't see firecracker replacing v8 isolates for most edge function execution. Firstly, this article's scenario is a bit unusual in that they were using someone else's isolates - so adding on a few hops; secondly isolates running JS/TS can be statically analyzed quite well, and at scale looking historically for issues and exploits, in many edge compute scenarios this is quite desirable. MicroVMs can have an awful lot more flexibility so to get the same benefit you have to really lock down what is available - the trade-offs for mid-size companies seems to benefit isolates. Obviously netlify is more than big enough and relies heavily on this that it leans in their favour.
True. If I invite nobody it about matches the night in.
Nope. Its a bunch of work and stress and thoroughly beaten by a dull night in. If I want to bring people together, I'll pay for it to be done - e.g. a restaurant.
This is often the case for any mass transit vs personal transit option.
As for home -> taxi -> mass transit -> taxi -> destination; you have to have a pretty short journey on the mass transit for it to reliably work out cheaper to do home -> taxi -> destination, which pretty clearly restricts the pool of people that applies to.
> and durable keyboards
It wasn't that long ago they had terrible keyboard lifespans which could be a death knell for the laptop, and overheating CPUs which limited performance way behind spec. They've come far in recent years, and I certainly wouldn't be sad if it was my main machine yet I don't expect them to be an outlier forever.
In some dimension Apple (and any serious manufacturer) is always going to be ahead - and they certainly are in non-gaming portable CPU/GPU combos right now. Alas, they aren't ahead in many other dimensions; my Fedora X1 Carbon is my strong preference over my M4 macbook pro and a large part of that is the basic usability of the system and window manager (sway), which is something Apple will never match until we meaningfully switch interaction paradigms.
Trying to respond to a signal is a nightmare of routing and lifecycle bugs. Never mind the fact that most dependencies won't be registered. Currently file/process signature matching is ok for major runtimes, and tends to fail on specific version detection. This would effectively formalise that.
I could see it being a successful standardisation for major runtimes and many libraries that wouldn't currently be detected - but take up would never be universal. A kind of CVE search stamp.