Write libraries instead of services, where possible
1–10 of 328 posts
Re: Write libraries instead of services, where possible
#2I like the approach and it seems to be definitely better for everyone, but how you monetize a library?
Re: Write libraries instead of services, where possible
#3I like the approach and it seems to be definitely better for everyone, but how you monetize a library?
You can sell a library just as well as any other piece of software I think.
Re: Write libraries instead of services, where possible
#4I like the approach and it seems to be definitely better for everyone, but how you monetize a library?
You can sell a library just as well as any other piece of software I think.
Not really. Your market is different. Instead of selling to business managers seeking to solve a problem, you're selling to developers. Developers tend to like solving problems themselves, and you're competing versus free.
Re: Write libraries instead of services, where possible
#5I 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.
Re: Write libraries instead of services, where possible
#6Earlier quoted context omitted.
You can sell a library just as well as any other piece of software I think.
Not really. Your market is different. Instead of selling to business managers seeking to solve a problem, you're selling to developers. Developers tend to like solving problems themselves, and you're competing versus free.
The definition being used here for libraries and services has both being marketed to developers. We're talking about APIs, not a web product with a UI etc.
Services, in this article, doesn't refer to things that can only be built as services (e.g. because it queries a proprietary dataset) but those that might optionally be built as services (e.g. fetching and processing otherwise accessible data) and could, as easily, be built as a library.
Re: Write libraries instead of services, where possible
#7I like the approach and it seems to be definitely better for everyone, but how you monetize a library?
Sell a license. I can't think of a better example off the top of my head, but here's a case study:
CKEditor has multiple commercial licensing plans: https://ckeditor.com/pricing/
Re: Write libraries instead of services, where possible
#8Earlier quoted context omitted.
You can sell a library just as well as any other piece of software I think.
Not really. Your market is different. Instead of selling to business managers seeking to solve a problem, you're selling to developers. Developers tend to like solving problems themselves, and you're competing versus free.
There's an ecosystem of paid libraries and tools around Java and C#. While developers might like to solve problems of their own, standards compliance is one place that they likely wouldn't want to tread their own path if they can help it. They've got work to do, and deadlines.