Forum Discussion
Please! New Edge should not replace Legacy Edge automatically In January.
They have been given the feedback that relasing a basicly broken browser that removes functionallity we do use today is NOT a way to make us Enterprise customeers happy.
I spoke to Colleen about it Yesterday for example
As I have been saying for a long time.
* Needed functions must be implemented. For me that is
- The functions in the favorites menu must be ported
- Epub support must be ported
* THe GUI must be as close to Edge HTML as possible to minimize retraing costs.
* The GUI must remain unchanged after that since retraining costs huge amounts
To NOT fullfill this will only make the companies choose Chrome instead since it's a lot more mature browser
matsmcp "To NOT fullfill this will only make the companies choose Chrome instead since it's a lot more mature browser."
Be that as it may, unless you heard something different at Ignite 2019**, Microsoft is going ahead with the release/deployment, using Version 79 as the Release Candidate.
With respect to your point about training/dislocation costs, I've been the IT Director of an Enterprise customer, so I understand the point and I agree. The friends I talked to recently (in both cases, people I mentored in their IT careers) are worried about training/dislocation costs going forward, because of the refresh cycle used by Chromium-based browsers, including both EdgeChromium and Chrome. But both seem to believe that the cost of deploying two browsers (IE and EdgeClassic) outweigh the costs imposed by initial deployment dislocation and a rolling development cycle.
I don't mean to imply that Version 79 will actually be deployed by Enterprise customers. I don't think that it will be. Almost all will use the Release Candidate for integration testing and to prepare deployment/training plans/materials, but not deploy. In fact, I would be surprised if more than just a few Enterprise customers deployed EdgeChomium for six+ months after release. By that time EdgeChromium will have been materially improved.
We all have opinions. I personally think that Version 79 isn't ready for prime time. Microsoft obviously thinks that it is, and it is Microsoft's call, not mine.
================
**I'm not in attendance because I'm retired, but I've reviewed the videos of each session relevant to browser development.
I agree.
The list of missing features are to long.
There are too many outstanding bugs.
The testing is not done to a good level