Setting our vision for the 2017 cycle

[cbreeden]

@wycats

For example, we could write a document that helps a Go programmer understand errors in Rust, a Ruby programmer understand traits from the perspective of open classes and refinements, or a Swift programmer understand Option from the perspective of nil and forced unwrapping.

I like these ideas, and also a similar guide mentioned earlier in this thread "If you're used to inheritance, here's what to do in Rust instead" kind of guide. Perhaps my concern with this approach was making such guides accessible. Should we just let these guides appear on the interwebs naturally? Should there be a curated list of guides? What's the story here? And for someone coming from another language, where do they start?