@jensGeorgsen The main reason we didn’t use Scratch/Blockly (and we did consider it when I started building the sequence editor years ago) was that the sequence editor is a core part of the application and we need full control over every aspect of it. We did not want to make compromises on this particular part of the application. I have seen some apps that do have Blockly-based plugin systems, but typically, the plugin system is not the core of the application. In the case of the sequence editor it’s a huge feature, if not the biggest feature.
From a risk perspective, this could be a problem for us long term. For example, what happens if the Blockly project makes a long term decision that is in line with their needs, but not the needs of FarmBot? For a feature as important as the sequence editor, we felt it was better to “re-invent the wheel” instead of purchasing a wheel that could change without notice and leave us stranded. We’ve seen this happen to us in the past with other third tools we’ve used, such as early versions of the app that were built with AngularJS v1.
With that being said, what do you like about Blockly and Scratch that you would like to see in the sequence editor?
And to continue what @aronrubin said, we would absolutely love to see a third party tool that users Blockly to control FarmBotJS.