Forum Discussion
Stable version of Edge insider browser
- Thanks for the discussion. We feel this has come to a natural conclusion, so we are closing this off to new comments - it's good to be aware of using content from other sites, but we do understand this was used to help make an argument rather than passing it off as your own content. But it doesn't seem like anything productive will come from further discussion here.
HotCakeX The so-called "Stable" version is almost certainly a build being used for internal testing, probably an internal build related to deployment testing, as was the last "Stable" version hosted on Microsoft servers. Because the build seems to embed into Windows 10 and replace Edge (Classic), Microsoft is probably testing with an eye to "replacement deployment" when Microsoft releases Edge Chromium to the public.
The one thing we do know is that the so-called "Stable" build is 78.0.276.14; that is an older build than the current Beta version (78.0.276.17) released some weeks ago, so it is not a "pre-release" build for public testing.
though about the versioning, Stable will always have a lower version number than Beta so considering that it might have been stable, the version number would've been correct
HotCakeX "That's exactly what I thought, but then I wondered if it's only for their internal use, why make it public, unless they want others to use it too ..."
It isn't "public" in any meaningful sense, because (a) the link is not published on the Microsoft Edge Insider site and (b) the link is not published on the Office365 site that hosts the link, either, as far as I know. The code for the page takes it out of the search path, as well. It is "public" only in the sense that if you know the URL, you can get to it. That is no different than the previous "Stable" build, which was also clearly internal.
Good luck with testing it. I'm not going to install it, because I had to do a Win10 restore after a Dev build got corrupted somehow last week and wouldn't uninstall. There's only so much pain I'm willing to put up with for the sake of idle curiosity.
Your comments suggest that Microsoft is planning a deployment that substitutes Edge Chromium as the Windows 10 browser if installed, replacing/removing Edge (Classic) and embedding Edge Chromium into Windows. Did you have a chance to see what happened to IE when "Stable" is installed? Does it go away?
- Spoiler
tomscharbach wrote:HotCakeX "That's exactly what I thought, but then I wondered if it's only for their internal use, why make it public, unless they want others to use it too ..."
It isn't "public" in any meaningful sense, because (a) the link is not published on the Microsoft Edge Insider site and (b) the link is not published on the Office365 site that hosts the link, either, as far as I know. The code for the page takes it out of the search path, as well. It is "public" only in the sense that if you know the URL, you can get to it. That is no different than the previous "Stable" build, which was also clearly internal.
Good luck with testing it. I'm not going to install it, because I had to do a Win10 restore after a Dev build got corrupted somehow last week and wouldn't uninstall. There's only so much pain I'm willing to put up with for the sake of idle curiosity.
Your comments suggest that Microsoft is planning a deployment that substitutes Edge Chromium as the Windows 10 browser if installed, replacing/removing Edge (Classic) and embedding Edge Chromium into Windows. Did you have a chance to see what happened to IE when "Stable" is installed? Does it go away?
Public means it is accessible by 7 billions people on this planet. that sounds meaningful enough to me.
based on your opinion, that would mean the Edge stable on Microsoft servers are private which is not.
if that was private then companies wouldn't even bother setting up firewalls and passwords, just put their assets and files somewhere on their servers hoping nobody will find the exact link to them.
I'm sure Microsoft Employees have better and more secure ways of accessing personal and corporate files that they need to work on.
I test it in Windows Sandbox so I'm good, that's what Windows Sandbox is for after all.
Yes that's exactly what happens with that version of Edge and that Windows 10 build number. no I couldn't check for IE status at that time. I had already disabled IE using optional features.
HotCakeX "Public means it is accessible by 7 billions people on this planet. [T]hat sounds meaningful enough to me."
We are using the term "public" in two different senses.
The best way to think about the "Stable" deployment (both this deployment and the one we discussed 6-8 weeks ago), perhaps, is to think in terms of a "pre-production environment", that is, deployment on the actual server from which the release version will, in time, be released, but deployed in a way that the version is not accessible to the public. That does not mean that a hacker cannot, through luck and diligence, find the build and "leak" the URL (common enough), but it does mean that the build is not "public" in the sense that Microsoft wants outsiders testing or using the build.
In this case (as was the case with the earlier "Stable" version) a person needs to know the exact URL to get to the build. Microsoft has not provided a path to the "Stable" version through the Edge Insider site or the Office365 site, and coding of the URL removes the site from web search engines. That tells me, anyway, that Microsoft did not intend for this version to be tested or used by the public, but instead intended the version to be "deployment tested" internally from a production server that will, in time, be used for deployment.
The practice of pre-production testing is standard in the industry, or at least that was the case when I was working in an enterprise IT environment. (I have to remind myself that I have been retired more years than many IT folk in their 20's and 30's have been working, so the concept of pre-production testing may have gone the way of the dinosaurs for all I know.) But unless things have changed in that regard since my working days, pre-production deployment testing is probably still a requirement for deployment. If it isn't, it should be, particularly in a case like this, where installation is complicated and appears to involve changes to the Windows 10 environment.
Do you mind telling us where you got the URL? It is just idle curiosity on my part, so if you don't want to, no harm, no foul.
I think that we've reached the end point of usefulness in this discussion.