[badsectoracula]

Stripe's website doesn't tell you anything about what exactly it provides though. At best you can infer that they provide some sort of API for accepting payments based on the code snippet they have at the bottom, but beyond that nothing else is there - and even that is something you have to infer.

SourceHut's site tells you what it does, how it does it, what features you can find in there and a bunch of other things. It is packed with information.

[hazz99]

Communicating "information" is not at all important, communicating __value__ is. Stripe does that exceptionally well, and sourcehut does not.

[badsectoracula]

What does that even mean?

When i want to learn about what something is, i want information about what that something is.

[hazz99]

Not necessarily. You don't (well, most people) want to know what a product is, you want to know what it can do for you.

In other words, the value it offers you. How it enables you to achieve what you want to achieve. That's what matters, the technical functionality does not.

I don't care that Nike uses vulcanized rubber and cotton, I care that my friends will think they look cool, and thus make me look cool.

So they focus on communicating that value proposition rather than an info dump about the product.

Sourcehut says "lots of open source mini services that work without JavaScript". Cool, why do I care? Is there a cost saving? Would my devs prefer this? Can it do something other paid services can't? Why should I use it?

This is sales, not engineering.