Why are we even arguin about this?
Ease of use can be improved without sacrificing all the speed. Why do we need to bring up nonsense like “It’s supposed to be hard” all the time? You don’t need to be dumb to enjoy ease of use, either. Thats elitist nonsense. “As difficult as necessary. As easy as possible.” Ballance!!!
If we don’t think about how to solve the problem but whether it’s a problem in the first place we are getting nowhere.
We could be arguing about ways to make things more consistent, more easy to use while keeping speed. Instead we argua about whether Blender is a car, or if Blender can only be fast and effieienct if it’s hard to learn without any way to improve it after 2.79.
Artists have different needs.
Blender is for everybody - professionals who value speed as well as newcomers who value their time to learn a program that is able to communicate how it wants to be used without any secrets you just “have to know”.
We do not need to sacrifice all of the speed and we don’t want to dumb anything down, either.
We want a maximized ballance between both. That means consistency, intuitive UI approach and actual attention to the areas that are still sore.
Again - these include usability as well as speed. It’s neither “Blender: The fastest software on the planet at any cost.” nor “Blender - the easiest software at any cost.”
So why should the experience of learning the software not improve, then?
(edit) Also even calling it “learning sacrifice” … I don’t even like the sound of calling learning a “sacrifice”. Learning can and should be fun. For a software good and consistent UX is part of it.
I don’t understand that. 3DsMAX have a shit of UX, same for Maya, Zbrush is the worst software, substance is a pain to use… Few software have a better UI and UX than blender.
That used to be the case, not anymore. Funny story: When Teslas first came out (referring back to the car metaphor), buyers would take them straight from the showroom to the race track and enter them in drag races. They consistently won their group and class.
And the whole interface Tesla drivers needed to learn to go fast was just pressing the accelerator pedal to the floor. The car took care of everything else (no gearbox, full anti-slip traction control and pure electric torque).
As far as is known, this is achieved by expensive design of automation systems, and not by simplifying a car to a bicycle.
Also, complex CG tasks are far away from being solved by pushing pedals.
I think our dialogue gets really fascinating at this point where the person associated with KIT-ops (a massive addon that gets harder to learn as it gets functionality)
talks about simplicity to the author of the simplest Blender add-on (F2), that occupies a single key, and which combines organic modeling and hardcore manual variable-density retopology into a single simple workflow.
Sorry, but I couldn’t help but appreciate the irony =)
Hahaha. Just insert name of whatever addon suits you. Hilarious-- an ad hominem “generator” that insults whatever and whoever based on which flavor of response you don’t currently like.
You should consider patenting your approach here. It’s a good one!
BTW, if you want a copy of KIT OPS to try out, private message me and I’ll happily comp you a free one.
I see that you are a diamond developer. Thank you for your support of the Blender foundation. There are only three such contributors at that high level-- one of the three compatriots is the other person you’ve disparaged here, masterxeon, creator of Hard Ops.
I really didn’t tried to disparage anyone here. (I am subscribed to masterxeon’s patreon for years as well, he is a great artist and developer that I admire)
Hardops/KIT-ops/Boxcutter are a nice example - they can be hard to learn, but they definitely deserve it to get the hard work done faster.
All I want to say - functionality brings complexity, and it is ok. And summarizing a wide range of possibilities in a simple form is really hard and expensive design work.
I am closing this thread. The discussion is moving in circles and has been going on long enough. Concrete, constructive Blender UI / UX feedback to the developers is welcome in focused threads in the User Feedback or Usability section. Thanks.
"