It was the tweet heard by the (Microsoft) world: sets are "no more". Except for one thing. They are still on the to-do list.
What triggered this confusion?
Rich Turner's executive program manager responding to a Twitter question about sets wrote: The tab experience provided by the shell no longer exists. "This led to numerous writing assignments, such as How-To-Geek, announcing that Sets was dead. However, Mr. Turner also noted that "adding tabs on the to-do list of 19459013 is at the top." The story is a bit more differentiated than "Sets is dead".
For those who are unfamiliar, Sets was a feature promised by Microsoft in Windows 10 that a tabbed application interface would be added. You could have multiple tabs in, for example, File Explorer or Microsoft Word or whatever. As originally implemented, sets based on the Microsoft Edge tab code. A web browser that uses Turner's words is "no more". So it makes sense that this original set implementation is also dead, because the classic edge is also dead.
But here's what I think happens. 19659002] Turner's note about a tabbed UI still on Microsoft's To-Do List is the more important part of this tweet: Microsoft's Plans have not changed. It is still intended to register Windows 10. This functionality only needs to be re-implemented because the previously used code base is retired and / or goes into maintenance mode.
If you read the answers Turner's Tweet, you will see a lot of anticipated speculation about how and why this change has taken place. However, I am surprised that the theme of the classic edge codebase never comes up. As this is clearly the cause of the new delay.
Regardless of the fact that sets are on Microsoft's to-do list, this feature still works. From a strategic point of view nothing has changed. What has changed are the technical means by which Microsoft will get there.
Of course, the problem real here is a problem of communication: How Chris Howman of How-To Geek stresses that he needs to analyze the strategy of Microsoft about A tweet from a single employee, no matter how good-natured he is is frustrating. This is also a prime example of this company's inability to communicate effectively. Come on, Microsoft, here's something official. You have a number of blogs to choose from.
Until we hear something else, I stay with Twitter for the truth that emerges from this conversation: Microsoft still intends to implement sets in Windows 10. It's only a matter of time. 19659002] provided with sets