Do you? Developers rarely decide what features stay or go or come back again.

They could have kept doing internal testing until the product's functionality was the same, but they chose to release it with missing features. That was a mistake. Was it a developer mistake? Probably not, but it WAS a mistake.

Windows+q? Save yourself a keystroke by just pressing the windows key and start typing

EDIT: Wait does that still work on Windows 11? I haven't upgraded yet and don't plan to anytime soon

Oh shit you are right. You solved it. Start a company asap and hire a bunch of devs to easily take over the software world.

It’s a technology subreddit. Fascinating to be honest.

jokes on you, I dont work, I procrastinate.

The point that you're missing is where choosing to go in a direction that causes the loss of helpful features is a mistake to begin with.

Yup it’s only you. You’re so special.

> People don't generally have a concept of MVP (Minimum Viable Product).

Ever since the first season of 'Silicon Valley' pretty much every idiot knows exactly what that is.

It's sad that you're being downvoted because you are absolutely correct. People don't generally have a concept of MVP (Minimum Viable Product).

My advice would be not to bother with these people, nothing you say will make any difference, they'd rather be mad at Microsoft.

This whole thread kind of reminds me of a scene in the Simpsons where they have principal Skinner tied to a post and about to light him on fire as he exclaims: "I'm telling you people! The Earth revolves around the sun!"

Also, downvoting me isn't going to make you any more right.

This article references power users....am I the only one who does everything with windows+q and typing what I need to do, or windows+x to get into any system menus?

I’d bet every product you have purchased has followed this flow and likely has some feature someone wanted they didn’t have right away. Most software is free and many people upgraded windows for free or with their new computer. Microsoft prioritizes the most important feature for a release then enhances it constantly. They even have a forum where the more noise you make the higher up the priority list it can go.

I'm not changing my pants simply because I pooped in them. The reasons are more complex than that. My pants are suddenly wet, stinky, and heavier. I'm putting pants on from the ground up that will be drier, lighter, and more odorless than ever before.

This person said screwed up. I offer an explanation for how and why it can happen without screwing up and aligns exactly to what the article said.

Your appeal to the authority of being a dev is not compelling, offer something more than that or jog off.

Looks like you're confusing the customer for the developer. Who is actually buying and using the product?

You know, rather than assume you could just ask how it’s possible.

There are times you rebuild something from scratch and old versions of code in that case don’t make sense. In some cases you can copy it over but in many cases it just wouldn’t make sense with the new structure of the project. You basically are rebuilding your product from scratch and prioritizing the most important features to recreate first. You then have to make it worth it for the customer so you build new features too. On the backlog you keep a list of things you likely want to bring back but are less pressing.

I could never get used to not simply looking down at the bottom of the screen and seeing all of my windows separated and given their own icon and a title. Grouping icons makes everything feel hidden and vague to me.

I'd imagine there's a version in development at all times, for something as pervasive as windows.

It's possible that support for features may be dropped as technology changes, such as floppy disks going obsolete. It doesn't make sense, however, to drop a feature that is currently used and well-liked.

You are correct. But “l” know how to type.

How do software product lifecycles work exactly? How is it possible for a company to both build something new and not have a feature they used to have? That’s the question related to the article and a key part of how software development works.

A developer has an idea. They or a hired programmer write a series of conditional instructions for a computer to carry out that best matches the desired functionality of the "program," and the developer iterates on those instructions until the resultant program reflects the developer's (or the customer's) vision for it.

Is that the gist of it?

Going to point to my comment above to again reiterate how clear it is you don’t work I software.

Seems like you don’t care about how end users work.

Seems like you are not a developer and have no idea how software works.