I agree with @Andrew_Sblendorio.
For building future proofed apps nothing beats well adopted open source tools.
I consider Pd very well adopted. SuperCollider is a niche environment for people willing to invest time in learning its language and mindset.
I was into Max/MSP and Pd before moving to SuperCollider. I’m a programmer and while dataflow languages are nice for audio patching IMO such languages do not scale well for non-audio stuff (persistance, logic, UI). Refactoring in dataflow languages is a nightmare, at least for me coming from a programming background.
Recently, however, as my Ruby port of Grrr has matured I’ve considered Pd as audio backend for Ruby apps with some kind of asynchronous UI approach (there is a lot of work to get there).
As a side note: the SuperCollider language (SCLang) is basically just Ruby with a C-syntax. SCLang compiles classes and is more suited to realtime work, though.
Now, to get back to the original question “How are people using their old grids nowadays?”
A work-in-progress app I’m using is mono-bright even though the device I’m using is vari. This is due to me using Grrr. I’ve found that instead of varying led brightness I’ve had to flash leds (shut them off and then on after a short delay) to provide necessary feedback.
I think mono-bright grids are great. There is even a charm to mono-brightness. I still hook up my monome 40h to a 9 year old MacBook running Snow Leopard from time to time. If I get the time to add vari-brightness support to Grrr I will definitely keep mono-support.