PudgePacket
Joined 12 years ago
Karma
1,331
Submissions
389
Member since
Jul 31
Recent submissions
Comment · 1 month ago
You have been able to for a while with rust-gpu https://github.com/Rust-GPU/rust-gpu.
Comment · 5 months ago
+1,009,257 -4,024
wild
Comment · 4 years ago
Heavily speculating but it's not unreasonable that the recording process impacts the game fps. Eg if you had 2 processes trying to max out your CPU it'd be less efficient than doing them one after the other because they're fighting for resources, doing context switching (losing cache etc).
Comment · 4 years ago
Seems very similar to https://www.prisma.io/migrate.
Comment · 4 years ago
kind of giddy thinking about multi-region supabase handled by fly, sky is the limit
Comment · 4 years ago
Comment · 4 years ago
There are a number of techniques available to shrink wasm size in rust, this is the best collection of them I'm aware of https://rustwasm.github.io/docs/book/reference/code-size.htm....
Please also consider Unity web used to be significantly worse and it took multiples of bevy's lifetime for it to get to where it is now :)
Comment · 4 years ago
Tangential but the slab concept is actually really neat, basically a userland allocator for a specific type, or a vector that gives you the key inserted at depending on how you prefer to think. https://docs.rs/slab/.
Comment · 4 years ago
Thanks for point it out, after a quick glance it actually looks like something I want to learn more about. Takes the niceties from prisma.io schema tooling and bring it closer to postgres.
Comment · 4 years ago
Comment · 4 years ago
Comment · 5 years ago
I only learnt about the logging and tracing crates existed from this blog post and I've already started using them, so thank you!
Comment · 5 years ago
This is a great article and you can tell the author has deep experience with SQL from the way they speak and the other projects they're involved in.
I think many of the comments here are missing the point by saying "Oh you can get around that issue in that example snippet by doing X Y Z". Sure there are workaround for everything if you know the One Weird Trick with these 10 gotchas that I won't tell you about... but that just makes the authors point.
We can do better. We deserve better.
What could things look like if you could radically alter the SQL language, replace it altogether, or even move layers from databases or applications into each other?
Who knows if it will be better or worse, but I'd like to find out.