I am directly addressing the problem of your suggestion. You are saying, “just break it down into smaller pieces and dedicate engineers to it”. I told you all the reasons why they can’t just do that for complex features that offer little value or ROI.
I am not going to chat with someone that engages in a bad faith discussion by pretending the legitimate discussion I am having is just fallacies. You reek of reddit user.
(Edit: Obviously I didn’t care anyways and replied, since I felt like I needed to. I feel bad that you’re feeling attacked, but that is genuinely a perspective issue. Stop assuming people are attacking you.)
Users wanting a feature for a long time doesn’t mean they are entitled to have the feature. Like I said, software engineering is complicated. There could be various features of the platform that would conflict with them adding states between public and private, which doesn’t even including the concept of designing the feature itself, and doesn’t include plans that they may have already to integrate it into the platform, nor the engineering overhead of that feature compared to other, more important features they could be developing. We have to look no farther than Avatar Scaling to see this.
That is totally valid! I do too! Having upload tokens or more public states/user authorization would help for sure.
But, like you are a lead developer in your own right, you should understand that a feature like that would need to account for a LOT of use case factors. It isn’t a matter or just adding a token or changing a bool to an enum. There’s a lot of design, API work, UX, and functionality to be built around it. And then beyond that, the value of that feature in the scope of the whole project. Sometimes stuff just needs to be put on hold.
I agree! Helping people with their projects is a MAJOR PITA, and it’s much easier to just do it for them. But what I WILL say is that if you’re developing a project through VCC, it should be significantly easier than it was before. Especially that you can just backup the project, send it to them, and all they need to do is install the VCC, open the project, login, and press upload (especially if you pre-compile the shaders and what not).
By the way, if you didn’t see:
Edit: I just wanted to re-quote Tupper here. Tupper posted it for a reason. This explains pretty much exactly why VRChat is likely not implementing features or fixing certain bugs. You NEED to watch this video.
And now that I watch that video… I think it kinda makes sense why VRChat set probably 100 or more features/bugs as “tracked”.