|
It's ugly as hell, but... maybe I'll do it...
Without renaming it... :P
|
|
|
|
|
Quote: Edge Chromium loads it in 2,59 seconds.
The old Microsoft edge loads it in 0.88 seconds.
With Opera I can't even start the timer so let's say 0 seconds.
Is it that Edge Chromium had to go query the DNS, hit the CDN servers, pull the data, then older Microsoft Edge brought it in the memory for caching purposes and Opera just copied the already loaded page and show it to you?
Ignore the rest if you enjoy using Opera
I am not saying that I do not like Opera, but lately, Opera has been hijacking my sessions from other browsers, especially Chrome. And I have hated that, always. I tried to post this as a bug on Chrome but one of the Opera engineers said that they ask for permission. But, clearly, they never do. It is merely a download, install and continue where you left off in Chrome.
At least Firefox and other browsers try to request data import, Opera never does, and brings in the logged-in sessions for several sites.
It might be that Opera uses the same internal engine that is why, or whatever, apart from the internal VPN and ad blocker, the browser sucks.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Not at all, just restarted the PC and started opera and the same speed, done several database connections and updated some values... all is much faster.
I really don't enjoy using it... I use it only for the VPN... Everything looks worse there.
But truly... almost 3 seconds of difference loading a page? 
|
|
|
|
|
|
Testing it right now...
It's fast.
And looks nice.
And accepts the same extensions than Chrome as it's chromium based...
How can it be possible than something based in the same chromium works that different in the same page?
|
|
|
|
|
I had nothing in particular against the old Edge, excep one couldn't drag the current URL from the tab bar...
So I might not care about the new Edge if they have the same basic UI functionality missing... 
|
|
|
|
|
I liked it and they decided to kill it... ^^¡
I think the new one can do it (in fact is like Chrome with everything placed where Microsoft would put it) with a couple of good additions...
The day they replaced the graphical representation of the form controls (only visible thing that I could notice) the browser started to become slower.
Who knows if they will make it better once it goes out of beta...
|
|
|
|
|
Beta to release is usually when they work on performance
And they have lots of test suite available...
And they better perform if they want to gain traction!
|
|
|
|
|
Maybe you're time tracker should count up the number of seconds it takes to load, so you can see how much time you've lost at the end of a year. 
|
|
|
|
|
|
How do Chrome and Firefox compare?
Maybe Edge will become faster once it's out of beta?
|
|
|
|
|
Sander Rossel wrote: once it's out of beta?
 are you really serious on that one?  
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Try repeating the experiment. The figure could just be an Edge Case 
|
|
|
|
|
Seems like Win 10 updates are a risk these days. Amyone updating? Or should I wait?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
To be fair, it's a minority of my systems that run into these sorts of problems.
OTOH, it's still a little disconcerting when my Server 2019 VM started exhibiting update problems so soon after that was still a recent, full, and clean install...running on their own hypervisor, so the physical hardware is abstracted away...
|
|
|
|
|
Tobe honest - with a week experience of W10, updates seem to me the smallest problem...
Let us talk about large fonts first...
Or the hide-and-seek re-design...
Or the Office licence wiped out...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Let us talk about large fonts first...
I'm not aware of any "large font" problem. That's a user choice.
I have a 4K display, and refuse to rescale the UI "because I have the pixels to spare". No, I want to run it at its native resolution, otherwise I'm just wasting screen real-estate (using up to twice as many pixels to render the same amount of data). Across 40", the text is actually smaller than it is on the 27" 1080p monitor I have sitting next to it.
Or are you talking about something else altogether?
|
|
|
|
|
I have weak eyes and with those high resolution monitors the normal font size is way too small... So I use 125%...
And if you Google for Windows 10 DPI you will see what I have here...
One of the fascinating things, that if I create a brand new WinForm application (using latest VS2019) it looks perfect in the designer (assuming I have configured VS compatibility mode correctly) but blurred when running... So I either have to set the exe's compatibility or change the form's properties in VS...
An other one is that IIS manager seems to be immune to any configuration I threw at it...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
So how is this font sizing thing not a problem with previous versions of Windows?
As far as I can tell, you had some options in 7, but it's only in recent versions that MS has made significantly more efforts to present additional options.
Bottom line...what I'm trying to say is that by default, 10's fonts aren't any larger or smaller than previous versions, but at least 10 presents plenty of options to do anything about it.
|
|
|
|
|
100%, 150%, and 200% work on W10
125% exists as an option but is broken, a similar effect can be reached by taking off your glasses (if you need them) or looking through fog. It used to work on 7 (maybe?) and 8 (definitely), and that old way of "actually working" can be resurrected with some weird 3rd party program that applies a registry setting at boot (Windows really likes to un-apply the setting).
|
|
|
|
|
Microsoft introduced (with W8) a new method to work with DPI - they call it High DPI. It targets high resolution monitors and became the default method in W10...
So older software - and that includes software from Microsoft - will display blurred fonts (fonts only not any other graphics) when picking larger font size... And now you have to tell to Windows about each and every software not to use the new method, but fall back to the original...
As one use W10 for work only I have no gain from this High DPI method - which should be spectacular fro games and video - but I can't turn it off only software-by-software...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Well...all I can say is that I'm not using any custom resizing or fiddle with per-app settings, and use each of my monitors' native resolution...and everything looks fine on all of them. Although I do keep hearing about some of the things you mention. If I had to guess, I'd say it all starts to surface once you start customizing things.
|
|
|
|
|
Aww, man, all these problems are so yesterday!
|
|
|
|
|
For some reason, the last one that got pushed at work turned off my numlock on start. It's confusing, and mildly infuriating.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Warning: Another Windows Update rant.
I've had a Windows Server 2019 VM refuse to install updates for quite a while now. Since today's patch Tuesday, figured I'd try to dig a little more into it since I'm going to be looking at that machine again sooner or later.
MS has made it clear for a while now that, with Cumulative Updates, you can take a brand new OS install, and immediately bring everything up to date just by installing the latest available Cumulative Update. Since this particular VM refuses to install the latest CU for Server 2019 (KB4522355, which came out October 24th) directly from my WSUS server, I figured I'd download the offline installer, and run that locally (more often than not this solves this type of problem).
Nope, "this update is not applicable to your computer". Tried many things, no change.
On a hunch, I tracked down the CU prior to that one--from October 8th (KB4519338). That one didn't complain, and is now in the process of being installed (as I'm writing this).
If these CUs are truly "cumulative", why does the newer one insist it's not applicable...? Windows Update itself insisted I needed it...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
