3 ms·
I think this is the important distinction. These "codeless" tools really just shift the inherent complexities of software development instead of getting rid of
by kickopotomus 9y ago
I think this is the important distinction. These "codeless" tools really just shift the inherent complexities of software development instead of getting rid of them. Anecdotally, I had much harder time learning how to read/understand LabVIEW graphical "code" than I did learning C.
- reificator 9y agoI used Unreal's Shader Blueprints as a positive example, but the more procedural Blueprints used in gameplay boggle my mind. I find them harder to read and much harder to write, and that's when they're well formatted. Another point that I forgot to bring up is that graphical tools don't always let you setup functions, and when they do the added indirection usually makes them even more confusing. It makes it difficult to break out repeated logic and confusing to follow the code after you do break it out.
- DonaldFisk 9y agoLabVIEW isn't a "codeless" tool. It's a programming language. It's very different from C (dataflow instead of imperative) and requires a different way of thinking.
- reificator 9y agoI think they recognize that, which is why they said code in quotes. It's still related to the topic, as that's one of the first places people go when trying to take the code out of programming.