4 ms·
> Unfortunately there are very few general-purpose visual languages This is not surprising, because "general purpose" tools have general, highly-composable, ex
by zozbot234 5y ago
> Unfortunately there are very few general-purpose visual languages
This is not surprising, because "general purpose" tools have general, highly-composable, extensible syntax. Endowing, e.g. condition operators with their own block shape makes sense when all you have is a simple tool like Scratch where they just "snap" inside if-then blocks, but not so much when "boolean" is simply one of many interchangeable types that might, e.g. be assigned to a variable. Then a condition operator is simply some expression-like element that just happens to return a boolean. Similar things happen with other program elements, like text strings, numbers etc. Custom types start to be needed, and then you need to add whatever the equivalent of a DATA DIVISION is in your Scratch-alike.
At the extreme of generalization, you find things like dependently typed languages where even "values" and "types" are no longer separated by rigid syntax, but are the same kind of program element.
- TuringTest 5y agoI don't have a problem with syntax. I have a problem with textual syntax, where abstract concepts are represented with words, with little to no secondary notation[1] and lots of repetition. When the syntax is highly visual, it can convey information through much more bandwidth than flat text, which is limited to a few dozens of repeatedly used symbols. And don't tell me that textual programmers don't realize the benefit of secondary notation and visually-conveyed details. We love when our IDEs full with syntax highlighting for different types of operators, global structure mini-maps and intellisense auto-complete tooltips. All these are visual tools that improve the flow of building a text-based program. [1] https://en.wikipedia.org/wiki/Secondary_notation https://en.wikipedia.org/wiki/Secondary_notation