Because too many software designers and project managers think “Look and Feel” stands for make it look awesome because then you’ll feel good when you look at it. They don’t realize that “look and feel” refers to the “feeling” you get from using it, not just from looking at it.
And that’s why software still sucks. When it comes to software, looking good is important, but not more important than being usable. If, as Thomas points out in this post over on Spend Matters on why you should Understand Your Use Case First — Develop Later!, it’s impossible to find the button or menu item you need, or determine if it even exists in the first place, as good as the software looks, it still sucks, at best.
Software has to support whatever process it was designed for, and it has to make it easy for the user to accomplish that process — if it doesn’t do that, then it fails — spectacularly! It might look damn good when it fails, but it still fails.
And as long as developers continue on this ridiculous hidden-menu, infinite scroll, more features than you need but none you actually use kick, software will continue to suck and keep us in the technological dark ages.
So what can you do? Shun software that puts look first and functionality second. Developers will get the message, and eventually so will their managers. Then software can continue to progress forward.