top | item 35309863

(no title)

corwinstephen | 2 years ago

If I'm being perfectly honest, it never even occurred to me to consider the open source route. I'm not opposed to open source at all--I've done in the past--but one issue could be that I might loose the ability to be highly opinionated about the evolution of the product, and I think in this space where there are already a ton of "do a lot of things halfway decently" products, being opinionated about what Lunette is and is not could be key to its success.

discuss

order

lelanthran|2 years ago

> but one issue could be that I might loose the ability to be highly opinionated about the evolution of the product

I hate to be that person, but you're pitching an app for authors, developed by yourself who is a self-described author, and you're mixing up 'loose' and 'lose' :-(

In any other context, this wouldn't matter, and with actual typos it wouldn't matter, but in this context with this particular word, it does reflect negatively.

> I think in this space where there are already a ton of "do a lot of things halfway decently" products, being opinionated about what Lunette is and is not could be key to its success.

You're quite correct. Having a narrow focus on the goal is better than trying to be all things to all people, otherwise sooner or later you're going to be fielding requests from people who used it to write the business docs and need non-book related features.

I am also doing something similar (am not really an author, made a few hundred dollars with self-published books and short stories a decade ago and then moved on), and I have an even narrower focus than you do.

internetter|2 years ago

How does open source mean loosing any of that? You don't need to accept everyone's stuff, or even anyone's.

andai|2 years ago

I think that's the model SQLite follows. Open source, closed development.