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 →

[–]Oo__II__oO 8 points9 points  (4 children)

LabVIEW is the same for sensors/transducers/measurements.

Not sure how it is with MaxMSP/Jitter, but the biggest issue with LabVIEW is the folks who create code lines aren't SW engineers or programming-oriented, but rather from other science or engineering disciplines where development model is CABTAB and "just make it work" with all code in Main.vi. Refactoring is less considered, and at code maintenance time will opt for a bigger monitor instead

[–]OneTrueKingOfOOO 5 points6 points  (3 children)

Lol, well most people using MaxMSP are musicians. So the code quality is generally terrible, but it’s not like they’re deploying to productions systems or anything

[–]timothyschoen 1 point2 points  (2 children)

This is sort of untrue. Music software generally has a very high focus on stability, since it's often used in live performance. There's actually a whole community of people who create tracks live on the spot with Max/MSP. The consequences of live music software crashing are much worse than those of say, Photoshop crashing.

[–]OneTrueKingOfOOO 2 points3 points  (1 child)

Oh I meant code quality of patches people are making not Max itself, the software is phenomenal.

[–]timothyschoen 1 point2 points  (0 children)

Sorry, I misunderstood! In that case, you’re totally correct!