3 ms·

> Otherwise one can access it on Github, but it's not very convenient How come? > I couldn't find "6.2.1. Is WeakMap Strictly Worse than Map" anywhere on your

> Otherwise one can access it on Github, but it's not very convenient How come? > I couldn't find "6.2.1. Is WeakMap Strictly Worse than Map" anywhere on your Github, other than in the screenshot. Maybe that's because that heading belongs in an old revision of a previous book of mine, but in any case, here you go: https://github.com/mjavascript/practical-modern-javascript/blob/371a52b3e4662210b006e5f08be2c750c1d970a3/ch05.asciidoc#is-weakmap-a-worse-map https://github.com/mjavascript/practical-modern-javascript/b... > [Twitter perms] Twitter didn't offer any permissions granularity last time I checked, so that's just what they always request. You don't need to go through my website, just go to GitHub, purchase the book, or ignore my content.

duopixel 8y ago
Feedback: very interested on the topic of your book, but seeing the marketing tactics and your response to criticism seriously put me off. I’d rather support more agreeable authors. Content ignored indeed.
- bevacqua 8y ago
  :wave:
anonytrary 8y ago
> How come [the Github version is not convenient]? You went through the trouble to create a "free" HTML version of it, so you already know the answer to that question. In any case, thanks for the link and thanks for posting your book to Github. Regarding the Twitter permissions, the last time you checked was too long ago. You are asking for read and write permissions when you only need read[0] permissions. Forcing people to market it on Twitter gives me the impression you aren't confident that people will share your book organically. Maybe you should just make the HTML version free like you said you would. You might even have more success in making people pay for the HTML version, compared to lying about it being free. I'm sure people would pay to read a beautified copy of the book, if it's any good. [0] https://developer.twitter.com/en/docs/basics/authentication/overview/application-permission-model.html https://developer.twitter.com/en/docs/basics/authentication/...
- deleted 8y ago
  [deleted]
- bevacqua 8y ago
  > You went through the trouble to create a "free" HTML version of it, so you already know the answer to that question. In any case, thanks for the link and thanks for posting your book to Github. The GitHub experience was worse back when I implemented the HTML version on my own site, because they weren't rendering AsciiDoc back then. Regardless, I implemented it because it was fun to integrate all the things (O'Reilly Atlas, GitHub, Twitter, and my site's automation processes) and as a way to centralize all if my content on my site.

duopixel 8y ago

Feedback: very interested on the topic of your book, but seeing the marketing tactics and your response to criticism seriously put me off. I’d rather support more agreeable authors. Content ignored indeed.

bevacqua 8y ago
:wave:

anonytrary 8y ago

> How come [the Github version is not convenient]? You went through the trouble to create a "free" HTML version of it, so you already know the answer to that question. In any case, thanks for the link and thanks for posting your book to Github. Regarding the Twitter permissions, the last time you checked was too long ago. You are asking for read and write permissions when you only need read[0] permissions. Forcing people to market it on Twitter gives me the impression you aren't confident that people will share your book organically. Maybe you should just make the HTML version free like you said you would. You might even have more success in making people pay for the HTML version, compared to lying about it being free. I'm sure people would pay to read a beautified copy of the book, if it's any good. [0] https://developer.twitter.com/en/docs/basics/authentication/overview/application-permission-model.html https://developer.twitter.com/en/docs/basics/authentication/...

deleted 8y ago
[deleted]
bevacqua 8y ago
> You went through the trouble to create a "free" HTML version of it, so you already know the answer to that question. In any case, thanks for the link and thanks for posting your book to Github. The GitHub experience was worse back when I implemented the HTML version on my own site, because they weren't rendering AsciiDoc back then. Regardless, I implemented it because it was fun to integrate all the things (O'Reilly Atlas, GitHub, Twitter, and my site's automation processes) and as a way to centralize all if my content on my site.