LabVIEW
Change properties of a cluster element withing an array of clusters
Solved!
You're funny. 
It may be a flaw, but its pretty inbuilt that LabVIEW uses Front Panels for double-duty as a debug UI for the developer of subVIs, in addition to the actual Operator UI. And even on the Operator UI, one is sometimes presenting a scrollable indicator of very large numbers of elements; a log with tens of thousands of entries, say. Things like the Tree control or Table control, which are part-way towards what you want, have great difficulty handling that many elements.
This thread is already spiraling into oblivion. Your experience with NI products make your opinion what they are, but had you chosen any other language you would have things to complain about. LabVIEW is not without faults, and we can have a real discussion about the things you find difficult about it, but the method of which you are expressing your opinion, is very put-off-ish and in the end will not accomplish anything. As gently as I can, here is my response to some of your points.
Just because it is a Windows environment, does not mean you can eat up as much resources as you want. Memory is not free, it is limited, and at some point a user will hit some memory limit and wish LabVIEW was more efficient. One way to avoid this is to not have separate properties for each element in the array.
UI's often have arrays with large number if elements and that doesn't make it bad UI design. That's like saying that other applications should not contain large amounts of numeric data in a list. That is exactly what Excel is. It isn't always bad UI design, or flawed.
Any language has strength's and weaknesses. A LabVIEW strength is rapid prototype, and centers around DAQ systems. A weakness is UI design. No one complains that it takes literally seconds to take a DAQ reading, but many complain about UI design issues. As a result we have come up with work arounds for UI desing issues, until NI makes better solutions. If you have a complaint or want improvements, NI has made the Idea Exchange board. Something Other companies don't have for their products. If enough people have the same issue with a product, NI addresses it.
Claiming LabVIEW is only for technicians is laughable. Would you call what SpaceX is doing not real programming? This is generally the first example but far from the last. Massive large scale distributed systems have been deployed with LabVIEW and TestStand with great success in much less time than it would take with other tools. Your inability to use a tool, doesn't invalidate the tools ability.
EDIT: Thanks for linking to that array cluster table, that was one of them I was thinking of.
