Diff chapter

[adelevie]

• needs a chapter number
• needs a link to the "next" chapter
• uses empty links to non-existent git and github chapters
• refers to @vzvenyach as the "creator/author/editor" of this book

[tmcw]

diffs make changes to a document obvious and easy for humans to look at.

maybe

diffs make changes to a document easy to understand.

[tmcw]

So awesome - would be interested to hear from @vzvenyach what he's seeing as far as demographics for website visits so far. I don't know for sure, but there might be a majority-windows audience, so using something like diff checker (to avoid the cli & unix tool requirement) might hit a wider audience.

[vdavez]

Current Analytics Data:

Operating System	Browser	Sessions	% New Sessions	New Users	Bounce Rate	Pages / Session	Avg. Session Duration
Windows	Chrome	216	92.13%	199	31.48%	2.31	0:01:17
iOS	Safari (in-app)	175	95.43%	167	41.14%	2.04	0:00:38
Macintosh	Chrome	125	81.60%	102	32.80%	2.9	0:02:10
Android	Chrome	124	86.29%	107	47.58%	2.16	0:01:57
Windows	Firefox	44	93.18%	41	34.09%	2.25	0:02:49
Linux	Firefox	35	54.29%	19	25.71%	6.8	0:07:43
Linux	Chrome	31	80.65%	25	41.94%	3.16	0:03:02
iOS	Safari	25	92.00%	23	40.00%	2.2	0:02:19
Macintosh	Safari	23	95.65%	22	39.13%	2.57	0:00:51
Android	Android Browser	18	100.00%	18	44.44%	1.94	0:00:30
		862	88.17%	760	37.70%	2.52	0:01:46

[adelevie]

@tmcw I think general "codability" of the demos should be handled comprehensively. There was talk of using a JS-simulated terminal where any exercise code could be run. Alternatively, we can say "if you're using a Mac, click the magnifying glass and type 'terminal'" and "if you're using a PC, there is a thing called cygwin ... where are you going? no don't leave! cygwin isn't scary! don't goooo!"