4 ms·
Please, do consider writing the C book as well. Most publishers have beta programs these days (O'Reilly, Manning, Pragmatic Programmers). Don't leave it in a de
by jarpineh 10y ago
Please, do consider writing the C book as well. Most publishers have beta programs these days (O'Reilly, Manning, Pragmatic Programmers). Don't leave it in a desk drawer (so to speak).
Perhaps simplified Redis example could work as a good base to learn C. Single threaded, memory only persistence, network communication service so no complex stuff like concurrency and file management. Though there's probably a lot more going on in there...
Perhaps "Redis for devops" is another book waiting to happen, or how to write Redis modules. By the way, Manning's book (from 2013) is freely available these days:
https://redislabs.com/resources/ebook/ https://redislabs.com/resources/ebook/
- antirez 10y agoYep I don't want to abandon the C book... Since is already halfway and is something more general and long lasting than Redis probably. The book indeed has certain Redis internals examples, but isolated so that you don't need to understand the Redis code base.
- jamiesonbecker 10y agoI would also love to read a C book by @antirez! It'd go up there next to my K&R.* I think a redis book is good, but your docs and blog articles are already excellent. If you combined them into a single document (slightly updated or curated blog articles as chapters, with the second half of the book as reference section/appendix for redis.io commands) then your book is done. You could probably even just hire someone to handle this formatting. The C book sounds really fantastic. * (btw, antirez wrote redis.)