{"action":"created","issue":{"url":"https://api.github.com/repos/bhauman/devcards/issues/32","labels_url":"https://api.github.com/repos/bhauman/devcards/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/bhauman/devcards/issues/32/comments","events_url":"https://api.github.com/repos/bhauman/devcards/issues/32/events","html_url":"https://github.com/bhauman/devcards/issues/32","id":102558187,"number":32,"title":"README: Start with a brief 'why' paragraph","user":{"login":"jakubholynet","id":624958,"avatar_url":"https://avatars.githubusercontent.com/u/624958?v=3","gravatar_id":"","url":"https://api.github.com/users/jakubholynet","html_url":"https://github.com/jakubholynet","followers_url":"https://api.github.com/users/jakubholynet/followers","following_url":"https://api.github.com/users/jakubholynet/following{/other_user}","gists_url":"https://api.github.com/users/jakubholynet/gists{/gist_id}","starred_url":"https://api.github.com/users/jakubholynet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakubholynet/subscriptions","organizations_url":"https://api.github.com/users/jakubholynet/orgs","repos_url":"https://api.github.com/users/jakubholynet/repos","events_url":"https://api.github.com/users/jakubholynet/events{/privacy}","received_events_url":"https://api.github.com/users/jakubholynet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-08-22T18:40:40Z","updated_at":"2015-08-22T18:45:34Z","closed_at":null,"body":"Hi! I have already looked at devcards for the 2nd time and I still fail to understand its value proposition (no, I am likely not in my brightest state :)). Why and when would I use it? What does it give me that figwheel does not?\r\n\r\nI think it would really help to start the README not with the \"what\" of Devcards (\"interactive visual REPL\") but its \"why\" (and the use case for it, i.e. when). What problem is it solving? The current start is:\r\n\r\n> Devcards aims to provide ClojureScript developers with an interactive visual REPL. Devcards makes it simple to interactively surface code examples that have a visual aspect into a browser interface.\r\n\r\nWhat is an \"interactive visual REPL\"? How does it differ from having figwheel connected to the browser and trying my (visual) Om components (interactively) as I develop them?\r\n\r\nGood luck!"},"comment":{"url":"https://api.github.com/repos/bhauman/devcards/issues/comments/133739490","html_url":"https://github.com/bhauman/devcards/issues/32#issuecomment-133739490","issue_url":"https://api.github.com/repos/bhauman/devcards/issues/32","id":133739490,"user":{"login":"jakubholynet","id":624958,"avatar_url":"https://avatars.githubusercontent.com/u/624958?v=3","gravatar_id":"","url":"https://api.github.com/users/jakubholynet","html_url":"https://github.com/jakubholynet","followers_url":"https://api.github.com/users/jakubholynet/followers","following_url":"https://api.github.com/users/jakubholynet/following{/other_user}","gists_url":"https://api.github.com/users/jakubholynet/gists{/gist_id}","starred_url":"https://api.github.com/users/jakubholynet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakubholynet/subscriptions","organizations_url":"https://api.github.com/users/jakubholynet/orgs","repos_url":"https://api.github.com/users/jakubholynet/repos","events_url":"https://api.github.com/users/jakubholynet/events{/privacy}","received_events_url":"https://api.github.com/users/jakubholynet/received_events","type":"User","site_admin":false},"created_at":"2015-08-22T18:45:33Z","updated_at":"2015-08-22T18:45:33Z","body":"Is it the case that devcards not only displays a React component but also makes it possible to change its props and observe the current state and props (just like React Dev Tools can do for normal react components (though they don't support changing them?) and also rewind to previous setting to observe how it changed over time? Is that the main feature? So is the \"why\" a better visibility into the current state + increased interactivity through history replay?"}}