Wow, the Verge sort of butchered the new requirement on updates and is causing some misinformation here...
You can delay when the updates get installed by a few days. That hasn't changed. What has changed is that they now require you to keep your machine on the latest version of the OS.
Here's a quick scenario for how Win10 works today:
Let's say your machine downloads an update which requires a reboot (not all of them do though). Windows will then let you schedule when that update happens. You get two options for update time (in addition to 'reboot now').
1) Windows knows when you're using it, and when you're not, so it will recommend a time when you're not using it. For my machine, it tells me 3:30am is the best time to update since I'm never up that late on the machine and it's a perfectly fine time to update. I think this is the default option.
2) You can also manually choose a date/time. I don't have an update available and can't check, but I believe you can schedule it up to 72 hours from the time the update is ready.
Windows isn't going to reboot everyone's PC's at once when they push out an update. That would be insane. That's how the Verge made it sound, and how some here interpreted it but it's certainly not the case.
Now, for "Pro" you get the option to
defer an update. What that means is that you are not required to install that update within those 72 hours. You essentially have until the next OS update to make sure your business is ready. Remember, Windows 10 is going to have frequent releases. Maybe not as frequent as the monthly Xbox One updates, but certainly much, much faster than every 2 years.
Mary Jo Foley pieces together the story fairly well:
http://www.zdnet.com/article/piecing-together-the-windows-as-a-service-puzzle-for-windows-10/
There will be three branches of Windows 10 out there at any given time.
1) Current Branch (version N) - Windows 10 Home users live here. The most up to date version of the OS
2) Current Branch for Business (version N - 1) - Windows 10 pro users can live here if they choose to defer updates. However, once a new Current Branch release happens, they will then get updated to what was the previous Current Branch release. Essentially one update behind Current Branch.
3) Long Term Service Branch - Enterprise users live here. Contains ONLY security updates, no new functionality to a build. The build is supported for 5 or 10 years I believe from when it gets pushed here. Gives enterprises time to orchestrate an upgrade, make sure all of their software will work on it, schedule training, etc.
Microsoft has the Insider program and flight rings which will greatly help weed out issues like this. If something isn't a critical fix needed to be pushed out immediately, it could potentially wait to be in the next OS update. That OS update will then go through the process the preview builds are going through. MS internal -> Insiders on Fast ring -> Insiders on Slow ring -> Public