Murkle (Michael Elstone) said:
I do like the idea of visual scripting rather than dealing with a bunch of lines, but I'd like to get some opinions for those who know about both.
In my personal opinion, visual scripting is awesome, but bolt is not. We used bolt for a while at work, and it pretty much does so much wrong in terms of what makes a visual scripting language great so use, that we decided to drop it again in favour of plain programming. There's a lot to say about that, but I'll just give you a few examples:
Almost all “pins” for values in bolt are of type “object”, meaning you don't get any meaningful suggestions of what other nodes to connect there, so its really like programming in a weakly-types language.
When creating a node, luqid had that great idea of implementing a fuzzy-finding which in practice is just plain stupid (if you type “transform”, it will find TryAndSetF… just because it contains the letters of transform in the right order).
Bolt handles (serializable) member-variables very poorly, instead of giving you the same interface as if you made the variable in C#, you get the name, type and value on each instance that you try to edit the variable. For object-types, it will simply not be able to even remember the correct type and you have to set it manually…
The list goes on, and maybe if you don't know C# and Unity too much yet some of it won't even make sense. The point is just that bolt is IMHO after all a poorly designed visual language. Bolt 2 looked promising but Unity killed it in favour of some new custom-solution. Unfortunately there doesn't seem to be a good visual alternative, so if you use Unity I'd recommend learning C#.
