Leaderboard

There are two broad categories of objects/classes: Values (e.g. numbers, strings, URLs, timestamps, images*, tuples/collections of these) Identities/entities (e.g. file, physical I/O channel, physical device, database, GUI control/indicator/window, state machine) Conceptually, values can be copied but identities cannot. (To illustrate what I mean: Branching a string wire can create a new copy of the string, but branching a DAQmx Channel wire cannot create a new channel) I would use references as a last resort for "value objects", but as a near-first resort for "identity objects". *IMAQ images are by-reference, but they didn't strictly have to be. Genuinely curious: Why do you expect reference-heavy G code to be less performant?

NextLabVIEWStand confirmed!

I don't blame the language. C# is just a front end for .Net (like VB.net et. al.) It's the .Net I blame and have always blamed and I don't care what language you put in front of it including LabVIEW - It will be worse. But there is more to this than a language choice. It is quite clear than NI have jumped in with both feet onto the Windows 10 platform which, don't forget, is attempting to corner all hardware platforms with one OS. There is some sense in that since Win 10 has JIT compilation of .NET (perfect for VI piecemeal compilation) , a background torrent system (push deployment and updates whether you like it or not) and plenty of ways to get data for mining and DRM enforcement (Customer Improvement Programs). This is the start of Software As a Service for NI so you won't need LabVIEW in its old form.