[quote] Or it’s called being-a-great-developer-and-living-near-HQ.
Makes me sad. [/quote]
Seranok and I live in Illinois during the year. Last year we had an intern come out all the way from New York.
[quote] Or it’s called being-a-great-developer-and-living-near-HQ.
Makes me sad. [/quote]
Seranok and I live in Illinois during the year. Last year we had an intern come out all the way from New York.
People would probably do trivial and tiny changes, yes, but changes about things that have bothered them and a lot of other users forever. These things, although trivial and tiny, can often improve software more than major updates that require a lot more work.
Just think about the number of things that are probably easy to fix and that make your ROBLOX experience significantly worse but that ROBLOX hasn’t ever fixed yet and will probably never fix.
[quote] I see two huge things wrong with this.
Obviously security, as mentioned before. And the fact that you’re asking a corporation to give away one of their only selling points for others to copy/steal/use for themselves, etc. [/quote]
Releasing the source code of a program isn’t the same as allowing people to copy it, steal it and use it for themselves. If they release the source and another company makes a clone of ROBLOX using it, they’re doing it illegally. Releasing content to the public doesn’t make copyright laws any less valid.
“probably do trivial and tiny changes, yes, but changes about things that have bothered them and a lot of other users forever.”
Such fixes would still take pretty much the same amount of Roblox developer time even if non-developers were doing the coding. The reason a lot of those “trivial any tiny changes” haven’t been made isn’t because they’re hard to code, but because we don’t have the time in the roadmap to do all of the testing / debugging / deployment on those changes.
It’s easy for you to claim something is a “simple change” and that it doesn’t need much debugging, but in reality a lot of “trivial changes” can actually have real effects that need to be caught with testing. For a recent example take the Cloning + Archivable change. That problem was the result of a fairly simple change to how Cloning was done, and the developers making the change did not anticipate the Archivable breakage that was linked to it in an obscure way.