I disagree. I think a lot of folks have / are going to turn away from NR when faced with Dash 2.
Its interesting to see so many echo my findings from a year ago (I started rebuilding my dash 1 website in dash 2 on March 24th 2024 - a year later and I'm not even close to having parity).
If I had to start with dash2 out the gate, I am quite sure my site would not have been built or ended up where it is today.
This well states what I have been struggling to describe. Dash2 raises the no code/low code bar into programmer / programming experience required territory.
It seems to put it on the same level as UIBUILDER.
I never felt the need to retain a programmer on staff till I got to working with Dash2.
I've put my 'responsive' bugs and glitches on the github, but it's hard to put a ticket in for the impressions and experiences shared in this thread.
I guess I just want to say @craigcurtin its not just you, there are quite a few that feel this way, so be encouraged to just keep picking up the mouse and whacking at dash2, you are not alone.
For 'migration' from dash 1 to dash 2, I just have this critical (for my site) tip.
Be aware that dash2 'leaks' ALL the msg.xxxx data to the browser. You can end up sending a LOT of crud over the wire that you never intended.
Clean up your msg payloads BEFORE sending it to a dash2 node.
