HN user

negativegate

144 karma
Posts0
Comments41
View on HN
No posts found.

nod-ai/SHARK from the original submission is by far the fastest way I've found to run Stable Diffusion on a 5700 XT.

For 50 iterations:

* ONNX on Windows was 4-5 minutes

* ROCm on Arch Linux was ~2.5 minutes

* SHARK on Windows is ~30 seconds

Welcome to C# 10 5 years ago

File-scoped namespaces is nice to not have every class already sitting at one level of indentation. I don't see what it has to do with nested folders.

Did you think Typescript would be the native language in Deno?

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)

I'm not following this train of thought.

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.

I'm seeing <2ms in Edge Chromium and ~10ms in Firefox on a 144 Hz display. I'm curious how that compares to what other people are seeing.

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.

Firefox 75.0 6 years ago

Fixed but it looks like it is still hiding behind a toggle on about:config.

Firefox 75.0 6 years ago

It looks like you currently need to go to about:config and enable layout.css.backdrop-filter.enabled. It worked for me without enabling web render. Not that this does much good until it's on by default.

Cool, I started working on something similar a while back but I didn't get past handling generics. Like if you have a node<T> with two T inputs and a T[] output, then when you attach a number to an input, the other input's type becomes number too and the output becomes number[]. That could need to propagate to connected nodes, too. Also when you disconnect a node, you would want to determine whether T must still be a number.

Is that something you're handling in your project? Do you have any pointers?

TypeScript 3.5 7 years ago

Interesting, though it does flag the push() as an error if you use "Array<string> | Array<number>" as the argument type.

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>?

So is this basically the server okaying a replay attack? I'm looking through the technical post but it hasn't clicked yet.