In order to focus on community-building features and a smarter editor, we’ve decided to take multi-language support off of our current roadmap. We won’t be adding editor support for other dynamic languages (e.g. Ruby, GO, Python, etc.) in 2017.
We’re not deprecating or removing anything. Your existing Python projects will continue to work.
Transpiled JS/CSS/template-based languages (Coffee, Typescript, Elm, SASS etc.) are still supported.
Why we’re doing this
- We want to focus on community-building features, like profile pages and teams that make coding more social, productive and fun. We’ve seen a lot of interest from educators and hackathon organizers and we want to help them out.
- Having a consistent language allows us to build a more approachable Gomix community for new developers.
- We can make a way better editing experience if we’re opinionated about what we build. This includes better collaboration tools, smarter debugging, and helpful intellisense-like features that tackle the frustrating parts of coding.
- At the rate Gomix is growing, we won’t be able to provide customer support for multiple languages at a quality level we’d be happy with.
Some extra context
In the past, we’ve promised multi-language support because that was our plan. As developers ourselves, a lot of us have other favorite languages as well. What’s changed since then is that we realized that by doing less, we could do more for Gomix’s mission of making real web development enjoyable and accessible to more people.
Today, we have the architecture in place to support arbitrary build environments (i.e. Python). This unofficial support isn’t going away, and we’re totally down with anyone who wants to hack in runtime support for any language.
Hopefully why we’re doing this makes sense now, and please let us know if you have opinions, thoughts, feelings or dreams.