Home

Universal OR NOT - An explanation

%3CLINGO-SUB%20id%3D%22lingo-sub-919371%22%20slang%3D%22en-US%22%3EUniversal%20OR%20NOT%20-%20An%20explanation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-919371%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20do%20I%20mean%20by%20%22universal%22.%26nbsp%3B%20Will%20apply%20it%20in%203%20spheres.%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20So-called%20'bugs'%20may%26nbsp%3B%3CEM%3Enot%26nbsp%3B%3C%2FEM%3Ebe%20universal%3B%20will%20not%20necessarily%20be%20seen%20by%20or%20affect%20every%20machine%20or%20User.%26nbsp%3B%20May%2C%20still%2C%20be%20a%20valid%20'bug'%20even%20if%20not%20showing%20on%20an%20individual%20basis.%3CBR%20%2F%3E%3CBR%20%2F%3E2.%20And%20this%20involves%20both%20fixes%20%26amp%3B%20features.%26nbsp%3B%20%3CSTRIKE%3EUniversal%3C%2FSTRIKE%3E%26nbsp%3BSimultaneous%20is%20%3CU%3Eoften%3C%2FU%3E%20not%20the%20case.%26nbsp%3B%20Fixes%20may%20not%20hit%20all%20Users%20or%20devices%20simultaneously.%26nbsp%3B%20And%20features%20contained%20in%20updates%20VERY%20often%20do%20not%20go%20out%20to%20ALL%20simultaneously.%26nbsp%3B%20And%2C%20that's%20not%20even%20counting%20intended%20%22Controlled%20Feature%20Roll-outs%22.%3CBR%20%2F%3E%3CBR%20%2F%3E3.%20Is%20Region%20%26amp%3B%20Language%3A%20When%20we%20are%20working%20with%20Microsoft%2C%20based%20in%20the%20US%20%26amp%3B%20using%20English%2C%20beta%20products%20will%20be%20just%20that.%26nbsp%3B%20This%20is%20true%20of%20the%20OS%20(Windows)%20and%20the%20browser%20(Edge).%26nbsp%3B%20This%20aspect%20becomes%20more%20universal%20as%20the%20Global%26nbsp%3B%20roll-out%20for%20locals%20%26amp%3B%20tongues%20in%20said%20project%20widens%20%26amp%3B%20broadens%20over%20time.%3CBR%20%2F%3E%3CBR%20%2F%3ECaveat%20here%20is%2C%20when%20working%20with%20betas%20don't%20expect%20universality%20or%20Global%2C%20simultaneous%20pushes%20or%20reception%20of%20things.%26nbsp%3B%20Plus%2C%20things%20can%20%26amp%3B%20do%20hit%20snags%20%26amp%3B%20delays%20when%20deployed%2C%20again%2C%20not%20meeting%20expectations.%26nbsp%3B%20Moral%20being%2C%20don't%20(ever)%20expect%20perfection%2C%20predictable%20timing%2C%20Global%20impact%2C%20a%20polished%2C%20finished%20product%20or%20universality%20throughout%20the%20process%20of%20working%20with%20betas.%3CBR%20%2F%3E%3CBR%20%2F%3ENot%20preaching%20or%20lecturing%2C%20just%2C%20the%20thoughts%20MIGHT%20be%20worth%20sharing%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20113px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F138553i8E6CA8F27D1091EB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22thVY64FD02.jpg%22%20title%3D%22thVY64FD02.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-919455%22%20slang%3D%22en-US%22%3ERe%3A%20Universal%20OR%20NOT%20-%20An%20explanation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-919455%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%3CSTRONG%3Eonly%3C%2FSTRONG%3E%20factor%20that%20can%20cause%20a%20%3CSTRONG%3EBug%3C%2FSTRONG%3E%20not%20be%20experienced%20by%20everyone%20is%20%3CSTRONG%3EControlled%20feature%20roll%20outs.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EWhich%20is%20the%20fact%20that%20Edge%20insiders%20users%20are%20put%20into%20different%20select%20groups%20(one%20factor%20is%20by%20geography)%20and%20they%20are%20rolled%20out%20different%20features%20that%20are%20not%20available%20to%20other%20groups%2C%20thus%20making%20their%20version%20of%20browsers%20different.%20But%2C%20%3CSTRONG%3EBugs%20are%20Bugs%3C%2FSTRONG%3E%2C%20no%20one%20can%20downplay%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Drew1903
Trusted Contributor

What do I mean by "universal".  Will apply it in 3 spheres.

1. So-called 'bugs' may not be universal; will not necessarily be seen by or affect every machine or User.  May, still, be a valid 'bug' even if not showing on an individual basis.

2. And this involves both fixes & features.  Universal Simultaneous is often not the case.  Fixes may not hit all Users or devices simultaneously.  And features contained in updates VERY often do not go out to ALL simultaneously.  And, that's not even counting intended "Controlled Feature Roll-outs".

3. Is Region & Language: When we are working with Microsoft, based in the US & using English, beta products will be just that.  This is true of the OS (Windows) and the browser (Edge).  This aspect becomes more universal as the Global  roll-out for locals & tongues in said project widens & broadens over time.

Caveat here is, when working with betas don't expect universality or Global, simultaneous pushes or reception of things.  Plus, things can & do hit snags & delays when deployed, again, not meeting expectations.  Moral being, don't (ever) expect perfection, predictable timing, Global impact, a polished, finished product or universality throughout the process of working with betas.

Not preaching or lecturing, just, the thoughts MIGHT be worth sharing

Cheers,
Drew
thVY64FD02.jpg

1 Reply

The only factor that can cause a Bug not be experienced by everyone is Controlled feature roll outs.

Which is the fact that Edge insiders users are put into different select groups (one factor is by geography) and they are rolled out different features that are not available to other groups, thus making their version of browsers different. But, Bugs are Bugs, no one can downplay them.