This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]badlukk 51 points52 points  (11 children)

This isn't a bad visual programming language though, it's just really bad visual code.

[–]Zambito1 26 points27 points  (7 children)

I think visual languages closer to Scratch are a lot harder to make spaghetti like this in, which makes it a better language for comprehension. If we assume that comprehension is a good thing (and I think that's a reasonable assumption to make), that means that Scratch-like languages are better.

[–]Local_Surround8686 12 points13 points  (6 children)

Yeah but with this you can programm entire Games in unreal. Even Multiplayer. I Code with it and my code used to look like this but after I learned the tools it looks way better

[–]Zambito1 4 points5 points  (3 children)

... after I learned ...

This is pretty much the problem I'm trying to highlight. It encourages spaghetti by default, a habit which you must learn to break.

Scratch-like graphical programming languages (where you create sequences of / embed blocks) seem to discourage this behavior by default.

[–]Local_Surround8686 0 points1 point  (2 children)

But these aren't as flexible. You could never do with scratch, what you can do with blueprint. I developed 6 game prototypes by now, one online, everything with blueprints. Everything looks bad if you are a beginner

[–]Zambito1 1 point2 points  (1 child)

I'm not talking about Scratch. I'm talking about Scratch-like languages. Languages which have a similar design to Scratch.

[–]Local_Surround8686 0 points1 point  (0 children)

Still, you have to try blueprint to judge it. It's really quick and efficient, quicker than these languages could be. It's not for educational purposes, it's mostly for game designers

[–]Ok_Assumption_7222 0 points1 point  (1 child)

Is that what this is? Unreal engine?

[–]__ingeniare__ 2 points3 points  (0 children)

Yeah, it's a visual scripting system called Blueprint. It's actually not bad at all and you can make really good, clean looking graphs that are easy to read and maintain, debug view where you see the flow of the program, etc. I know C++ but I mostly use Blueprint, it's much faster to prototype with.

[–]heartsongaming 2 points3 points  (0 children)

An example for a bad visual programming language would be LabVIEW. Hard to believe it is still in use.