144 karma · joined July 30, 2017
For 50 iterations:
* ONNX on Windows was 4-5 minutes
* ROCm on Arch Linux was ~2.5 minutes
* SHARK on Windows is ~30 seconds
Edit: I suppose in this case they could test prior samples, but if you don't have any, you're out of luck?
Go to Settings > Projecting to this PC to enable it. You may need to install the Wireless Display optional feature first.
Yes? I thought that was the whole point. Actually I'm confused about the use of "native" here. It supports running both TS and JS files? And the TS files must be compiled to JS before they can be run anyway. So I'm not seeing any choice that was lost.
That’s what we all do now
I mean, some people do, but I don't. Not everyone uses React / Vue / etc, and afaik it's only React that is forgoing stylesheets. And it's not like stylesheets are dead or that styling elements through JS is non-standard. (I do use Vue, with stylesheets)
First of all C# doesn't run in the browser without compiling to WASM which has all sorts of caveats.
Second, I don't see how the fact that one could compile TS to C# would suddenly put everyone "on the .NET stack". Does the same risk exist if we can compile JS to C#? Which would work about just as well (i.e. not). And TS is also open source and produces reasonably readable JS, so it's not like there's even any lock-in.
Wouldn't it make more sense to be worried about compiling C# or other languages to WASM? Which I'm also not worried about.
There would probably be less GC pauses if the benchmark code wasn't doing things like
[...Array(this.count.value).keys()].forEach(...)
instead of a for loop.I've been doing some WebGL work recently and I've noticed that while it reaches ~144 fps using requestAnimationFrame() in Firefox, there's a lot of stuttering. It's very smooth at 144 fps in Edge Chromium, while Edge Legacy is below 80 fps. As far as I can tell it's not CPU bound, and it's definitely not GPU bound. It would be nice if I could get it running smoothly in Firefox but I don't know what to investigate.
Is that something you're handling in your project? Do you have any pointers?
It almost seems like some sort of co/contravariance issue?
A function that reads from an Array<string | number> should be able to accept either an Array<string> or an Array<number> (or Array<string | number>), but a function that mutates it should only be able to accept Array<string | number>?
It being natural doesn't have any bearing on how healthy it is.