Home

To Clarify Betas as Default vs Non-beta.

%3CLINGO-SUB%20id%3D%22lingo-sub-805714%22%20slang%3D%22en-US%22%3ETo%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-805714%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20oft%20feels%20that%20there%20may%20be%20some%20misunderstanding%20floating%20about%20which%2C%20surrounds%20betas%20vs%20non-betas.%20I%20will%20address%20my%20concern%20thusly%2C%20to%20keep%20it%20simple%20%26amp%3B%20clear%20(I%20hope).%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20run%20Windows%2010.%26nbsp%3B%20It%20is%20not%20a%20beta.%26nbsp%3B%20Some%20people%2C%20myself%20included%2C%20are%20Windows%20Insiders%20and%20the%20Builds%20we%20run%20are%20betas.%26nbsp%3B%20And%20we%2C%20always%2C%20tell%20Folks%20do%20not%20run%20a%20beta%20OS%20on%20a%20'production%20machine'.%26nbsp%3B%20Why%3F%26nbsp%3B%20Because%2C%20they%20may%20have%20things%20wrong%20with%20them%2C%20things%20may%20not%20work%20on%20them%20or%20they%20crash%20or%20are%20unstable.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20browser%20we%20use%20in%20Win10%20is%20Edge%20and%20it%20is%20not%20a%20beta.%26nbsp%3B%20Nor%20does%20it%20need%20to%20downloaded%20%26amp%3B%20installed%20because%20it%20is%20an%20integral%20part%20of%20the%20OS%2C%20the%20Default%20browser.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ENow%20we%20have%20Edge%20Chromium%20%3CEM%3EChannels%3B%20%3C%2FEM%3E2%20now%20%26amp%3B%20soon%2C%203.%20%3CSTRONG%3EThey%20are%20all%20betas!%3C%2FSTRONG%3E%26nbsp%3B%20In%20due%20course%2C%20Edge%20(C)%20will%20replace%20Edge%20in%20the%20OS%20as%20its%20Default%20browser%20and%20that%20will%20not%20be%20beta.%3CBR%20%2F%3E%3CBR%20%2F%3ECaveat%20here%20is%2C%20if%20one%20%26gt%3B%20Settings%20%26amp%3B%20sets%20the%20Default%20browser%20to%20be%20an%20Edge%20(C)%20Channel%20(Canary%2C%20Dev%20or%20Beta%20-%26nbsp%3B%20%3CEM%3EOh%20no%2C%20calling%20one%20Beta%20won't%20be%20confusing%20to%20anyone%3C%2FEM%3E)%2C%20instead%20of%20Edge%2C%20that's%20cool%2C%20but%2C%20the%20Edge%20C%20is%2C%20still%2C%20a%20beta%20version%20which%2C%20is%20not%2C%20actually%20or%20yet%2C%20baked%20into%20the%20OS.%20A%20beta%20browser%20has%20been%20designated%20to%20be%20used%20as%20the%20'default%20browser'.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20when%20someone%20is%20asking%20or%20wonder%20when%20(new)%20Edge%20will%20be%20release%20or%20DONE...%20betas%20are%20not%20that.%26nbsp%3B%20Because%20one%20has%20set%20a%20beta%20Edge%20Build%20as%20default%20browser%20simply%20means%20their%20default%20browser%20is%20a%20version%20of%20a%20beta%20browser.%3CBR%20%2F%3E%3CBR%20%2F%3ESome%20of%20us%20suspect%20the%20'real'%20(new)%20Edge%20to%20be%20pushed%20out%20w%2F%201909.%26nbsp%3B%20For%20now%2C%20enjoy%20these%20betas%2C%20be%20they%20set%20to%20Default%20browser%20or%20not.%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%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%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%2F127047i842FDB713851B2D1%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%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-806367%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-806367%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316824%22%20target%3D%22_blank%22%3E%40Drew1903%3C%2FA%3E%26nbsp%3B%22%3CEM%3ENow%20we%20have%20Edge%20Chromium%26nbsp%3BChannels%3B%26nbsp%3B2%20now%20%26amp%3B%20soon%2C%203.%26nbsp%3B%3CSTRONG%3EThey%20are%20all%20betas!%3C%2FSTRONG%3E%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20strict%20technical%20sense%2C%20Drew%2C%20you%20are%20correct.%20Traditional%20software%20development%20nomenclature%20describes%20in-house%20testing%20versions%20of%20developing%20software%20as%20%22alpha%22%20and%20developing%20software%20distributed%20to%20an%20outside%20group%20for%20testing%20as%20%22beta%22.%20Beta%20software%20used%20to%20be%20distributed%20only%20to%20developers%2C%20reserving%20%22near%20final%22%20releases%20for%20testing%20by%20a%20more%20general%20population%20of%20outside%20testers.%3C%2FP%3E%3CP%3EIn%20more%20recent%20times%2C%20Microsoft%20and%20Google%20started%20to%20use%20outsiders%20to%20test%20software%20at%20earlier%20stages%20in%20the%20development%20process%2C%20using%20outsiders%20to%20do%20much%20of%20the%20%22alpha%22%20work%20that%20was%20previously%20done%20in-house.%20While%20that%20saves%20Microsoft%20and%20Google%20a%20lot%20of%20money%2C%20that%20also%20renders%20the%20strict%20technical%20sense%20of%20%22alpha%22%20and%20%22beta%22%20less%20meaningful%20and%20less%20important.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20read%20the%20same%20comments%20you%20have%20on%20this%20Forum%2C%20comments%20to%20the%20effect%20that%20%22Edge%20Chromium%20is%20%3CEM%3Ealpha%3C%2FEM%3Esoftware%20at%20this%20point%20...%22%2C%20meaning%20that%20the%20builds%20are%20as%20buggy%20as%20can%20be%20and%20nowhere%20near%20ready%20for%20prime%20time%20release.%20I%20don't%20have%20a%20problem%20with%20that.%20Language%20changes%20over%20time%2C%20and%20given%20the%20new%20protocols%20of%20software%20testing%2C%20releasing%20software%20to%20outside%20testing%20at%20stages%20when%20it%20would%20have%20formerly%20been%20considered%20%22alpha%22%20and%20testing%20in-house%2C%20I%20suspect%20that%20it%20is%20the%20strict%20technical%20nomenclature%20that%20is%20out%20of%20whack%20with%20reality%2C%20not%20the%20colloquial%20sense%20used%20in%20this%20forum.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%3E%3CEM%3ESome%20of%20us%20suspect%20the%20'real'%20(new)%20Edge%20to%20be%20pushed%20out%20w%2F%201909.%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EEdge%20Chromium%20is%20not%2C%20to%20my%20knowledge%2C%20baked%20into%2019H2%20at%20this%20point%2C%20and%20that%20release%20is%2C%20according%20to%20Microsoft%2C%20scheduled%20for%20wrap-up%20next%20month.%26nbsp%3B%20%26nbsp%3BNothing%2C%20as%20far%20as%20I%20know%2C%20suggests%20that%2019H2%20is%20going%20to%20include%20Edge%20Chromium.%26nbsp%3B%20What%20are%20you%20seeing%20that%20the%20rest%20of%20us%20(including%20the%20trade%20press)%20are%20not%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20Microsoft%20intends%20to%20roll%20out%20Edge%20Chromium%20with%2019H2%2C%20Microsoft%20had%20better%20get%20busy%20if%20it%20wants%20to%20avoid%20serious%20and%20accurate%20criticism%20about%20a%20botched%20release.%26nbsp%3B%20The%20versions%20we%20are%20testing%20are%20not%20ready%20for%20prime%20time.%26nbsp%3B%20Do%20you%20really%20think%20that%20Microsoft%20will%20have%20Edge%20Chromium%20ready%20to%20go%20in%20less%20than%20a%20month%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-806521%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-806521%22%20slang%3D%22en-US%22%3E%3CP%3ERight.%20Plus%20with%20Beta's%20and%20Alphas%20(as%20sometimes%20called)%20they%20sometimes%20continue%20in%20public%20beta%20even%20after%20the%20stable%20version%20is%20release.%20Meaning%20the%20public%20beta%20testing%20doesn't%20always%20just%20end%2C%20and%20that's%20it%20as%20some%20stable%20software%2Fapps%20are%20always%20being%20updated%20itself.%20Once%20Edge%20stable%20is%20released%20it'll%20be%20updated%2Fimproved%20every%20few%20weeks%20or%20months%20or%20whenever%20they%20opt%20to%20do%20it%20as%20all%20other%20stable%20browsers%20do.%20I'm%20a%20beta%20insider%20for%20Edge%20for%20Android.%20I%20get%20the%20beta%20versions%20when%20they're%20release%20to%20the%20Google%20Play%20Store.%26nbsp%3B%20(If%20you%20go%20to%20the%20Google%20Play%20store%2C%20search%20and%20click%20for%20Edge%2C%20and%20scroll%20down%20more%20towards%20the%20bottom%20you%20might%20see%20an%20option%20that%20say's%20%22Join%20Beta%22%20in%20which%20case%20if%20you%20do%20you'll%20get%20the%20stable%20release%20and%20the%20in-between%20beta%20releases%20of%20Android%20Edge).%26nbsp%3B%20I've%20been%20using%20Google%20Chrome%20Canary%20for%20years%20as%20a%20secondary%20browser%20and%20Google%20Chrome%20has%20since%202011%20the%20same%20Canary%2C%20Developer%2C%20Beta%2C%20Stable%20options%20as%20Edge%20does.%20Firefox%20has%20Firefox%20Nightly%20(their%20version%20of%20Canary)%20and%20Firefox%20Beta%20(their%20version%20of%20Developer%20since%20Firefox%20Aurora%20was%20discontinued)%20on%20top%20of%20Stable.%20I%20sometimes%20refer%20to%20Canary%20as%20%22the%20beta%20of%20the%20beta%20of%20the%20beta%22%20hehe.%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20don't%20know%20when%20Edge%20will%20be%20released%20into%20stable.%20The%20Beta%20channel%20hasn't%20yet%20been%20released%20and%20that%20alone%20states%20after%20the%20Beta%20Channel%20(Beta%20Version)%20is%20released%20it%20will%20be%20updated%20every%20six%20weeks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-807178%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-807178%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ETom%2C%20precisely%20due%20to%20what%20stage%20things%20are%20at%2C%20now...%20I%20suggested%20there%20is%20no%20way%20it%20would%20be%20ready%20before%201909.%26nbsp%3B%20I%20am%20not%20%22seeing%22%20anything%2C%20it's%20a%20hunch.%26nbsp%3B%20I%2C%20also%2C%20thought%2C%20on%20the%20occasions%20where%20this%20was%20being%20discussed%2C%20I%20had%20said%20or%20meant%20to%20imply%2C%20not%20before%201909%20%26amp%3B%20maybe%2C%20after.%20And%201909%20goes%20out%20in%20October%20so%2C%20maybe.%26nbsp%3B%20Excuse%20if%20you%20misunderstood%2C%20I%20have%20never%20said%20along%20w%2F%201909%20was%20etched%20in%20stone%2C%20just%20a%20possibility...%20Mostly%2C%20it%20was%20telling%20people%20that%20Edge%20C%20would%20definitely%20NOT%20be%20anything%20before%20the%20Fall%2C%20at%20least.%26nbsp%3B%20I%20recall%20at%20the%20same%20times%20reminding%20people%20the%20Beta%20Channel%20isn't%20even%20available%2C%20yet%2C%20when%20they%20have%20asked%2C%20%22When%20will%20this%20browser%20be%20released%3F%22%26nbsp%3B%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%2F127183i8736E8148E4A82DB%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-807215%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-807215%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F373791%22%20target%3D%22_blank%22%3E%40ItalianAce%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EYes%2C%20and%20for%20the%20moment%20I%20was%20purposely%20staying%20away%20from%20the%20'continues%20after%20release'%20part.%26nbsp%3B%20I'm%20sure%20it%20can%20be%20confusing%20for%20some%20Folks.%26nbsp%3B%20I%20happen%20to%20be%20an%20Edge%2C%20Bing%2C%20Office%20%26amp%3B%20Windows%20Insider%20so%20I%20certainly%20know%20of%20what%20you%20speak.%26nbsp%3B%20Certainly%2C%20Win10%20Insider%20Builds%20are%20a%20perfect%20example.%20For%20Windows%20this%20has%20been%20the%20case%20w%2F%20Operating%20Systems%2C%20it's%20a%201st%20for%20a%20MS%20browser...%20But%2C%20seem%20to%20do%20it%20w%2F%20lots%20of%20software%20these%20days%2C%20involve%20public%20%26amp%3B%20corp%20(pre)%20testers.%26nbsp%3B%20It%20well%20be%20the%20case%20will%20Edge%20C.%26nbsp%3B%20I%20just%20wanted%20to%20sure%20people%20were%20grasping%20that%20%3CU%3Ecurrently%3C%2FU%3Eif%20one%20of%20the%20Edge%20C%20Channels%20is%20set%20as%20their%20%22Default%20browser%22%20that%20it%20is%2C%20still%2C%20running%20a%20beta%20(version)%20browser.%26nbsp%3B%20The%20non-beta%20release%20will%20come%20in%20due%20time.%3CBR%20%2F%3E%3CBR%20%2F%3EMaybe%2C%20this%20helps%20explain%20it...%20Help%20Desks%20(usually)%20do%20not%20offer%20Tech%20Support%20for%20beta%20anything.%26nbsp%3B%20As%20a%20matter%20of%20fact%2C%20for%20example%2C%20MS%20Help%20Desk%20will%20not%2Fdoes%20not%20offer%20support%20for%20Win10%20Insider%20Builds%20(they%20are%20betas).%3CBR%20%2F%3E%3CBR%20%2F%3EThere%20is%20Support%20for%20Edge%20not%2C%20for%20Edge%20C%2C%20%3CEM%3Eyet%3B%20%3C%2FEM%3Enot%20until%20it's%20non-beta.%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%2F127185iB0FE52CA24560699%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-807435%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-807435%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316824%22%20target%3D%22_blank%22%3E%40Drew1903%3C%2FA%3E%26nbsp%3B%20Sorry%2C%20I%20did%20misunderstand%2C%20apparently.%26nbsp%3B%20I%20thought%20you%20were%20suggesting%20that%20Edge%20Chromium%20would%20be%20released%20with%2019H1%3A%20%22%3CSPAN%3E%3CEM%3ESome%20of%20us%20suspect%20the%20'real'%20(new)%20Edge%20to%20be%20pushed%20out%20w%2F%201909.%3C%2FEM%3E%22%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EObviously%2C%20that%20is%20not%20going%20to%20be%20the%20case.%26nbsp%3B%20%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EThe%20first%20Beta%20channel%20version%20hasn't%20been%20released%20yet%2C%20and%20since%20Microsoft%20seems%20to%20anticipate%20several%20Beta%20updates%20(%22%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoftedgeinsider.com%2Fen-us%2Fdownload%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EBeta%20Channel%26nbsp%3BUpdated%20every%206%20weeks%3C%2FA%3E%22)%2C%20there%20just%20aren't%20enough%20days%20in%20the%20calendar%20for%20Edge%20Chromium%20to%20be%20%22pushed%20out%20w%2F%201909%22%2C%20whether%20or%20not%20it%20is%20part%20of%20the%2019H1%20release%20or%20independent.%26nbsp%3B%20%26nbsp%3BEven%20if%20there%20are%20only%20%3CSTRONG%3Etwo%3C%2FSTRONG%3EBeta%20updates%2C%20that%20pushes%20the%20earliest%20possible%20release%20date%20into%20mid-November.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20personally%20hope%20that%20Microsoft%20takes%20its%20time%20and%20doesn't%20push%20Edge%20Chromium%20out%20until%20it%20is%20100%25%20ready.%26nbsp%3B%20There%20is%20no%20particular%20urgency%2C%20and%20I%20don't%20think%20that%20Edge%20Chromium%20will%20survive%20if%20the%20product%20is%20not%20fully%20featured%20and%20working%20perfectly%2C%20both%20for%20consumers%2C%20and%20more%20importantly%20perhaps%2C%20for%20business%20and%20enterprise%20users.%26nbsp%3B%20%26nbsp%3BEdge%20Chromium%20has%20to%20be%20flawless%20when%20released.%26nbsp%3B%20EdgeHTML%20got%20an%20early%20reputation%20for%20problems%20and%20it%20never%20recovered.%26nbsp%3B%20Microsoft%20can't%20afford%20that%20this%20time%20around.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-807616%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-807616%22%20slang%3D%22en-US%22%3ETrue%2C%20did%20write%2C%20suspect%20not%2C%20would%20be.%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20for%20your%202nd%20paragraph%2C%20I%20absolutely%20agree%20100%25.%20It%20is%20the%20only%20way%20it%20should%20be.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%2C%20since%20we%2C%20really%2C%20don't%20know%20the%20time%20span%2C%20I%2C%20honestly%20just%20try%20to%20offer%20some%20kind%20of%20response%20to%20all%20those%20asking%2C%20%E2%80%9CWhen%2C%20when%2C%20when%3F%3F%E2%80%9D%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3EDrew%3CBR%20%2F%3E%3CBR%20%2F%3ESent%20from%20Windows%20Phone%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-808230%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-808230%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316824%22%20target%3D%22_blank%22%3E%40Drew1903%3C%2FA%3E%26nbsp%3B%20%26nbsp%3B%22%3CSPAN%3E%3CEM%3EAnd%2C%20since%20we%2C%20really%2C%20don't%20know%20the%20time%20span%2C%20I%2C%20honestly%20just%20try%20to%20offer%20some%20kind%20of%20response%20to%20all%20those%20asking%2C%20%E2%80%9CWhen%2C%20when%2C%20when%3F%3F%3C%2FEM%3E%E2%80%9D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHow%20about%20%22I%20don't%20know.%20%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-809528%22%20slang%3D%22en-US%22%3ERe%3A%20To%20Clarify%20Betas%20as%20Default%20vs%20Non-beta.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-809528%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20working%20at%20a%20different%20work%20side%20yesterday%20at%20my%20job%2C%20that%20required%20using%20someone%20else's%20computer%20which%20only%20had%20the%20original%2Fold%20Edge.%20Using%20the%20original%20Edge%20I%20was%20reminded%20how%20much%20better%20and%20nicer%20the%20new%20Edge%20C%20is.%20I%20haven't%20used%20the%20old%20Edge%20since%20using%20Edge%20Canary.%20The%20old%20Edge%20was%20nice%2C%20but%20having%20been%20using%20the%20chromium%20Edge%20even%20in%20it's%20beta%20as%20my%20default%20browser%20I've%20gotten%20too%20spoiled%20with%20it.%26nbsp%3B%20I%20can%20only%20see%20each%20Beta%20getting%20better%20and%20better%20and%20setting%20up%20a%20proper%20and%20stable%20prime%20release.%20Although%20I%20also%20understand%20and%20see%20people's%20side%20of%20wanting%20to%20get%20the%20new%20Edge%20C%20in%20prime%20as%20soon%20as%20possible%20so%20they%20can%20make%20a%20full%20break%20from%20the%20old%20Edge.%20Or%20make%20a%20full%20break%20from%20other%20browsers%20like%20Firefox%20or%20Opera.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Drew1903
Valued Contributor

It oft feels that there may be some misunderstanding floating about which, surrounds betas vs non-betas. I will address my concern thusly, to keep it simple & clear (I hope).  

We run Windows 10.  It is not a beta.  Some people, myself included, are Windows Insiders and the Builds we run are betas.  And we, always, tell Folks do not run a beta OS on a 'production machine'.  Why?  Because, they may have things wrong with them, things may not work on them or they crash or are unstable.

The browser we use in Win10 is Edge and it is not a beta.  Nor does it need to downloaded & installed because it is an integral part of the OS, the Default browser. 

Now we have Edge Chromium Channels; 2 now & soon, 3. They are all betas!  In due course, Edge (C) will replace Edge in the OS as its Default browser and that will not be beta.

Caveat here is, if one > Settings & sets the Default browser to be an Edge (C) Channel (Canary, Dev or Beta -  Oh no, calling one Beta won't be confusing to anyone), instead of Edge, that's cool, but, the Edge C is, still, a beta version which, is not, actually or yet, baked into the OS. A beta browser has been designated to be used as the 'default browser'.

So when someone is asking or wonder when (new) Edge will be release or DONE... betas are not that.  Because one has set a beta Edge Build as default browser simply means their default browser is a version of a beta browser.

Some of us suspect the 'real' (new) Edge to be pushed out w/ 1909.  For now, enjoy these betas, be they set to Default browser or not.

Cheers,
Drew
thVY64FD02.jpg





8 Replies

@Drew1903 "Now we have Edge Chromium Channels; 2 now & soon, 3. They are all betas!"

 

In the strict technical sense, Drew, you are correct. Traditional software development nomenclature describes in-house testing versions of developing software as "alpha" and developing software distributed to an outside group for testing as "beta". Beta software used to be distributed only to developers, reserving "near final" releases for testing by a more general population of outside testers.

In more recent times, Microsoft and Google started to use outsiders to test software at earlier stages in the development process, using outsiders to do much of the "alpha" work that was previously done in-house. While that saves Microsoft and Google a lot of money, that also renders the strict technical sense of "alpha" and "beta" less meaningful and less important.

 

I've read the same comments you have on this Forum, comments to the effect that "Edge Chromium is alpha software at this point ...", meaning that the builds are as buggy as can be and nowhere near ready for prime time release. I don't have a problem with that. Language changes over time, and given the new protocols of software testing, releasing software to outside testing at stages when it would have formerly been considered "alpha" and testing in-house, I suspect that it is the strict technical nomenclature that is out of whack with reality, not the colloquial sense used in this forum.

 

"Some of us suspect the 'real' (new) Edge to be pushed out w/ 1909."

 

Edge Chromium is not, to my knowledge, baked into 19H2 at this point, and that release is, according to Microsoft, scheduled for wrap-up next month.   Nothing, as far as I know, suggests that 19H2 is going to include Edge Chromium.  What are you seeing that the rest of us (including the trade press) are not?

 

If Microsoft intends to roll out Edge Chromium with 19H2, Microsoft had better get busy if it wants to avoid serious and accurate criticism about a botched release.  The versions we are testing are not ready for prime time.  Do you really think that Microsoft will have Edge Chromium ready to go in less than a month?

 

 

 

 

 

 

Right. Plus with Beta's and Alphas (as sometimes called) they sometimes continue in public beta even after the stable version is release. Meaning the public beta testing doesn't always just end, and that's it as some stable software/apps are always being updated itself. Once Edge stable is released it'll be updated/improved every few weeks or months or whenever they opt to do it as all other stable browsers do. I'm a beta insider for Edge for Android. I get the beta versions when they're release to the Google Play Store.  (If you go to the Google Play store, search and click for Edge, and scroll down more towards the bottom you might see an option that say's "Join Beta" in which case if you do you'll get the stable release and the in-between beta releases of Android Edge).  I've been using Google Chrome Canary for years as a secondary browser and Google Chrome has since 2011 the same Canary, Developer, Beta, Stable options as Edge does. Firefox has Firefox Nightly (their version of Canary) and Firefox Beta (their version of Developer since Firefox Aurora was discontinued) on top of Stable. I sometimes refer to Canary as "the beta of the beta of the beta" hehe.  

I don't know when Edge will be released into stable. The Beta channel hasn't yet been released and that alone states after the Beta Channel (Beta Version) is released it will be updated every six weeks. 

@tomscharbach 

Tom, precisely due to what stage things are at, now... I suggested there is no way it would be ready before 1909.  I am not "seeing" anything, it's a hunch.  I, also, thought, on the occasions where this was being discussed, I had said or meant to imply, not before 1909 & maybe, after. And 1909 goes out in October so, maybe.  Excuse if you misunderstood, I have never said along w/ 1909 was etched in stone, just a possibility... Mostly, it was telling people that Edge C would definitely NOT be anything before the Fall, at least.  I recall at the same times reminding people the Beta Channel isn't even available, yet, when they have asked, "When will this browser be released?" 

Cheers,
Drew
thVY64FD02.jpg

@ItalianAce 

Yes, and for the moment I was purposely staying away from the 'continues after release' part.  I'm sure it can be confusing for some Folks.  I happen to be an Edge, Bing, Office & Windows Insider so I certainly know of what you speak.  Certainly, Win10 Insider Builds are a perfect example. For Windows this has been the case w/ Operating Systems, it's a 1st for a MS browser... But, seem to do it w/ lots of software these days, involve public & corp (pre) testers.  It well be the case will Edge C.  I just wanted to sure people were grasping that currently if one of the Edge C Channels is set as their "Default browser" that it is, still, running a beta (version) browser.  The non-beta release will come in due time.

Maybe, this helps explain it... Help Desks (usually) do not offer Tech Support for beta anything.  As a matter of fact, for example, MS Help Desk will not/does not offer support for Win10 Insider Builds (they are betas).

There is Support for Edge not, for Edge C, yet; not until it's non-beta.

Cheers,
Drew
thVY64FD02.jpg

@Drew1903  Sorry, I did misunderstand, apparently.  I thought you were suggesting that Edge Chromium would be released with 19H1: "Some of us suspect the 'real' (new) Edge to be pushed out w/ 1909.

 

Obviously, that is not going to be the case.   The first Beta channel version hasn't been released yet, and since Microsoft seems to anticipate several Beta updates ("Beta Channel Updated every 6 weeks"), there just aren't enough days in the calendar for Edge Chromium to be "pushed out w/ 1909", whether or not it is part of the 19H1 release or independent.   Even if there are only two Beta updates, that pushes the earliest possible release date into mid-November.

 

I personally hope that Microsoft takes its time and doesn't push Edge Chromium out until it is 100% ready.  There is no particular urgency, and I don't think that Edge Chromium will survive if the product is not fully featured and working perfectly, both for consumers, and more importantly perhaps, for business and enterprise users.   Edge Chromium has to be flawless when released.  EdgeHTML got an early reputation for problems and it never recovered.  Microsoft can't afford that this time around.

True, did write, suspect not, would be.

As for your 2nd paragraph, I absolutely agree 100%. It is the only way it should be.

And, since we, really, don't know the time span, I, honestly just try to offer some kind of response to all those asking, “When, when, when??”

Cheers,
Drew

Sent from Windows Phone

@Drew1903   "And, since we, really, don't know the time span, I, honestly just try to offer some kind of response to all those asking, “When, when, when??

 

How about "I don't know. "

I was working at a different work side yesterday at my job, that required using someone else's computer which only had the original/old Edge. Using the original Edge I was reminded how much better and nicer the new Edge C is. I haven't used the old Edge since using Edge Canary. The old Edge was nice, but having been using the chromium Edge even in it's beta as my default browser I've gotten too spoiled with it.  I can only see each Beta getting better and better and setting up a proper and stable prime release. Although I also understand and see people's side of wanting to get the new Edge C in prime as soon as possible so they can make a full break from the old Edge. Or make a full break from other browsers like Firefox or Opera.