C:\Users\Username\AppData\Local\Microsoft\Edge SxS\User Data is it true? there is not edge folder >there is ''edge sxs'' folder
It's still just as fast as it was with the first leak for me, using Canary 127. In fact I just ran a JetStream benchmark and it's about 11% faster (on average of 3 runs) than the original 109 leaked build. It's faster for me than the original 109 build, and I test the hell out of each of them every time a new one comes out as well as using it as my primary browser on LTSC 2019. But I mean really, we're talking about a few milliseconds here now and again, it's not even really noticeable UNLESS you're doing benchmarking. Guess the meaning of "getting slower" has somehow become a Bizarro World kinda thing that everybody thinks is backwards or something.
Did you just install it and start using it, or have you mucked with it in various ways or manners? 'cause if you just install it and use it it works great, really. It's when people keep tweaking stuff beyond what's considered rational that it breaks.
Been working with "personal" computers since 1974, so... It still doesn't mean "Edgium" isn't great so far even in spite of your limited experience. So far "Edgium" has been outperforming basically every other browser except native Edge in the benchmarks I use for testing, and native Edge on wins in just one of them but the results are somewhat flaky (one run it'll be better, next run it's not, then it's better, etc) - "Edgium" has proven to be consistently faster overall with higher scores on benchmarks in my own testing. If it's not working that well for you, I suppose there's reasons for it, sure.
What I would have liked more is the original Edge + all Chrome extensions working as in native Chrome + a Canary channel for Edge as well. Edge is great . It's speed , the smooth scrolling which is second to none and the lite slick and beautiful interface making it really good. If only the Extensions were ported and operate as good as on Chrome, I would have never switched from Edge to any other browser.
I do not install Edgium, I only extract content to a custom folder, but when I launch it, the User Data folder is created in C:\Users\Username\AppData\Local\Microsoft\Edge.
I noticed the same. To me, vanilla Edge and vanilla Firefox have the smoothest scrolling, but Chrome and Edgium have Smooth Scrollinfgg flags you can enable to get more fluid scrolling. Firefox still wins this competition. I wish Chrome hardware acceleration could use my videoscard's nd monitor's G-Sync.
I think we should make it official when it comes to Edge naming to prevent discrepancies in posts . Old Edge = Edgexplorer, new Edge = Edgium. Any idea how to make it a default browser from its portable location?
How can I create an .EXE file that simply starts Edge .exe with a parameter that makes it portable? I know the parameter, but not how to make a new EXE. That .exe would be like a normal .exe, but with a special parameter. Didn't someone already try to make portable Edgium?
Sorry, what I was referring to was where are the binaries/exectuables installed. Not the default location of the profile data. I ended up getting a chance to test this out today and my assumption (based on my Chromium experience) was confirmed. By default, the executables are installed in AppData user profile location, similar to Chromium. For anyone that wants to install this in Program Files, you can do this from the (Admin) command line quite easily. Example: Code: "D:\Downloads\Chromium Builds\Edge\MicrosoftEdge_X64_74.1.96.24.exe" --system-level Change command based on your directory structure, of course. Ensure that this is done with an Admin command prompt. Confirmed via edge://version Code: Microsoft Edge 74.1.96.24 (Official build) (64-bit) Revision 9fd157eac96f1b6749c7dd42bd8e44015538fdd6- Operating system Windows 10 OS Build 18362.53 JavaScript V8 7.4.288.18 Flash 32.0.0.171 C:\Windows\system32\Macromed\Flash\pepflashplayer64_32_0_0_171.dll User agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.48 Safari/537.36 Edg/74.1.96.24 Command-line "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --flag-switches-begin --enable-appcontainer --enable-gpu-appcontainer --enable-features=msEdgeDarkModeAvailable --flag-switches-end Executable path C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe Profile path C:\Users\~redacted~\AppData\Local\Microsoft\Edge\User Data\Default Below I am just going to share some of my own notes from my testing, mostly in comparison to Chromium. Also, for what it's worth, enabling chrome://flags/#enable-gpu-appcontainer sandboxes your GPU process within an LPAC (Less Privileged AppContainer) sandbox. * * Interesting, copying and pasting edge://flags/#enable-gpu-appcontainer from edge://flags/ automatically pastes as chrome://flags/#enable-gpu-appcontainer. Minor development bug, I suppose. Third-Party Module Feature (edge://conflicts/) unfortunately is not available in Edge Chromium. This is a feature in Chrome which blocks DLL injection into browser processes, particularly conflicting modules. Site Isolation (Site Per Process) edge://process-internals/ is available which is nice. edge://edge-urls/ interesting internals here. edge://policy/ seems to have been removed and missing. This concerns me because I have always managed Chrome and Chromium via group policy. So this is the one missing page that really stands out to me from the list of internal URLs. Anyway, that is it for my testing of Edge Chromium for now. It held my patience for approx. 25 minutes.
Oddly enough I just copied and pasted chrome://flags/#enable-gpu-appcontainer directly from your post and it converted chrome to edge. Some nice info there, especially the URLs list, thanks for sharing that stuff.