"c++ is hard, let's use blueprints."
The blueprint: 🙃
"c++ is hard, let's use blueprints."
The blueprint: 🙃
@djlink oh wow, I recognize that. The graph on the left is our microservice API dependency map and the graph on the right is the wiring diagram for one of our distribution switch racks.
Honestly it's easier to keep the former in your head and map the latter by wiggling the cable you're interested in.
@djlink there’s pushing the limits of what Blueprints can do, and then there’s the admission that this complexity is likely better served with C++
These are the latter
@djlink Complexity is a fact of large software systems that do a lot of things - which is what customers demand. While C++ has many warts, you cannot make a significant difference is the blueprint problem with a different language as the language isn't the source of the problem, it is the complexity of the features that is the source.
What I wanted: 2D Platformer implementation
What I got: Sentient neural network.
The implementation in c++,
…
The designer didn’t know c++, none of the work happened because all the programmers were busy.
@djlink If there's one thing I've learned about UI, it's that there's a sort of induced demand phenomenon for quality of life features. The more accessible something gets, the less skilled people try to use it (good for them!), and the more mess they make.
In Unity, which now has its own visual scripting tool but used not to, there was the notorious GetComponent() function, which streamlines initialization... so a lot of people used it every frame (and killed performance).