Yes. This is Roblox’s standard excuse for not including Rojo. And that’s ok. Your pain point is valid.
I do want to address why this is not a valid reason to not include rojo.
First of all, rojo is one button. So you can ignore it if it’s not necessary to you. Second of all, Roblox Studio has horrible UX. This is secondary to Rojo.
However, we are not new users. We each have 10+ years of experience in Roblox. Adding this feature does not improve the UX for new users. This is ok. We’re saying we, as people who are making 90% of Roblox’s money, need this feature.
Once Roblox integrates rojo, it can start teaching new uses how to use it. But until then, there is a MASSIVE jump in complexity—and it makes it harder to hire you to work at Adopt Me or another Roblox game studio.
This feature is not for you right now. That is ok. Roblox should provide a way to teach you how to use rojo.
So once again, Rojo just syncs files into studio. This is not a requirement for making a Roblox game, and will never be. But it is a requirement of large scale teams making top games on Roblox.
New users will probably get little to no value out of rojo integration. This doesn’t matter! Top developers will get massive value out of rojo integration.
Furthermore, If Roblox does not integrate rojo, in 3 years when you need this feature set, it will be much harder for you to learn how to do what top developers are doing.
New user experience matters, but this feature request is NOT for that. It’s for top developers experience.