These days, if you want to get on Amazon, you need to be with a major publisher. If it were a work of fiction I'd say sure, self-publish, and let it coast on buzz. Having had experience with publishers, I can categorically state that going with a major publisher is not just about distribution of paper books: how often and how recently a tech is published in books is directly related to the perception of the relevance of that technology.
So an Apache Flex book is more than just a reference manual: this book needs to be a statement to the world that Flex isn't dead, that it is still very much alive and kicking, to show all the doubters that they were wrong, and that the move to Apache was a step forward, not backwards. And for that we need the reputation, the reach and the distribution of a major publisher. So self-publishing is self-defeating to that purpose, because it says to the world that Flex is no longer prime time, which is not the message we should be sending. I have a list of publishers and an excellent agent who knows everyone who's everyone in tech publishing. I'll find a publisher who's willing to do this. And with everyone's help, it will be a huge success for the community and for the publisher. _______________________________________________________________________ Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca Author, Professional Flex 3 :: http://tinyurl.com/proflex3book Justin Mclean wrote: > Hi, > >> Well, I just heard back from O'Reilly. And unfortunately they're not >> interested >> in publishing an Apache Flex book of any kind > > While it would of been nice to have them as a publisher (print book, > distribution, marketing etc etc) do we actually need a publisher? > > In this day and age it's easy enough to publish ebooks. > > Thanks, > Justin
