Live data from Hacker News

Write libraries instead of services, where possible

catern.com

11–20 of 328 posts

Re: Write libraries instead of services, where possible

#11
>People say, "services are easy because you can upgrade them centrally, so you can avoid slow-to-upgrade users making everyone's lives worse."

> But this assumes that slow-to-upgrade users can have negative effects on everyone else.

Is the above a reference to Moxie Marlinspike's comments[1]?

So would a concrete example of your abstract essay be that communication should be a client utility that uses an XMPP library[2] instead of Signal's services?

[1] https://signal.org/blog/the-ecosystem-is-moving/

[2] https://xmpp.org/software/libraries.html

Re: Write libraries instead of services, where possible

#12
post #2

I like the approach and it seems to be definitely better for everyone, but how you monetize a library?

Back in the days, RogueWave had a pretty solid customer base selling portable C++ standard libraries.

I worked at 2 different companies and they both quite heavily depended on RogueWave STL.

Re: Write libraries instead of services, where possible

#13
post #2

I like the approach and it seems to be definitely better for everyone, but how you monetize a library?

Does everything have to be about money? This is "Hacker" News, not "Monetize Everything" News.

I think you’re reading too far. The comment doesn’t imply that everything it’s about money. It’s only a question about monetizing a library.

Re: Write libraries instead of services, where possible

#14
post #9

Earlier quoted context omitted.

Does everything have to be about money? This is "Hacker" News, not "Monetize Everything" News.

How are we to survive then

by switching from a competitive money driven world to a cooperative one.

Re: Write libraries instead of services, where possible

#15
post #3

Earlier quoted context omitted.

You can sell a library just as well as any other piece of software I think.

Stealing a library is easier than stealing a service.

Yes. I suppose it’s the same with installable software. But it sells anyway.

Re: Write libraries instead of services, where possible

#17
post #2

I like the approach and it seems to be definitely better for everyone, but how you monetize a library?

You may take a look at Fluence's ideas on that https://fluence.network

It basically allows you to share your code to others in exchange for a fee. If someone builds an app or service that uses your library, and it is paid within Fluence, you will receive a fee. This works transitively.

Re: Write libraries instead of services, where possible

#19
post #2

I like the approach and it seems to be definitely better for everyone, but how you monetize a library?

Does everything have to be about money? This is "Hacker" News, not "Monetize Everything" News.

Certainly not, but it's worth thinking about how developers will get paid to create and maintain useful systems.

Re: Write libraries instead of services, where possible

#20
> A service has constant administration costs which are paid by the service provider. A properly designed library instead moves these costs to the users of the library.

I agree with the articles point, but this introduction, right there, is why it's not happening. SaaS turns your startup into a unicorn and yourself into a rich person. Or at least that's what you are hoping/aiming for. A library is not going to make you a billionaire. Sad but reality.

Post reply on HN