Me musing about the road ahead

%3CLINGO-SUB%20id%3D%22lingo-sub-1025533%22%20slang%3D%22en-US%22%3EMe%20musing%20about%20the%20road%20ahead%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1025533%22%20slang%3D%22en-US%22%3E%3CP%3EAlways%20ahead%20of%20a%20product%20release%20there%20is%20speculation%2C%20rumour%20%26amp%3B%20various%20things%20in%20'print'.%20Depending%20on%20the%20source%2C%20Edge%20HTML%20is%20being%20replace%20by%20Edge%20Chromium%20OR%20there%20will%20be%20both.%20And%20the%20analogy%20of%20IE%20has%20been%20used%20to%20support%20the%20idea%20that%202%20Edges%20will%20exist.%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20own%20thought%20is%20the%20same%20grounds%20or%20rational%26nbsp%3B%20do%20not%20exist%20or%20apply%20to%20both%20scenarios.%26nbsp%3B%20There%20was%20a%20reason%20for%20IE%20lingering%20around%20after%20Edge%20arrived...%20Enterprise.%20Same%20reason%20Enterprise%20is%20being%20given%20IE%20Mode%20with%20Edge%20C.%26nbsp%3B%20Enterprise%20has%20old%20legacy%20software%20that%20only%20plays%20nicely%20with%20IE.%26nbsp%3B%20Such%20is%20not%20the%20case%20with%20Edge%3B%20same%20software%20works%20with%20Edge%20%231%20%26amp%3B%20or%20Edge%20%232.%20No%20need%20for%20the%20previous%20one%20%26amp%3B%20no%20need%20for%20two.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20other%20similarity%20there%20would%20be%20is%20'confusion'.%20Meaning%20some%20people%20seem%20confused%20about%20using%20Edge%20or%20sticking%20to%20old%20IE%2C%20even%2C%20though%20they%20are%20VERY%20different%20on%20every%20level%20%26amp%3B%20even%20though%2C%20in%20theory%20Edge%20is%20the%20better.%26nbsp%3B%20Now%2C%20Edge%20C%20is%20to%20be%20better.%20So%2C%20if%20%232%20is%20better%20than%20%231%20and%20the%20issue%20of%20certain%20programs%20only%20running%20on%20%231%20doesn't%20apply...%20no%20confusion%2C%20have%20only%20the%20New%20%26amp%3B%20Improved.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1026867%22%20slang%3D%22en-US%22%3ERe%3A%20Me%20musing%20about%20the%20road%20ahead%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1026867%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%20The%20one%20thing%20that%20we%20can%20be%20certain%20about%20is%20that%20at%20least%20half%20of%20what%20we%20read%20in%20the%20trade%20press%20is%20dead%20wrong.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20has%20made%20statements%20that%20there%20will%20be%20a%20transition%2C%20and%20that%20that%20at%20some%20point%20both%20EdgeClassic%20and%20IE%20will%20be%20removed%20from%20Windows%26nbsp%3B%3CEM%3Econsumer%3C%2FEM%3E%20builds%20(that%20is%2C%20Home%20and%20Pro)%2C%20but%20has%20given%20no%20timetable.%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20complicating%20factor%20is%20that%20Microsoft%20has%20said%20that%20%22IE11%20will%20continue%20to%20be%20supported%20on%20the%20lifecycle%20of%20the%20OS.%22%26nbsp%3B%20%26nbsp%3BI%20understand%20what%20that%20means%20in%20the%20case%20of%20Windows%207%20and%208%2F8.1%2C%20which%20have%20limited%2C%20defined%20end-of-support%20cycles%20(Windows%207%20support%20ends%20shortly%2C%20and%20Windows%208%2F8.1%20support%20ends%20in%202022%2F23)%2C%20but%20I'm%20not%20sure%20what%20that%20means%20in%20the%20case%20of%20Windows%2010.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Enterprise%20situation%20is%20even%20less%20clear%20because%20Microsoft%20has%20contractual%20obligations%20to%20Enterprise%20customers%20that%20may%20override%20other%20considerations.%26nbsp%3B%20I%20have%20read%20Microsoft%20statements%20that%20suggest%20that%20IE%20may%20continue%20to%20be%20embedded%20in%20Enterprise%20versions%20of%20Windows%2010%20for%20several%20years.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20will%20undoubtedly%20find%20out%20more%20about%20the%20timetable%20going%20forward%2C%20but%20it%20seems%20obvious%20that%20there%20will%20be%20a%20period%20during%20which%20EdgeClassic%20and%20IE%20will%20continue%20to%20be%20options%20for%20both%20consumers%20and%20Enterprise%20customers.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20case%20of%20consumers%2C%20I%20would%20be%20surprised%20if%20either%20EdgeClassic%20or%20IE%20were%20removed%20from%20existing%20supported%20builds%20(currently%201809%2C%201903%2C%201909)%20while%20those%20builds%20are%20supported.%26nbsp%3B%20%26nbsp%3BI%20don't%20know%20what%20the%20situation%20is%20with%2020H1%2C%20but%20I'm%20a%20Windows%20Insider%20using%2020H1%2C%20and%20I've%20seem%20no%20signs%20at%20all%20that%20Microsoft%20intends%20to%20remove%20either%20EdgeClassic%20or%20IT%20from%20that%20build.%26nbsp%3B%20%26nbsp%3BIf%20Microsoft%20follows%20recent%20practice%2C%2020H2%20will%20be%20a%20service%20release%20(as%20is%2019H2%2C%20or%201909)%2C%20and%20while%20it%20possible%20that%2020H2%20will%20remove%20EdgeClassic%20and%20IE%2C%20it%20seems%20less%20than%20likely%20that%20Microsoft%20would%20make%20a%20change%20of%20that%20magnitude%20in%20a%20service%20release.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%2021H1%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1028192%22%20slang%3D%22en-US%22%3ERe%3A%20Me%20musing%20about%20the%20road%20ahead%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1028192%22%20slang%3D%22en-US%22%3EEdge%20classic%20will%20stay%20for%20a%20while%20for%20compatibility.%3C%2FLINGO-BODY%3E
Highlighted
Trusted Contributor

