Microsoft Accidentally Released Internal Windows 10 Development Builds (theverge.com)
Microsoft is apologizing for mistakenly releasing some confidential and internal Windows 10 builds to the public. "Builds from some of our internal branches were accidentally released for PC and Mobile," reveals Dona Sarkar, Microsoft's head of its Windows Insiders program. "This happened because an inadvertent deployment to the engineering system that controls which builds / which rings to push out to insiders." The Verge reports: Microsoft says it quickly reverted the issue and put blocks in place to ensure these development builds didn't reach more people, but a "small portion" of Windows 10 users still received them. Worryingly, the accidental mobile build even reached retail devices outside of Microsoft's Windows Insiders testing. If Windows 10 testers installed the mobile build it forced phones into a reboot loop and bricked the device. Testers will have to recover and wipe the device using the Windows Device Recovery Tool. Windows 10 testers that installed the PC build, an internal Edge branch, will have to wait for Microsoft to publish a newer build or roll back using the recovery option in Windows 10 settings.
Microsoft is evil and does not care about the best interests of their customers. These updates are harmful but users don't have a choice other than Windows 10 because Microsoft is a monopoly. Odumba should have issued an executive order to break up Microsoft for violating antitrust laws.
I don't think it means what you think it means...
I'm sure Office 365 and Azure customers will be...heartened and encouraged...by this sort of expertise in operations and system management on the part of their cloud service provider.
Users of their client software, by contrast, can think happy thoughts about how robust and well supervised the release process for Windows updates is.
Gee, if you didn't tell us it wasn't intentional, we probably wouldn't have been able to distinguish it from any other update.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
I must have been using an accidentally released internal build all these years.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
Did the builds have debug symbols? That would be a goldmine for reverse-engineers.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Well, they are moving everything to something git-based, which is a _LOT_ of work. Especially because normal git can't handle something that massive, so it is actually a diffused, virtual networked git object storage, with every other CI and deployment tool needing to be migrated to this new backend.
Someone likely screwed up on one of the provisioning tools, or a new tool was easy enough to misuse, and someone got confused (for real, or on purpose -- lots of people there are not really happy that they need to learn something new, the usual :p).
macOS hardware choice sucks! you can hack it but after each update you may have to re hack it
macOS hardware choice sucks! you can hack it but after each update you may have to re hack it
Mac hardware is much more carefully-spec'ed than you realize.
For about 85-90% of applications, what they offer does just fine. The other 10% usually hack. Apple has obviously accepted that tacit arrangement. They could lock macOS to Apple hardware with ease; but they don't.
I believe that is exactly why.