6 ms·

Can someone explain why https://makepad.dev/ https://makepad.dev/ is extremely slow and "unusable" on Microsoft Edge browser but run smoothly on Chrome? Is it b

by skyde 5y ago

Can someone explain why https://makepad.dev/ https://makepad.dev/ is extremely slow and "unusable" on Microsoft Edge browser but run smoothly on Chrome? Is it because of bad WebGL perf on JavasSript perf in general?

ComputerGuru 5y ago
Edge or Edgium?
tyingq 5y ago
Another possibility is code that acts differently depending on user-agent.
- rikarendsmp 5y ago
  It most definitely does not.
yonl 5y ago
For me, it's not very fast in chrome.
- ehsankia 5y ago
  Can you give a bit more flavor to "not very fast"? I'm on a measly chromebook and scrolling, selecting text, expanding directories, everything is smooth and high framerate. Is there a specific operation that is not fast? Opening it for the first time took a few seconds but afterwards it was pretty buttery.
  - rikarendsmp 5y ago
    Makepad kinda has a minimum GPU spec. It's aging-out for the people who don't have this, but some people still don't have gpu's that can bitblit their screen with a solid color.
- fulafel 5y ago
  You might be getting the software rendering webgl implementation if there are GPU driver problems (https://blog.chromium.org/2016/06/universal-rendering-with-swiftshader.html https://blog.chromium.org/2016/06/universal-rendering-with-s...). (Of course in principle you don't need hardware acceleration to make this kind of thing run fast...)
slaymaker1907 5y ago
Did you try using dev/canary Edge? It should pretty much be the same rendering engine and JS engine as Chrome. Definitely report this to the Edge team if you have the time (very easy to do from the dev version of Edge). In my experience, they are very responsive to bug reports and feature suggestions.
- rikarendsmp 5y ago
  Back in the day i made it work on Edge on an xbox. This was microsofts browser +JS engine. Nowadays its just chrome though. If it has problems, i'd be highly surprised.
rikarendsmp 5y ago
I tried for it not to be, however there is no technically specific reason no.

by skyde 5y ago

ComputerGuru 5y ago

Edge or Edgium?

tyingq 5y ago

Another possibility is code that acts differently depending on user-agent.

rikarendsmp 5y ago
It most definitely does not.

yonl 5y ago

For me, it's not very fast in chrome.

ehsankia 5y ago
Can you give a bit more flavor to "not very fast"? I'm on a measly chromebook and scrolling, selecting text, expanding directories, everything is smooth and high framerate. Is there a specific operation that is not fast? Opening it for the first time took a few seconds but afterwards it was pretty buttery.
- rikarendsmp 5y ago
  Makepad kinda has a minimum GPU spec. It's aging-out for the people who don't have this, but some people still don't have gpu's that can bitblit their screen with a solid color.
fulafel 5y ago
You might be getting the software rendering webgl implementation if there are GPU driver problems (https://blog.chromium.org/2016/06/universal-rendering-with-swiftshader.html https://blog.chromium.org/2016/06/universal-rendering-with-s...). (Of course in principle you don't need hardware acceleration to make this kind of thing run fast...)

slaymaker1907 5y ago

Did you try using dev/canary Edge? It should pretty much be the same rendering engine and JS engine as Chrome. Definitely report this to the Edge team if you have the time (very easy to do from the dev version of Edge). In my experience, they are very responsive to bug reports and feature suggestions.

rikarendsmp 5y ago
Back in the day i made it work on Edge on an xbox. This was microsofts browser +JS engine. Nowadays its just chrome though. If it has problems, i'd be highly surprised.

rikarendsmp 5y ago

I tried for it not to be, however there is no technically specific reason no.