Always ahead of a product release there is speculation, rumour & various things in 'print'. Depending on the source, Edge HTML is being replace by Edge Chromium OR there will be both. And the analogy of IE has been used to support the idea that 2 Edges will exist.

My own thought is the same grounds or rational  do not exist or apply to both scenarios.  There was a reason for IE lingering around after Edge arrived... Enterprise. Same reason Enterprise is being given IE Mode with Edge C.  Enterprise has old legacy software that only plays nicely with IE.  Such is not the case with Edge; same software works with Edge #1 & or Edge #2. No need for the previous one & no need for two.

The other similarity there would be is 'confusion'. Meaning some people seem confused about using Edge or sticking to old IE, even, though they are VERY different on every level & even though, in theory Edge is the better.  Now, Edge C is to be better. So, if #2 is better than #1 and the issue of certain programs only running on #1 doesn't apply... no confusion, have only the New & Improved.

Cheers,
Drew 


2 Replies
Highlighted

@Drew1903  The one thing that we can be certain about is that at least half of what we read in the trade press is dead wrong.  

 

Microsoft has made statements that there will be a transition, and that that at some point both EdgeClassic and IE will be removed from Windows consumer builds (that is, Home and Pro), but has given no timetable.   

 

A complicating factor is that Microsoft has said that "IE11 will continue to be supported on the lifecycle of the OS."   I understand what that means in the case of Windows 7 and 8/8.1, which have limited, defined end-of-support cycles (Windows 7 support ends shortly, and Windows 8/8.1 support ends in 2022/23), but I'm not sure what that means in the case of Windows 10.

 

The Enterprise situation is even less clear because Microsoft has contractual obligations to Enterprise customers that may override other considerations.  I have read Microsoft statements that suggest that IE may continue to be embedded in Enterprise versions of Windows 10 for several years.

 

We will undoubtedly find out more about the timetable going forward, but it seems obvious that there will be a period during which EdgeClassic and IE will continue to be options for both consumers and Enterprise customers. 

 

In case of consumers, I would be surprised if either EdgeClassic or IE were removed from existing supported builds (currently 1809, 1903, 1909) while those builds are supported.   I don't know what the situation is with 20H1, but I'm a Windows Insider using 20H1, and I've seem no signs at all that Microsoft intends to remove either EdgeClassic or IT from that build.   If Microsoft follows recent practice, 20H2 will be a service release (as is 19H2, or 1909), and while it possible that 20H2 will remove EdgeClassic and IE, it seems less than likely that Microsoft would make a change of that magnitude in a service release.

 

Maybe 21H1?

Highlighted
Edge classic will stay for a while for compatibility.