as the update consumed RAM at a prodigious rate for some before falling over
Yes, that update has been out for years.
Windows Insiders eager to get their hands on next year's Microsoft OS were reminded last night that living on the bleeding edge can have its downsides: the update consumes RAM at a prodigious rate for some before falling over. It all began so well. Build 18237 was emitted with the usual degree of fanfare. Now given a …
...the Internet Explorer 4 launch? It wasn't really an update to IE, it was a beta test for Win98 in disguise. A least in the here and now Microsoft is being a little bit more honest about what code isn't ready for mass consumption. Now that I think about it, I don't know a a single personal that I would consider "well qualified" in the IT world that participates in the Windows Insider program. Maybe that is a good thing, maybe it's not.
There are no fanatics. Either idiots or Redmond C-team on the pay.
xNIX platform proved much much better in everything. I bet M$ will slide in Linux based system after W10 like MAC OS is based on BSD. W10 and other server versions cannot be better because they reach the summit entropy point. After that is simple chaos and system degradation. That is what we see in failing patches and updates. After 25 years of attempts to make such process stable.
After 25 years of dominating IT OS market Redmond crap is going to die as OS. 25 years wasted and thousands of strokes and heart attacks.
I remember W95 presentation and advertising clip. Completely stupid and idiotic. With Bill of Redmond as the star. Behaving correspondingly. That was the label for all Windows OS versions I used since that.
I do. I'm in their "insider" program, receiving early releases from their ring.
But it's only to test our own stuff, see what they've broke next and fix our products before their general release. It's all in a VM (as is nearly all our Windows machines), and mostly automated.
I have zero interest in making Windows better. You're fighting the largest company in the world with that.
In fact, I discovered a bug and reported it (twice) over a year ago. I probably "reported" it more times, via telemetry. It's still there now, I just work around it. I've spotted a few more, but I'm not wasting my time with them.
Had it been something preventing cortana starting, they would have flew in a team of developers.
Honestly, exactly, what do these people get out of testing windows for MS for free?
Entertainment value? Finding new-found appreciation for your primary machine that's running Linux?
Actually, I have an old scrap laptop running the tech preview, mainly so I know what shit is coming down the tubes before friends and family encounter it.
Internet Exploder 4 with it's introduction of Active Desktop to NT4 was the shiitake!
For an Admin it 'was' cool to provide an interactive internal directory of stuff on the Desktop.
For a User it was an awesome way to fill the disk and compromise the PC. Some were walked out based on content they had viewed that had been inadvertently set to be included in the active desktop experience.
when I wrote for computer magazines I always had one or more beta test computers. But obviously, no one in their right mind would pollute a fully functioning PC with a beta or even the first integer release and at least 2 dot releases of any OS changes, especially from Microsoft.
Traveling down memory lane. I remember the first few versions of MS DOS and PC DOS that were simply a licensed hack of CP/M and called QDOS for Quick and Dirty Operating System. Microsoft either licensed or bought it from a Seattle developer for $50,000 and became billionaires off of it.
Windows release versions are still terribly bug ridden. I read that Microsft has two QA testers for every programmer. Security researchers are making plenty of money reporting vulnerabilities (aka bugs) in that horrible operating system.
Microsoft does not do "testing" any more. It's why they have
And they probably don't have a sense of humor, either.
Hey Micro-shaft: it's ready AIM fire, not ready FIRE aim. Or, in your case, patch, TEST, upload to servers, not what YOU did: patch, upload to servers, test.
Well, that's right - you don't do "test" any more! So you REALLY did patch, upload [no test].
icon, because, facepalm for the OBVIOUS 'lameness' of this moment
It is an early test version -- only an idiot would install it and not expect problems.
Sheesh, 19H1, skip ahead version.
I know, MS should have "test version" superimposed on the Start Menu and Desktop of every Insider version, they don't. But still, after all this time who would not expect an early test version to have serious problems?
But still, after all this time who would not expect
an early test version a General Availability release to have serious problems?
There, fixed it for you.
You seem to forget that it is MS we're talking about.
"The next time these chuckleheads boast about their quarterly profits, remember part of that largess comes at the expense of having anything resembling a responsible QA process."
cannot be emphasized enough
(insiders and end users - those are the new 'QA department', with forced updates to perpetuate it)
It's so blurred its a complete waste of settings, images, company logos spent on it.
It looks to me to be more blurred than the half life model (will have to go check when I get home) but even compress you only know the pic is dunes because we know the original.
As far as I am concerned, have images, or no images, big blurs are a waste of time, and frankly can be procedurally generated without all the tedious mucking about with large hi res image files that look that the were scaled from an icon to full HD resolution.
What's with the hate of blur?
I'm one big ADORER of blur. Much like "frosted glass" in my opinion. And that lockscreen screenshot looks good, actually. (Finally, a new feature to actually like in Windows 10!)
I've even brought it over to Linux - magic of compton ;-)
Biting the hand that feeds IT © 1998–2019