Comment by venussnatch
4 days ago
Define resources and create a better limit then. 10 small code-only projects will take orders of magnitude less storage, bandwidth and cpu than one project with committed image and sound assets.
4 days ago
Define resources and create a better limit then. 10 small code-only projects will take orders of magnitude less storage, bandwidth and cpu than one project with committed image and sound assets.
It's a community code forge. If someone poured their heart and soul into making an awesome game with kick-ass image and sound assets, the community probably wants to support it.
Their stance is obvious: if you just want dumb git hosting with a freemium model, use something else.
The resource limit are quite clear: From each according to their ability, to each according to their needs.
And as long as it's hand-made, that's fine.
What is hand made code? Does that mean no auto complete? No linters?
If a carpenter uses a table saw, is he still a carpenter?
What if he just throws wood randomly at the table saw and tries to sell whatever pieces come out?
(Never do this with a table saw, btw. They can, and will if you don't use proper procedures, throw wood sideways at speeds that can punch through walls and impale people)
4 replies →
People downvote this kind of take because you're striking at the heart of the enforcement problem and also the definition of what a project that is majority built with AI really means. What they really want is to ascertain the amount of effort from a human that went into the project and they're using the percentage of code generated by an AI as a proxy metric. But it's a bad proxy, both because it doesn't capture human effort and because it is not measurable.
8 replies →