In addition to being super useful...first unique design I've seen in a long time.
Report
What an amazing concept!
Report
Removing a barrier to entry is only beneficial when a learning opportunity is present.
If I really want to develop an application that does exactly what it should efficiently (super DRY) then, I'm not going to start with gomix.
If I want to learn how other previously built apps work with others who have a deep understanding of them then, gomix is a good option.
To jump into say, a Python Flask project on gomix with, absolutely no knowledge of computer science or programming fundamentals is actually pointless so,
gomix should most certainly encourage it's users to learn the languages that support each mix otherwise,
users are ferociously pointing and clicking on stuff with no knowledge of how asynchronous patterns are required or, how certain things must be declared.
The best mix to encounter then is one with great comments- perhaps comments that guide the mixer along allowing them to slowly unravel how the app is actually working otherwise,
Someone is going to get boggled down in point-and-click-ville and be likely "changing" source code in a way that is not standard.
Because programming is a standardized practice that must follow specific patterns to be deemed efficient and DRY, gomix needs to promote efficiency and the DRY principles from within otherwise,
People are actually getting stupid as they play around with source clueless as to whether they are following best practice (if they aren't then they are potentially learning nothing in the mix).
To allow me to clone a github project into gomix is to bring in all the standards of that repo and all the hard work that someone put into holding to a standard of efficiency and DRYness so,
To let people just grab a finished project and not play with it within this standard is unproductive.
Before someone uses gomix they need to be surveyed: Have you written code before? What code have your written?
The survey results before using gomix should be applied to their mixing experience so that they actually have a chance via links to Python & Flask docs to really understand what they are doing when they "change" "anything"...
As a learning platform gomix makes sense to me- but this does not seem to be clearly communicated.
I see this as a glorified Codepen.io that supports a full-stack app as opposed to only front-end programming and, this is needed no doubt but, the execution is important if someone actually wants to not just "play" with "changing" source as opposed to completing their mixing experience having learned how to change the app within the standards I previously mentioned.
I built the bot of my dreams and now we're married. No, seriously, a very good app with a potential to become an easier and more accessible tool for software engineers. Nice job, @anildash.
Braavo
Symphony
Lil' Trump