65 karma · joined April 11, 2023
E.g. I see 9m downloads for vite: https://www.npmjs.com/package/vite
What proportion of that is currently for Bun?
*MY_GPIO |= 1;
Or more complex?Problem solved!
I'm looking forward to the launch of Zig, that should be a good choice for WASM. Only if I could get a pytorch-like interface in Zig now...
One needs to define their types as a const, like this one:
``` [{ type: Number, name: "field1" }, { type: String, name: "field2" }] as const ```
and then use Typescript magic to convert it into the fully fledged Typescript type.
Yes, it's annoying, but it's more flexible.
Apart from that (and noticeably higher memory consumption), Postgres is most likely preferable.
Potentially has big practical applications as it allows for construction of chemical computers that compute through chemical reactions.
The research is referenced in the WSJ article, which is behind a paywall: wsj.com/articles/the-places-with-the-worst-air-pollution-in-america-52ae23be
Imagine the world where you could trivially train a model entirely on the client side, without uploading all that data to the cloud. Then we can settle on federated learning or simply use ensembles of models trained on different clients, all without sharing data with the server.
BTW, I did have some experience with ONNX, also ran into problems with some ops (like nn.SELU not working correctly in the browser - https://pytorch.org/docs/stable/generated/torch.nn.SELU.html...).
> That doesn't get us full CUDA support, but we can run OpenCL apps at least (with x11/nvidia-driver, x11/linux-nvidia-libs and the nv-sglrun script from emulators/libc6-shim). And NVENC if you bother to compile it.
Why would you want to limit yourself to the operating system that cannot train, say, a pytorch model on your nvidia GPU?
We had some success running inference on CPU, which works for as long as the model isn't that large. But that doesn't scale for larger models, where you also want to batch requests and run them all at once on GPU.