91–100 of 152 posts
Earlier quoted context omitted.
Where is the empirical evidence of a mother's love? Have you sent a PR for the joy of playing with a puppy in sunshine?
> Where is the empirical evidence of a mother's love? Everywhere? When they care for you when you're sick, drive you to sports practice, clean up after you and what not?
Microsoft forced millions to upgrade to Windows 10... it would be trivial to force an upgrade to a different build...
Microsoft forced millions to upgrade to Windows 10... it would be trivial to force an upgrade to a different build...
Snark is easy but a lot of these stories are from long before the whole Win 10 upgrade and is explicitly from before Windows Insider which puts it at least before 2014.
Seems like you could've achieved the end-goal by just warning of the danger and coming across like their safety is your primary concern rather than finding the leaks, i.e.: "Build 97241 contains a potentially fatal bug that could wipe your computer. If you are using Build 97241, please upgrade it to a more recent build or otherwise cease using this build immediately. We do not care how you acquired this build. We sim…
I imagine in Windows' case, some enterprising individuals who don't know better will end up installing these builds on various computers, and you end up with a large group of users on the wrong build who:
1. Expect better quality than the pre-release build provides.
2. Blame Microsoft for their pre-release build breaking.
Raymond Chen also mentions a third case where the pre-release build messes up other parts of the network... so now you've got:
3. Somebody else blaming this guy for something he genuinely thinks is Microsoft's fault.
And then if you put out a warning message, it's typically ignored because the software is 99% working until catastrophic failure. And then you still get blamed by unreasonable users who then spread the word about how much you suck but conveniently leave out the "leaked pre-release build" part of the story. (If you sense some bitterness, yeah, I've had a few of my own experiences with much less consequential software.)
It's a lose-lose situation for Microsoft. I don't envy anybody in that position, regardless of the quality of the final finished product.
Earlier quoted context omitted.
Is this one of those "only in America" stereotypes? I'd love to see how the hell they justified that, much less if they won
> I'd love to see how the hell they justified that, much less if they won There are general principles of responsibility of property owners for dangerous conditions on the property that apply even when the harm done by them is done to trespassers (and regardless of the purpose of the trespass.) IIRC, these are largely common law principles, and older than the US. Of course, they don't relieve any criminal liability f…
Bizarre!
Earlier quoted context omitted.
> I'd love to see how the hell they justified that, much less if they won There are general principles of responsibility of property owners for dangerous conditions on the property that apply even when the harm done by them is done to trespassers (and regardless of the purpose of the trespass.) IIRC, these are largely common law principles, and older than the US. Of course, they don't relieve any criminal liability f…
So - if an intruder breaks in to your house, you can shoot him without repercussions; but if an intruder breaks into your house and trips on your loose stair carpet, he can sue for his resulting injuries? Bizarre!
In many US jurisdictions, not generally the case. The ones with a strong "castle doctrine" are notable because this is not the norm.
But, even so...
> So - if an intruder breaks in to your house, you can shoot him without repercussions
Your loose stair carpet was not created as a specific and immediate response to a particular unlawful act, and thus the relief from otherwise applicable legal liability attached as a result of self-defense doesn't apply to it.
Include a remotely-activated kill switch; and kill with plenty of warning. What do I mean? I no longer use iPhone because I installed a beta iOS. When the official build came out, I kept "checking for updates" but I never got an update. One day, Apple remotely killed my phone. Manually updating to the production iOS would be fine; but remotely disabling my phone without warning was not acceptable. This is why I refus…
It is quite likely the project Raymond is talking about is Longhorn, as a few pre-'reset' builds were leaked in quick succession.
How about: have a really cheesy wallpapers in the pre-release builds which conveys the message (perhaps with explicit text right in the wallpaper image) that this is not a released build. Also, how about making not-released builds simply expire. The build should know that nobody ought to run it past a certain date. (If such operation is needed internally, it can be rigged with an extension mechanism built into the ex…
I think that would get the message across quite effectively :)
Earlier quoted context omitted.
Might be considered a public disclosure for purposes of patenting the feature.
This is accurate. A leak still constitutes a public disclosure (I use to help track down leaked builds of Windows)
Surely if the "leak" is the result of an employee acting unlawfully, i.e. maliciously leaking their employer's intellectual property in contravention of their employment agreement, then the leak does not constitute a disclosure.
If it did, then IP-based organisations would have an absurd level of exposure to the bad actions of any employee, and would have to impose equally absurd security measures - cavity searches at the exits, anyone? - on every employee with access to IP.