News for hackers. Stuff that matters.
Re:Announcing .NET Core 1.0 by wvenable on Monday June 27, 2016 @01:13PM (#11987627)
Microsoft is looking to do more data-driven design; this is the reason for all the telemetry in Windows as well. Raymond Chen pointed out an example where a button was removed File Explorer (prime real-estate) because the telemetry showed that hardly anyone ever pressed it.

It's unfortunate they are so tone-deaf about the PR implications in Windows.

Re:Announcing .NET Core 1.0 by logfromblammo on Monday June 27, 2016 @01:44PM (#11987882)
We have removed all the weapon deployment buttons from our nuclear subs, silos, and bombers, because telemetry shows that they are typically only pressed during unit testing.

Since we only have two recorded events of someone deploying a nuclear weapon in a real-world scenario, it should be safe to relocate those buttons off the main console, and just use the auxiliary functions button, behind the kick panel, next to the row of DIP switches used for selecting the button press function. Since "reorder coffee pods" was the last auxiliary function to be added, "launch nukes" will be next, so make sure you double-check those switches before pushing, coffee drinkers!

Re:Announcing .NET Core 1.0 by MichaelApproved on Monday June 27, 2016 @02:52PM (#11988495)
You're joking but I'll give a serious reply to why your analogy is off. This is why they have war games. The telemetry from those games would be included in the analysis.
Re:Announcing .NET Core 1.0 by logfromblammo on Monday June 27, 2016 @05:50PM (#11989805)
My point was that user interface patterns do not always indicate the importance of the control, because there may be multiple modes of operation (such as "Standby", "War", "War Game", and "Readiness Drill") that might not be obvious--or even apparent--from the raw button-press numbers.

You want the "War Game" telemetry to count for the "War" design, but you can't really tell which is which without having additional data that you shouldn't be allowed to see. If you detect "casual user" and "programmer" modes in your OS, the user shouts, "I don't want my computer knowing (and sharing) that much info about who I am!"

Even though most people aren't likely to ever need to use a fire extinguisher, you really want that interface to be simple and accessible. If you decide that because no one ever used this particular fire extinguisher, it doesn't need to be there, that's a decision that could make the difference between life and death. Moving a button on a form doesn't seem quite that serious, but it could still cause people to lose time or money, which adds up across all the people using the software.

Re:Announcing .NET Core 1.0 by Klathmon on Monday June 27, 2016 @06:51PM (#11990148)
But they aren't saying they will blindly follow the telemetry data, just that it's an important factor.

You need to determine which feature to add:

1. One that 3 developers asked for

2. One that 6 developers asked for.

With telemetry that can become:

1. One that 3 developers asked for and can improve things for 60% of your userbase.

2. One that 6 developers asked for, but only 12 of them are using the function that it will improve.

Without telemetry data, you are playing with an arm tied behind your back.

Re:Announcing .NET Core 1.0 by georgemcbay on Monday June 27, 2016 @02:19PM (#11988194)
I know this is just meant in jest, but because the weapon deployment buttons are something you never want to be pressed on accident, ideally you really do want to obscure them behind layers and layers of user interaction.

If anything we had the problem of them not being obscured enough for a while (if the story of the launch codes being 00000000 across the board is true).

Re:Announcing .NET Core 1.0 by djsumdog on Monday June 27, 2016 @05:04PM (#11989472)
I thought it was just four zeros (0000)
Re:Announcing .NET Core 1.0 by luciusism on Monday June 27, 2016 @05:03PM (#11989460)
The "Compatibility Files" button was removed: https://blogs.msdn.microsoft.com/oldnewthing/20150902-00/?p=...
Re:Announcing .NET Core 1.0 by jenscow on Monday June 27, 2016 @01:30PM (#11987772)
Like when they removed Macros from Visual Studio because according to telemetry only 1% of users used them.
Re:Announcing .NET Core 1.0 by hatchnyc on Monday June 27, 2016 @01:41PM (#11987863)
I always suspected that there was probably significant overlap between users of macros and users who opted out of telemetry. Lesson learned: leaving "yes" checked from now on.
Re:Announcing .NET Core 1.0 by emn13 on Monday June 27, 2016 @03:25PM (#11988751)
Big Brother has trained you well. ;-)
Re:Announcing .NET Core 1.0 by kbenson on Monday June 27, 2016 @04:55PM (#11989394)
Yep. Don't vote and nobody will care about your (unexpressed) needs when making decisions.
Re:Announcing .NET Core 1.0 by BHSPitMonkey on Monday June 27, 2016 @05:19PM (#11989589)
Well, it would be nice if there is a way to vote or express one's needs via some alternative to having one's usage actively mined for data.
Re:Announcing .NET Core 1.0 by cfreeman on Monday June 27, 2016 @07:46PM (#11990429)
I think you are truly in a minority if you'd rather take a survey than have the data collected automatically. There has to be a sane middle ground.
Re:Announcing .NET Core 1.0 by emn13 on Saturday July 02, 2016 @09:45AM (#12022484)
Data collected by a neutral third party without conflicting interests pushing for creative monetization opportunities that's responsible for sufficient annonymisation/aggregation before releasing the data?
Re:Announcing .NET Core 1.0 by reitanqild on Monday June 27, 2016 @05:45PM (#11989773)
There is mining for data and there is mining for data.

Monitoring which features I use? Opt in.

Monitoring what I do? Uninstall if possible.

Re:Announcing .NET Core 1.0 by rbanffy on Tuesday June 28, 2016 @05:19PM (#11997670)
You can always refrain to use their technology. There is plenty green grass in the neighboring fields.
Re:Announcing .NET Core 1.0 by spo81rty on Monday June 27, 2016 @09:50PM (#11990940)
I only remember accidentally t turning them on and they getting mad!
Re:Announcing .NET Core 1.0 by iask on Monday June 27, 2016 @08:14PM (#11990559)
Are you referring to the 1% on wall street? ;)
Re:Announcing .NET Core 1.0 by brudgers on Monday June 27, 2016 @01:23PM (#11987705)
The Story of the Ribbon video about Microsoft and data driven design.

https://www.youtube.com/watch?v=Tl9kD693ie4

Re:Announcing .NET Core 1.0 by jameskegel on Monday June 27, 2016 @05:52PM (#11989820)
The Ribbon is, in my opinion, the use interface equivalent of a broken pull tab on a can of corn. I know it is there, I know that I'm supposed to use it, but I can't because it is broken.
Re:Announcing .NET Core 1.0 by krylon on Tuesday June 28, 2016 @05:19AM (#11992434)
I am relieved to see there is somebody out there who shares my opinion on this ... innovation.
Re:Announcing .NET Core 1.0 by ethbro on Monday June 27, 2016 @02:32PM (#11988337)
Ribbon, or "How to Figure Out Where a Menu Item Is Based Solely on UX Data"*

*Customers may not be granted access to UX data

Re:Announcing .NET Core 1.0 by jobigoud on Monday June 27, 2016 @03:35PM (#11988824)
> a button was removed from File Explorer

Would that be the "Go up to the parent directory" button that was removed in 7 by any chance?

Re:Announcing .NET Core 1.0 by ohitsdom on Monday June 27, 2016 @04:07PM (#11989051)
Easily my favorite button in file explorer.
Re:Announcing .NET Core 1.0 by serge2k on Monday June 27, 2016 @05:36PM (#11989704)
They still have that button, and you can go up by clicking on the parent folder name as well.
Re:Announcing .NET Core 1.0 by LeonB on Monday June 27, 2016 @06:32PM (#11990047)
[Ctrl][Up] works in Vista onwards to move up a folder. It's worth knowing.
Re:Announcing .NET Core 1.0 by pidg on Tuesday June 28, 2016 @05:29AM (#11992466)
<Backspace> does this, since XP I think - ^↑ doesn't seem to work for me in Win 10.
Re:Announcing .NET Core 1.0 by Ntrails on Tuesday June 28, 2016 @08:57AM (#11993376)
Backspace is "back" not "up a folder level" as far as I am aware. This is consistent with web browsers - and indeed the conceptual meaning of "backspace" (go back 1)
Re:Announcing .NET Core 1.0 by dingle_thunk on Monday June 27, 2016 @07:18PM (#11990275)
No. And that was added back in Windows 10.
Re:Announcing .NET Core 1.0 by contextfree on Monday June 27, 2016 @11:28PM (#11991300)
8, actually