Power User definition

>People don't like change. When people see change they don't like it. It doesn't matter if it's a improvement or not. They will bitch, always. ALWAYS.

That's because there's a cost associated with adopting to a change. If there isn't a perceived benefit to change that outweighs the cost, then people are going to be unhappy about it.

Think of it like maintaining API compatibility in libc. At some point, someone realized that read() could be improved by adding an offset to eliminate the need for two syscalls (lseek and read). If they would have just changed read(), that would have broke a lot of applications. So instead they introduced pread().

Yes, having 2 (or 3, or 4) different calls for read() is "crufty". We'd all rather work in code bases that never maintained these sorts of things.

But it's unrealistic to build a library and pretend like there's zero-cost in porting applications if the library breaks API compatibility.

Likewise, it's unrealistic to build a GUI environment and pretend like there's zero-cost in learning new workflows/options. Imagine how upset people would get if glibc started breaking ABI compatibility every couple years in core POSIX calls. That's effectively what Gnome is doing.