Adding to this, security should always match the value of the thing being secured. I use weaker passwords on sites I don't care much about, and strong passwords on banking sites and such.
Here's another philosophy I tend to use: I have sufficiently secured a channel if there are much easier ways to obtain the data via other channels I do not control. For instance, if I write a thick client app that only uploads all its data to an unsecured HTTP web service, then it's probably not worth it to add tons of security into the app like obfuscation and data store encryption and such.
I'm pretty sure I heard him say that if you like your compiler, you can keep your compiler.
@magicalclick: And if it were just this one time, we wouldn't mind all that much. We've all had flawed reasoning, it's a human condition.
But you do this often here on this forum. You say something, then when people point out a flaw in your reasoning, you act like you never said the thing in the first place. But you did say the thing, and it's quite annoying that you keep arguing the thing and then act like you never said the thing.
Maybe the annoyance you are experiencing with W10 is karma coming back to bite you.
So let's consider this statement. I'll go back and speak to your initial post which had 2 main points:
Ok, it sounds good in paper. That it will do a lot of updates just like competitors. But, I now getting annoyed by it. The update actually crippled the OS. The Music can't play music when minimized. And now I just found out that it turns itself off as well. Sure it is alpha or something. But, the bricking update is just terrible both intentionally or unintentionally.
That part is talking about the inconvenience of the fact that a recent update screwed something up. It is noteworthy because it helps illustrate that a new (rather annoying) bug exists. I think is a fine point to make.
Here's your concluding point:
And I fear the future of Windows is like this. I am currently having less trust to the updates than before. I am considering turn it off when I get the official build.
Now, combine that with the title: "Fear of new Windows ways."
The only conclusion is that, while you had good points to begin with, your true intention for this thread was showing us that you consider alpha-level updates to be equivalent to release-level updates.
And we said that is silly, the two aren't comparable.
So, I do believe that we are debating "how words should be defined and applied".
Then that's it.
But the bug I am experiencing right now it very intentional. They knew it and they still put it out.
Intentional? Of course it is, it is an alpha. By definition, an alpha product is something that is intentionally put out even though there are unknown and sometimes even known quality issues.
I thought you said you knew there would be risk.
Yes, I know it is alpha build
Ok, good, we're on the same page again.
but, tell me, will your company push out public alpha with major functionality issues?
See now you make me think that you don't in fact understand what alpha means. Perhaps you are confusing it with something that has some level of guarantee of working, which W10 Insider Preview does not have. It even states when you sign up for the insider program that you should be comfortable with formatting your hard drive because it might be necessary, and that you should not use it as your day-to-day OS.
Proceed at your own risk.
Oh, and file a bug report in the feedback app. That will get it resolved much faster than this forum.
@kettch: Yeah, I've been using Chrome as my main browser for years, and recently my company decided to support Chrome officially (whereas it only supported IE before).
Well, by "support" I mean they issued new policy that locks Chrome extensions down to a thin whitelist. So now my best productivity tools are blocked, and there's no way around it short of installing it in a VM.