systemvoltage

Problem with Gitlab is that they will never stop adding features.

Snapshots have an intention behind them as a chunk that the programmer thought of. It has infinite flexibility depending on the programmer/team. IMO they are a necessary feature, but the article considers it a bug. It’s an explicit and deliberate chunking of code writing process which is what you want in a chaotic “collaborative” environment. The system doesn’t get to decide but you decide when to commit.

It's interesting that we are seeing a time when subscriptions are not preferred and usage-based billing is.

Pay-as-you go isn't a common thing in SaaS. For example, except for AWS SES, all email providers are bulk-subscription based.

Any recommendations for a trustworthy registrar?

Interesting. All 3 seems like they’re obviously going to impact quality. e.g, reducing the effort from high to medium.

So then, there must have been an explicit internal guidance/policy that allowed this tradeoff to happen.

Did they fix just the bug or the deeper policy issue?

I am not following the logic. If you’re a hobbyist, sure.

But the argument is if you’re using Vercel for production, you’re paying 5-10x what you’d pay for a VM, with 4gb.

So then what’s the rationale? You can’t be a hobbyist but also “it’s pay time” for production?

What do you do if not AWS?

What changed? 2017 HN would be very different on this take.

No, I can’t find a single article praising wealth concentration.

Not trolling. It has served me better than most heuristics.

If there is something subjective and if you cannot find a critique of it, it’s usually a super power to assume the opposite is true barring obvious exceptions.

[flagged]

It encourages the 80% into group think. Flagging is a signifier that “you should not dare to think that was a good comment. Move on and don’t think for yourself”.

I agree somewhat, you can feel the tension on HN with respect to labor vs capital. Which is funny because the entire premise of YC is to infuse capital and get a huge leverage over bootstrappers.

Chess engines should come with another metric bar: "The twitchy-ness" of the position aka the gradient of primary eval metric as you pareto the possible moves from best to worst. The stronger this gradient, the more risky it is to play, and more changes to make a mistake.