2
points
apitman
Joined 11,197 karma
Software architect on the iobio team at the University of Utah Eccles Institute of Human Genetics. I'm passionate about the application of computer science to solving health problems. Hans Rosling is my hero.
Personal site:
apitman.com
Projects:
IndieBits.io - A community for data ownership, self-hosting, and decentralization.
LastLogin.net - A free, privacy-focused login provider
TakingNames.io - Domain names for self-hosters
boringproxy.io - Simple, e2ee tunneling proxy
patchbay.pub - Connect any two computers on the internet with curl
- apitmanI would love to see more root cause analysis data on the crashes they were seeing with wireguard-go. I wonder if it was bugs in the library itself, or the FFI.
- I miss n-gate
- It's annoying though because it keeps (accurately) pointing out critical memory bugs that I clearly need to fix rather than pretending they aren't there. It's slowing me down.
- The PSO problem is referring to this, right? https://therealmjp.github.io/posts/shader-permutations-part1...
- Also a fast compiler which lets the agent iterate more times.
- That's bad news for C++, Rust, and other slow compilers.
- For what it's worth the Intel B50 supports GPU virtualization and software support seems to be improving quickly. Really hoping this blows the lid off over the next couple years.
- Fortunately core wasm is simple enough for a single person to implement an interpreter or even compiler for.
Even if the major engines continue to pile on complexity we have a pretty good escape hatch I think.
- I did a brief comparison a while back, specifically WASM vs libriscv for. I decided to go with WASM, primarily because it was much more closely designed for this sort of thing, and it works in browsers. libriscv is really cool and impressive though.
EDIT: Found this link in my notes as well: https://www.hackerneue.com/item?id=24900376
- Careful, you're responding to the author of a wasm-based alternative.
- Note that you don't have to compile on an Alpine system to achieve this. These instructions should work on most distros:
- ncruces/go-sqlite3 was the first thing I thought of when I saw .load litestream.so. That's awesome that you've implemented this. Was it a big lift to make it work with wasm?
- Ah thanks!
- 2 points
- Currently Zig has the same issues as Rust in this context, primarily depending on a compiler that's too complex for a single person to maintain if necessary.
But in Zig's case it seems there's a pretty good chance that will change if they're able to drop LLVM in the future.
- > Hence why it should be a priority for WG14 to actually improve C's safety as well
Sorry should have been more clear. I'm talking specifically about C89, or maybe C99.
- I use Rust and C at work. I quite enjoy Rust, but I currently have no reason to believe C won't outlive it, by a lot.
- Because a human browser has to implement CSS.
- 3 points