But the reality is: Knowledge changes Tools evolve Errors are discovered Better explanations emerge
In software, we accept continuous improvement as normal. In publishing, we still freeze books at “v1.0”.
I’m experimenting with this idea through a platform called Ulomira: authors publish once, and keep improving their book while it stays live.
I’m curious how others here think about this:
Should books be immutable? Or should they evolve like software?
Genuinely interested in feedback from authors and readers.
- New editions of books are released all the time. The immutable record a particular edition of a book is a bedrock-importance feature, not a bug.
I don't want a new platform for books that might change under my feet. That's antitical to the benefits of ownership. I'll take a plain text file over your walled lotus garden any day.
- Continuous updates could be disastrous for how-to books or any kind of technical learning manual. It says one thing today, but something different when I look at it tomorrow? How is one supposed to follow the directions if they’re changing?
Fixed editions are nice because you get the big update all at once; it’s planned for and expected.
- "1984"? what do you mean it was about power changing truth on the go?! It was always about floral arrangements and cookies recopies ;))
- One of the main reasons why books cannot update as software is because there is no GitHub or even Git thing for books crafting.
- When I read an e-book and notice a factual error, I'm unhappy I can't tell the author or publisher about it and expect the e-book to be updated.
- How would the author get paid for updating the book in a way that is better than the current edition based system?