Skip to content

Change RSpec Book link to Amazon #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Change RSpec Book link to Amazon #96

wants to merge 1 commit into from

Conversation

CodingItWrong
Copy link

The PragProg no longer has a link to purchase The RSpec Book, saying it's out of print (even the e-book). Amazon still has copies available for purchase, so that seems like a better link for now.

The PragProg no longer has a link to purchase The RSpec Book, saying it's out of print (even the e-book). Amazon still has copies available for purchase, so that seems like a better link for now.
@JonRowe
Copy link
Member

JonRowe commented Jun 13, 2016

Hi @CodingItWrong, the RSpec book is kinda out dated, so for now we're not going to update this link. Thanks for your input!

@JonRowe JonRowe closed this Jun 13, 2016
@CodingItWrong
Copy link
Author

Think it makes sense to remove the link from the site then? Or better to keep it up, so people will know it's out of print?

@JonRowe
Copy link
Member

JonRowe commented Jun 13, 2016

For now we'll keep it for historical reasons, when something more up-to-date is released we'll reword this to indicate that.

@packtpartner
Copy link

Hi @JonRowe & @myronmarston , Packt has published a book on RSpec which I think could replace the existing book. Do have a look at RSpec Essentials and do let me know if we could feature this book. I think it could prove to be a good learning resource.

@myronmarston
Copy link
Member

Hi @JonRowe & @myronmarston , Packt has published a book on RSpec which I think could replace the existing book. Do have a look at RSpec Essentials and do let me know if we could feature this book. I think it could prove to be a good learning resource.

I'm authoring a book for which we'll have an announcement soon. We'll definitely be featuring it.

@packtpartner
Copy link

That's great news @myronmarston :) Can't we have 2 books listed, yours as well as the one from Packt?

@JonRowe
Copy link
Member

JonRowe commented Jan 23, 2017

Without reviewing it we couldn't really recommend an external authors one.

@packtpartner
Copy link

I agree. I can send you a review copy. Would that work @JonRowe ?

@myronmarston
Copy link
Member

@packtpartner -- I don't see us adding a link, for a couple reasons:

  • As the lead maintainer of RSpec, a book co-authored by me has "official" endorsement status that no other book has. If I truly felt that another book was as good as my own, I might consider, but bear in mind that I'm literally the world's leading expert on RSpec (by virtue of having worked on it for so long).
  • There are other books that cover RSpec. I don't really want to go down the path of us linking to/endorsing them all.
  • Personally, I've invested literally thousands of hours in maintaining RSpec, all w/o receiving compensation. Now I've invested literally hundreds (or perhaps thousands; I've not kept track) of hours in co-authoring a top-notch book. This book is my chance to earn some compensation from all the time I've spent on RSpec and the book. I plan to use the tools at my disposal to promote my book when it becomes available. The RSpec website is one of the main tools I have to promote my own book. I don't plan to use those tools to promote someone else's book. That may sound selfish, but I think it's reasonable. Our books are, in some sense, competitors in this space, and I'm under no obligation to promote yours as en equal to mine.

@xaviershay
Copy link
Member

Agree with @myronmarston here

@packtpartner
Copy link

Thanks for pointing out a few details. Wish you the best for your new book @myronmarston

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants