You make a valid point about usability from the point of view of viewing the slides online. However, it wasn't designed for that, but as a tool by the Go authors to be able to quickly churn out presentations in a simple markup language and run code from within the presentation similar to how play.golang.org works. There's a presentation on that, actually[1]
The assumption is that if you use this software you'll read the instructions and know how to use it. In other words, being able to put it online was an afterthought. Not that this isn't a fixable problem.
TL;DR: historical reasons, designed for different usecase, can be fixed.
The assumption is that if you use this software you'll read the instructions and know how to use it. In other words, being able to put it online was an afterthought. Not that this isn't a fixable problem.
TL;DR: historical reasons, designed for different usecase, can be fixed.
[1] http://talks.golang.org/2012/go-docs.slide#20