{"action":"created","issue":{"url":"https://api.github.com/repos/mweststrate/mobservable/issues/73","labels_url":"https://api.github.com/repos/mweststrate/mobservable/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/mweststrate/mobservable/issues/73/comments","events_url":"https://api.github.com/repos/mweststrate/mobservable/issues/73/events","html_url":"https://github.com/mweststrate/mobservable/issues/73","id":121970614,"number":73,"title":"Comparative documentation","user":{"login":"kmalakoff","id":756520,"avatar_url":"https://avatars.githubusercontent.com/u/756520?v=3","gravatar_id":"","url":"https://api.github.com/users/kmalakoff","html_url":"https://github.com/kmalakoff","followers_url":"https://api.github.com/users/kmalakoff/followers","following_url":"https://api.github.com/users/kmalakoff/following{/other_user}","gists_url":"https://api.github.com/users/kmalakoff/gists{/gist_id}","starred_url":"https://api.github.com/users/kmalakoff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kmalakoff/subscriptions","organizations_url":"https://api.github.com/users/kmalakoff/orgs","repos_url":"https://api.github.com/users/kmalakoff/repos","events_url":"https://api.github.com/users/kmalakoff/events{/privacy}","received_events_url":"https://api.github.com/users/kmalakoff/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-12-14T04:01:46Z","updated_at":"2015-12-14T15:18:17Z","closed_at":null,"body":"I was thinking that it might be good to use language comparisons (No Classes, ES5 Prototypical Inheritance, ES6 without decorators, ES6 with decorators, TypeScript) in the mobservable documentation. \r\n\r\nHere's what I did on [Knockback](https://kmalakoff.github.io/knockback/tutorial_kb_view_model.html). You see in the top right that you can toggle between CoffeeScript and JavaScript so people familiar with or constrained by one feature set can understand how to achieve a solution using that feature set. \r\n\r\nIt also would have the benefit of demonstrating best practices and recommended solutions to specific problems to help reinforce how to use the mobservable feature set. That would definitely help me!\r\n"},"comment":{"url":"https://api.github.com/repos/mweststrate/mobservable/issues/comments/164463944","html_url":"https://github.com/mweststrate/mobservable/issues/73#issuecomment-164463944","issue_url":"https://api.github.com/repos/mweststrate/mobservable/issues/73","id":164463944,"user":{"login":"kmalakoff","id":756520,"avatar_url":"https://avatars.githubusercontent.com/u/756520?v=3","gravatar_id":"","url":"https://api.github.com/users/kmalakoff","html_url":"https://github.com/kmalakoff","followers_url":"https://api.github.com/users/kmalakoff/followers","following_url":"https://api.github.com/users/kmalakoff/following{/other_user}","gists_url":"https://api.github.com/users/kmalakoff/gists{/gist_id}","starred_url":"https://api.github.com/users/kmalakoff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kmalakoff/subscriptions","organizations_url":"https://api.github.com/users/kmalakoff/orgs","repos_url":"https://api.github.com/users/kmalakoff/repos","events_url":"https://api.github.com/users/kmalakoff/events{/privacy}","received_events_url":"https://api.github.com/users/kmalakoff/received_events","type":"User","site_admin":false},"created_at":"2015-12-14T15:18:17Z","updated_at":"2015-12-14T15:18:17Z","body":"I definitely agree that too many variants is not worth the cost of documenting. I'm only using ES6 with decorators so your proposal would meet my needs.\r\n\r\nThe person who introduced me to mobservable uses the ES5 syntax within an ES6 application because he treats the observable({}) as the basis of a single unified, object-based store instead of getting fancy with classes and decorators. I'm not sure if dropping this usage pattern from the main part of the document would be serve that category of user. I can introduce you if you want to learn more why. \r\n\r\nI do agree that a simpler API with smaller surface area and keeping the document work to a manageable level are a good pragmatic goals!\r\n\r\nStill doesn't exclude a comparative-style of documentation though - no need to do this, just thought I'd draw your attention to this option before you redo the docs since you've been talking about eventually needing to update them.\r\n"}}