New Windows 10 Insider Preview Skip Ahead Build 18214 - August 10 Insider

I think MS should completely skip Skip Ahead and focus more resources on making the publicly released builds better and Fast Ring builds to at least being able to update and run without screwing up the whole system.

slicendice said:

I think MS should completely skip Skip Ahead and focus more resources on making the publicly released builds better and Fast Ring builds to at least being able to update and run without screwing up the whole system.

And leave me bored ? No thank you.

slicendice said:

I think MS should completely skip Skip Ahead and focus more resources on making the publicly released builds better and Fast Ring builds to at least being able to update and run without screwing up the whole system.

But, but, but . . . they already have a team working on Fast Ring Builds. In fact, I think I just got the third update yesterday.

I like Skip Ahead and don't want to dispense with it.

CountMike said:

And leave me bored ? No thank you.

Perzackly!

CountMike said:

And leave me bored ? No thank you.

Wynona said:

Perzackly!

Wynona said:

But, but, but . . . they already have a team working on Fast Ring Builds. In fact, I think I just got the third update yesterday.

I like Skip Ahead and don't want to dispense with it.

There are more important things in life to do than poking around in this never ending story. To be honest, I see absolutely no difference between the official public build, Slow Ring, Fast Ring and Skip Ahead. They are all equally much Beta software where one has new emojis and the other doesn't.

MS should not skip ahead when not even the older software work properly.

...just saying...

slicendice said:

There are more important things in life to do than poking around in this never ending story. To be honest, I see absolutely no difference between the official public build, Slow Ring, Fast Ring and Skip Ahead. They are all equally much Beta software where one has new emojis and the other doesn't.

MS should not skip ahead when not even the older software work properly.

...just saying...

There certainly are better things to do but it's same case with playing games or kicking a ball around.

CountMike said:

There certainly are better things to do but it's same case with playing games or kicking a ball around.

Sure, we all choose our entertainment we enjoy best.

slicendice said:

Sure, we all choose our entertainment we enjoy best.

Or as much as we can, After 70th birthday I ain't much for ball kicking any more.

slicendice said:

MS should not skip ahead when not even the older software work properly.

...just saying...

The problem with your opinion is that it is predicated on the assumption that if those development resources were assigned to the Fast Ring, one would see a benefit in improved FR reliability. Life just does not work like that.

It is like proverbs - for every proverb, there is a counter proverb.

For moving resources "Many hands make light work".

Against "Too many cooks spoil the broth".

I also bet the the Skippy Developers would consider bug bashing as beneath them and for juniors.

IMO whether skippy exists or not, I doubt moving resources will have any benefit.

In the end, as a user, you do not have to partake in Skippy - I tend to be negative to its value but I accept others may be happy to partake.

cereberus said:

The problem with your opinion is that it is predicated on the assumption that if those development resources were assigned to the Fast Ring, one would see a benefit in improved FR reliability. Life just does not work like that.

It is like proverbs - for every proverb, there is a counter proverb.

For moving resources "Many hands make light work".

Against "Too many cooks spoil the broth".

I also bet the the Skippy Developers would consider bug bashing as beneath them and for juniors.

IMO whether skippy exists or not, I doubt moving resources will have any benefit.

In the end, as a user, you do not have to partake in Skippy - I tend to be negative to its value but I accept others may be happy to partake.

My point was that, they have too many code monkeys writing new stuff, when there's a lot that needs to be made a lot more reliable. They are constantly adding new half baked features to Windows without ever completing the previous ones. And if there's a new feature that breaks 25 other features, then there's something wrong with the code or even the code writer.


A lot of development is happening in Windows but it seems to get nowhere. The core and absolutely mandatory features should be rock solid, no matter what you throw at it. Now they just break more and more code without fixing what they have broken before breaking even more code.