![]() ![]() Stop “Defending the user for his own sake”… Just like how the modifiers cannot be edited or deleted in the UI, the same should be true for assets that are essential for Blender to function. You know, i was considering as a joke, to write “Just bundle it to the binary or make it a binary blob” but you guys actually considered that? seriously?Īnd “read-only” usually refers to the way the assets are accessed in the Blender UI. So what, would you like me to wait till it will be bloated as the versions go-by, come back and say “I told you so?” for it not to be a fallacy? who will it help.Īs far as the update link to the current on-going project That’s why they are brought up in the first place.Ĭall it a fallacy as you may, i call it : “That’s what i want to hear so i will call it a fallacy” These are issues that are actively worked on. ![]() An argument that this will “open the floodgate to massive bundles” is a slippery slope fallacy. These issues are actually quite solvable. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |