{"action":"opened","issue":{"url":"https://api.github.com/repos/rust-lang/beta.rust-lang.org/issues/404","repository_url":"https://api.github.com/repos/rust-lang/beta.rust-lang.org","labels_url":"https://api.github.com/repos/rust-lang/beta.rust-lang.org/issues/404/labels{/name}","comments_url":"https://api.github.com/repos/rust-lang/beta.rust-lang.org/issues/404/comments","events_url":"https://api.github.com/repos/rust-lang/beta.rust-lang.org/issues/404/events","html_url":"https://github.com/rust-lang/beta.rust-lang.org/issues/404","id":385865213,"node_id":"MDU6SXNzdWUzODU4NjUyMTM=","number":404,"title":"Add back runnable code example","user":{"login":"Ichoran","id":2298644,"node_id":"MDQ6VXNlcjIyOTg2NDQ=","avatar_url":"https://avatars1.githubusercontent.com/u/2298644?v=4","gravatar_id":"","url":"https://api.github.com/users/Ichoran","html_url":"https://github.com/Ichoran","followers_url":"https://api.github.com/users/Ichoran/followers","following_url":"https://api.github.com/users/Ichoran/following{/other_user}","gists_url":"https://api.github.com/users/Ichoran/gists{/gist_id}","starred_url":"https://api.github.com/users/Ichoran/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ichoran/subscriptions","organizations_url":"https://api.github.com/users/Ichoran/orgs","repos_url":"https://api.github.com/users/Ichoran/repos","events_url":"https://api.github.com/users/Ichoran/events{/privacy}","received_events_url":"https://api.github.com/users/Ichoran/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-29T18:21:37Z","updated_at":"2018-11-29T18:21:37Z","closed_at":null,"author_association":"NONE","body":"# Content Feature Request\r\n## Summary\r\n\r\nThe easily-accessible runnable code was a big help to me in deciding that I wanted to use Rust.  It should be restored to the new webpage to appeal to people who prefer getting their hands dirty over having lots of elegant layout.\r\n\r\n## Motivation\r\n\r\nThe Rust web site should appeal to as wide a range of people as possible.  Some people don't believe all the nice-sounding descriptions nearly so much as actual code, and they don't believe the code as much if it's not runnable (e.g. if it's not runnable, maybe there are 100 lines of setup that are elided).  There are a _lot_ of pretty descriptions of things but the content that backs them up is hidden under links.  That's enough to turn certain people _off_.  (Possibly including me.)\r\n\r\nSo, for the people who like to see that it's not all just talk and try things out with zero fuss, put back the runnable code example, either on the front page or at the top of the \"get started\" section.\r\n\r\n## Drawbacks\r\n\r\nRunnable code requires infrastructure that has to be maintained (and looks bad if it goes down), and runnable code samples have a tackier, lower-level look than the rest of the site.\r\n\r\nAdding runnable code therefore might put off or scare more people than it attracts.\r\n\r\n## Rationale and alternatives\r\n\r\nThe rationale is explained under the motivations: to appeal to people who are skeptical of style and are attracted to substance (rather than, e.g., enjoying the style and being happy to dig for substance later).\r\n\r\nAlternatives include links to play.rust-lang.org (but these are less obvious) and a change to include more non-runnable code examples (but these clutter the style more).\r\n\r\nLeaving the site as it is would, in my judgment, render it slightly (more) offputting to a non-negligible class of highly talented individuals.  Everyone's better off if these people can quickly see that Rust is an incredible language, not a mediocre one propped up by incredible marketing.\r\n\r\n## Maintenance\r\n\r\nWhoever maintained the original runnable code example could presumably keep doing so, using whichever methods were used before.\r\n\r\n## Unresolved Questions\r\n\r\nIs it possible to fully demonstrate both a commitment to aesthetic appeal and to rigor in solving serious problems via website design?  I think the Rust community does have both traits, but the website projects the former far more than the latter now (whereas before it projected the latter far more than the former).  Simply adding runnable code doesn't address the entire issue.  Finding a more holistic no-compromise solution would be better.\r\n\r\n\r\n"}}
{"actor":{"display_login":"Ichoran"}}