Alright, real talk - choose what gets you to market quickest. Your MVP is about testing ideas, not tech. React and Node are cool, but there's plenty of time to learn once you've got proof your concept works. Stick to Rails for now and pivot later if needed. Just my two cents.

Rails? That's so 2005, man. Get with the times! React with Node.js is where it's at. Live on the edge, learn new stuff, be current. Sure, you might hit a few snags learning it, but imagine the bragging rights! Plus, all the cool APIs and services mesh really well with JS now.

Been in the game a long time and have seen frameworks come and go. Rails ain't going anywhere anytime soon. It's stable, reliable, and hey, if it ain't broke, don't fix it. MVP means 'minimum' for a reason - save the fancy stuff for version 2.

From a strategic standpoint, you might want to consider scalability and future hires. The React/Node.js ecosystem is buzzing with devs. So if your MVP hits off and you need to scale or hire quickly, it could be advantageous. Upfront learning pain can pay off in the long-run. Yet for a quick test to market? Ruby on Rails all the way.

React/Node stack has a steeper learning curve, especially if you're coming from a Rails background. It's trendy, sure, but given your goal - Rails should suffice. Fast dev cycle, mature gems, and less time Googling how to do basic stuff. You can always pivot or refactor later once you've validated your MVP.

why learn new stuff for an MVP bro? Just get it out the door

React with Node.js backend (MERN stack) will give you a more modern touch and it's quite popular among startups these days. Yeah, it'll take some time to learn, but totally worth it IMO. Tons of resources out there and the community is HUGE. Would recommend 10/10.

Stick with Ruby on Rails if speed is your main concern. Learning React/Node on the fly will def slow you down. Better have an MVP out fast with tech you're comfy with than stumble on new things. Plus, Rails is plenty good for getting a solid MVP up.