I get the idea but I'm not sure if I want to spend the time to fill in the gaps and start an experiment
But I agree with the idea in general: Using informal DSLs as an intermediate language.
I'm not sure, though, if this approach (reduced syntax) is the right one.
This idea of using an intermediate step, where you write non-functional code, just seems like an extra hoop to jump through.
And when you’re ready to progress towards a production-ready solution, you’re looking at upgrading existing code, rather than transcribing or translating this other sketch code stuff.
Idk. If it works for you then it works, but for me, this seems like more work than it’s worth.
As most of us here can see, for many tasks now you don't really need to worry that you have the exact right syntax. I think you still need expert precision when it matters immensely, but we all develop tools, scripts, layers and the like that manual precision isn't necessary.
Immediately felt like one of those disposable framework ideas.
> Sketch can be implemented in any programming language...
... as long as it is react.js?
That said, I feel like this is learning something like CoffeeScript. You have to learn all this language specific syntax (though simplified), why not just learn the language itself at that point?
That's why I just maybe it still needs more time before seeking wider feedback: It's not just one example in react.js, it's basically all of the supporting arguments being based on react, with all of the examples in react.js.
Maybe they have a point, but right now the only support they for this proposal is react.js. A few examples showing the output in a few languages would help, which is why I say this needs more time to bake.