Yes, and depending on the enterprise, these "big features only there to justify high costs" may not actually be needed or useful or relevant. It might be 'OK' to have a bunch of interns slap something together, if it only needs to be "real" enough to look pretty and look functional in a few demos or in a few specific happy-day cases.
Analytics and Reporting is probably the most common example I've seen of this -- it's not a bad feature on it's own, but companies will sometimes pay top dollar for it, even in places it makes no sense and/or will never get used. If that gets delivered in a broken/unusable state, it's "ok" because the customer will never actually click that button anyway.
----
If "New Skype" is "enterprise communication support" in a corporate feature list (and not a real product filling a real need, as it used to be) then I can see how a broken or unusable Skype could still be a 'success' for Microsoft.
Note: I don't agree with any or support any of this. But I've seen this play out in real life enough to know it happens.
Are you implying people are paying for dropped calls and poor performance as a feature?
The old normal (not for business) Skype Linux client could even do active screen sharing (share your own screen) on Linux. Although it was limited to 1:1 calls IIRC. Haven't checked whether they have managed to break/remove that in the new Linux client...
Software is horrible.
Software that looked like Excel 2000 with visible accelerators was clean, easy to use, discoverable, fast, not very aesthetically pleasing but at least consistent. macOS of 5+ years ago was more human-friendly.
Linux usability is only abhorrent if you use Gnome (3). It's fine with KDE, Xfce, and others. I started using Xfce recently at work and it's great: usability is just what I expect (i.e. it doesn't do any weird UI experiments like Gnome3, Windows, etc.), it's stable and reliable, and discoverable since it was designed back when they thought discoverability was a good thing. KDE5 is pretty good too.
Stop using UIs that have been taken over by people trying to "revolutionize" UIs and you won't have the problems you're seeing. Linux has plenty of such UIs, but for some odd reason they're not the default setting of the mainstream distros.
root@server:~# ip route add 192.168.1.0/30 10.0.0.1
Error: either "to" is duplicate, or "10.0.0.1" is a garbage.
The "help" is literally a dump of the grammar, which doesn't contain enough detail to add a route (the syntax of PREFIX is not described). The error message is bafflingly useless. Of all the options available relating to routing, the two I use most are "route a network via a gateway IP" and "remove a route" and I'm going to guess that those are the two most common operations for most people not doing any advanced networking.
Note that this is the replacement to the old "route" command, which had a single line of help: "inet_route [-vF] add {-host|-net} Target[/prefix] [gw Gw]" which is way way more helpful for this use case!
Of course it's possible to go into `man ip` and then find routing help is elsewere and go into `man ip-route` and at the bottom of a 400 line document there is /a single example/ of adding a default route which doesn't include a subnet definition, and then to decode that the error message about duplicate/garbage means "you didn't add the word "via"" and then to backtrack into the grammar dump and trace where that was mentioned.
And of course this is but one tool.
And of course it's better for many use cases that it be stable and performant than that it be frilly.
But all over, it feels like this. Usability, quality error messages, making the common things easy and discoverable, are all afterthoughts with priorities somewhere between "caveat user" and "it's free so shut up" and "we refuse to change it because ~POSIX~" and "usability is for wimps, Linux is for clever people (where clever means 'able to edit a text file and willing to do everything the hard way')" and "we benefit from people buying RedHat Certifications so why should we make it any easier than we have to?".
I'm not saying it's incapable or unstable or useless, but I am saying usability for common tools and overall experience is really, really, really, really poor. With possible exception "install Ubuntu/Mint/flavour-of-day and run FireFox to get to your Googles".
I like my setup (i3wm), but it would be a horrible default. You have to read a manual to make it usable. Gnome is a kind of nice default - since everything looks modern and works out of the box.
Completely impplaussible that maybe those stupid people do not use the alternatives, because they suck even more? As in, they are non standardized, not easy to setup et etc.
The old Skype was great. But it's gone now; that's how the world works: things change, and not always for the better. You have to adapt.
>Completely impplaussible that maybe those stupid people do not use the alternatives, because they suck even more?
Given all the complaints I've seen about new-Skype? No. It's because people are just too stupid to look for alternatives when the thing they've been using turns to crap.
>As in, they are non standardized, not easy to setup et etc.
The newer alternatives are web-based and easy (or, at least, no more difficult than new-Skype). And WTF does "standardized" mean? There's no standardization for video chat programs; that makes as much sense as asking about standardization for social media websites like Facebook.
That's a scenario where the needs of the people making and receiving calls are subordinate to the needs of the people paying for Skype.
But sometimes it is a question of different priorities, and I did not mention that above. Good catch.
But actually, I meant that it is apocryphal that salespeople have to play golf to close Enterprise Sales. It's more of a stand-in catch-all term for semi-formal socializing with the client.
"When I started in sales, my boss told me, "Your job is to get to know your customer and build a relationship. Nothing is more important than building a relationship.” The second most important thing was to make sure that the customer always won when we played golf."
https://www.forbes.com/sites/salesforce/2017/01/03/the-death...
https://discuss.fogcreek.com/askjoel/default.asp?cmd=show&ix...
"With software sold in corporations, as soon as your price gets up in the $3000 level, the amount of approval it needs is so absurd that you are not going to sell products without a salesperson making a few visits. Hiring the salesperson, sending them out to make presentations, hotels, airfare -- now it costs $50,000 to get the sale done just in sales closing costs. That's why you see a lot of software products at $100,000 and a lot under $3000, but anywhere in-between and it's impossible to make sales. (It's sort of funny -- these big corporations create so much bureaucracy around purchasing in order to protect themselves against losing money, but they just force the vendors to spend a fortune on salesforces, which results in vastly higher prices for the big corporations)."
1. You are not the customer.
With ad-driven products, we have painfully realized that if we aren't paying, we aren't the customer, and when something seems awful to us, the explanation often lies in the fact that the thing that is awful to us benefits the real customer, or perhaps that the thing that benefits us is of little value to the real customer compared to things that do not benefit us.
The same is true of Enterprise Software. Most users are not the software's customer, and therefore their needs are subordinate to the needs of the individuals and departments who are actually paying for it.
2. Pricing-Driven Development
As Spolsky famously pointed out, Enterprises forcibly impose an insane cost-of-sales on software vendors. When you have to employ expensive salespeople, prepare proposals, apocryphally play golf with clients, or whatever, vendors must build those costs into the cost of the product.
Then they must justify those costs with features that sound like they produce big values. Typically these are not going to be things that make users' lives easier, they are going to be things that users may never see, like analytics and back-office integrations.
Like the "you are not the customer" problem above, this tends to create the illusion that the software sucks and that the vendor isn't improving it. In actual fact, the vendor is locked into a Red Queen's Race with competing vendors, and is improving the software constantly. It's just that users never benefit from the improvements, because UX improvements are not thought to "move the needle."