Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sestep
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
61.
▲
by
sestep
1y ago
Currently you use Binaryen to build up a representation of a Wasm module, then call emitText to generate a .wat file from that. With wasm-tools you'd do the same thing via the wasm-encoder crate to generate the bytes corresponding to a
62.
▲
by
sestep
1y ago
For what it's worth, I also tried Binaryen from TypeScript and similarly found it frustrating. I switched to using wasm-tools from Rust instead, and have found that to be a vastly better experience.
63.
▲
by
sestep
1y ago
I statically link all my Linux CLI tools against musl for this reason. Or use Nix.
64.
▲
Parameters and binding forms should be mutually recursive
(samestep.com)
6 points
by
sestep
1y ago
|
0 comments
65.
▲
by
sestep
1y ago
For reference, this idea is becoming more popular recently due to the Green brothers: https://youtu.be/-C3lR3pczjo
66.
▲
by
sestep
1y ago
Did you not click the link to the website? It is Trump and MAGA related.
67.
▲
by
sestep
1y ago
Yep fair. I'm not sure why they didn't spend more effort on the JS part, just saying they didn't.
68.
▲
by
sestep
1y ago
True, but also the loop syntax is simply incorrect, which would have been caught by running it; so probably a better interpretation is simply that the author didn't spend much time thinking about that JavaScript code because it didn&#x
69.
▲
by
sestep
1y ago
If I understand correctly, the only parts you'd need to verify are the core of the theorem prover, called the "kernel" (which is intentionally kept very small), and possibly the code in charge of translating the theorem stat
70.
▲
by
sestep
1y ago
https://xosh.org/text-to-diagram/
71.
▲
by
sestep
1y ago
Yeah I've used it (cool project indeed!), albeit mostly just in a project I and others in the autodiff community maintain which benchmarks many different autodiff tools against each other: https://github.com/gradbench&#
72.
▲
by
sestep
1y ago
A bit more advanced than this post, but for calculating Jacobians and Hessians, the Julia folks have done some cool work recently building on classical automatic differentiation research: https://iclr-blogposts.github.io/202
73.
▲
by
sestep
1y ago
Could the question mark in the HN version of the title be removed? It makes it read as a bit silly.
74.
▲
by
sestep
1y ago
Right, but the only time I've ever used `git add -p` was just to try it out years ago and be like "yep that sucks" and go back to using Magit (and then later VS Code). Those are my actual baselines.
75.
▲
by
sestep
1y ago
I really like all the concepts and have only heard good things, so I tried it but wasn't able to figure out how to use it as effectively as I can use Git. Specifically, I use VS Code and do a lot of stuff with the IDE's builtin su
76.
▲
by
sestep
1y ago
I already do: https://github.com/gradbench/gradbench/blob/0276272d0df5be19... And the CI build doesn't use Docker caching, so no shenanigans there.
77.
▲
by
sestep
1y ago
I tried going back to change my Dockerfile to see if that would work, and it did not: RUN eval $(opam env) && opam pin add dune 3.7.0 && opam install --yes dune Similar error to before: [ERROR] Package dune has no
78.
▲
by
sestep
1y ago
No, the problem is that dune=3.7.0 got removed from the registry entirely.
79.
▲
by
sestep
1y ago
And even if you do get opam working for a project, it's not at all reproducible and will just randomly break at some point in the future. For instance, I had this in a Dockerfile for one project: RUN eval $(opam env) && opa
80.
▲
by
sestep
1y ago
You probably only saw the cursive backup font and not the intended Roboto font that the page actually uses (which took about half a second to load for me); here's a snippet from the CSS: font-family: "Roboto", "Under
81.
▲
by
sestep
1y ago
Does std::deque support random access?
82.
▲
by
sestep
1y ago
Or technically, three orders of magnitude smaller? (half a character per post)
83.
▲
by
sestep
1y ago
More specifically, it seems like this is a problem for people using async Rust.
84.
▲
by
sestep
1y ago
Thank you for providing a uv.lock file! I spent a good chunk of last month trying to get graphics research projects working that only provided requirements.txt (or not even that, e.g. the original Gaussian splatting paper), and it was hell
85.
▲
by
sestep
1y ago
No, OCaml is not lazy.
86.
▲
by
sestep
1y ago
Ohh you're right thanks, I mixed up which part of the post you were talking about; sorry for getting confused. Yes, I agree that it doesn't make sense for that to be due to the OS. That's just poor writing on my part: in that
87.
▲
by
sestep
1y ago
Gotcha, sorry for not picking up on the sarcasm. Yeah, I mean, I didn't really bother running the experiments many times for the smaller array sizes, so it could potentially be interesting to see if those artifacts persist when poked.
88.
▲
by
sestep
1y ago
Thanks, I may try that. Out of curiosity, what do you see when running the same code on your machine?
89.
▲
by
sestep
1y ago
No, they spell it with two: look again at the URL that JPLeRouzic posted.
90.
▲
by
sestep
1y ago
Haha, it seems you may have thought the person you were responding to is the post author :) but actually that would be me. Agreed that the odd spikes don't matter, that's why I didn't bother discussing them; I was more intere
More ›