3 ms·
To each their own, but I tried messing with this type of dev a couple years ago on a project using Unreal and Blender. To me it seemed to make easy things hard
by russellbeattie 5y ago
To each their own, but I tried messing with this type of dev a couple years ago on a project using Unreal and Blender. To me it seemed to make easy things hard and hard things nearly impossible, while simultaneously being a nightmare to track changes and undo mistakes.
I assume I'm missing something given its popularity but I personally am in no rush to use this style of development again.
To me, the problem being solved by low code tools should be focused on formatting and syntax. That's what always trips up non devs. They just don't get why capitalization, spacing and special characters always need to be so perfectly placed, with so many arbitrary rules, like functions use commas to separate parameters, but for(), which looks exactly the same, uses semicolons. Why? Reasons. New coders hate it.
TouchDevelop by Microsoft Research really nailed this problem years ago. Turn the commands and variables text into clickable objects so new coders can focus on the logic and program flow - still using "text" like normal coding - but without worrying about the syntax. Too bad it died.
- fsloth 5y ago"I assume I'm missing something given its popularity but I personally am in no rush to use this style of development again." There is a market for solving programming problems in various specific domains without actually programming. Codeless programming has less value if a) you don't have domain knowledge b) you already know how to code. If you a) have domain knowledge and b) don't know how to code then a codeless platform allows one to create models that create added value. Excel, LabView and material editors in various CG packages, Blender included are targeted for domain experts.