only using rust myself, too, but not seen any crashes
only using rust myself, too, but not seen any crashes
This is something I should write a blog post about as well… but for now, if you're curious check out www.rastair.com and its repo where this is happening :)
Last week, I was working on one of the fastest tools in its category. Then I got tricked into optimizing it, made Claude write some compute shaders for me, got rid of more `memmove`s, and now I think I can run on laptop in 10min what last week ran for 2.5h on a server with 16 cores! #rustlang
So many opinions on this one. Zoomable graphs with different levels of details showing summaries makes perfect sense to me cause that’s what it oooks like in my head (maybe also buy a 50” touch screen but that’s an easy fix)
Very cool! Was looking at lilaq.org recently based on Typst (makes it quite flexible for the cost of learning and bundling typst) but this looks even more feature-full :O
Fun to read in this format too! I kinda liked the big GitHub link previews as visual dividers but that’s a minor thing. Your *this* close to just making a “this week in bevy merge train” blog aren’t you?
oh yes! i love that format
Is it weird that I as a human have more fun reading skill files compared to actual programming books?
Oh hahaha I saw this name and for some reason thought it was related to tokio-tracing or github.com/wolfpld/tracy
@fasterthanli.me what ever happened to your experiments/research into with writing specs with ids and then tracing them in the code? I remember seeing you post about it and I think @jamesmunns.com and you talked about it but can’t find it anymore :)
Ah, neat! Always cool to see you do new stuff in the space. Might finally have a use case for facet soon with cli/config files/docs generation :)
Woah another facet thing going in another direction? I have a hard time keeping up 😅 need to make time to read a couple weeks worth of your posts!
Ugh yeah same, was worried for a bit but then just added a filter and went to sleep 😅
Always fun to read this, especially now that I’ve discovered tbsky.app 😄 tbsky.app/profile/alic...
Do you need the compute power or the ram or the IO? I’m sure there’s enough people using For You that you can get a dedicated server if you want :) maybe www.hetzner.com/dedicated-ro... for ~75€ would work out? I’d pitch in for sure
Just did some accounting documents in typst cause having a programming language that can render tables is actually cool! Not as visually clear as spreadsheets but still has live preview
░░░░░░░░░░░░░░░░░░░░ 0.00%
A blue square that says "Job Opportunity" from Ferrous Systems. Text says: Hiring: Research Engineer We're hiring for a rare role: Join us to formalize the semantics of Rust on a real, multi-year project.You'll work with leading experts, contribute to the foundations of the language, and can also be used as an opportunity to pursue a PhD alongside the work.
🦀 A unique #opportunity for #RustLang enthusiasts and verification researchers: Join us for a three-year project formalizing a Rust subset – and pursue a PhD if you choose.
Interested? 👉 ferrous-systems.com/blog/researc...
I listened to this as an ai generated podcast while at the gym, thinking it would be the best medium for this rfd specifically. I got the point but I regret my choices
at least this one comes embeddable to some degree www.npmjs.com/package/@pin... (I used it in typst as well, instead of learning how to recreate half of it there)
Sadly this is code for my previous employer :/ but my old serde pr is here github.com/serde-rs/ser...
Omg yes please! I still have at least one project with a custom serde fork to get this for some yaml config thing (and every year it so I get a comment on my stale PR saying “why is this not merged”)
In case anyone else needs to hear it: `Vec::with_capacity(user_input)` is probably a bad idea and will eat your RAM when you least expect it. At least put a `.min(reasonable_max)` on it. #rust
Interesting! I’ve been using color-eyre because I liked the panic hook and the fact it collects span traces as well. If I could have context in one place for tracing and errors and get it in the right stacktrace-y report that’d be amazing
Alright, I have pretty printing! Now how do I load my `.lldbinit` file by default when press "debug test" in @zed.dev? :)
I have seen `.rustup/toolchains/$version/lib/rustlib/etc` exists but I didn't dare touch anything yet. Maybe soon
For now, I'm at
```rust
#[cfg(debug_assertions)]
pub mod smallvec {
pub use std::vec as smallvec;
pub use std::vec as smallvec_inline;
pub type SmallVec<T, const _N: usize> = Vec<T>;
}
#[cfg(not(debug_assertions))]
pub use smallvec::smallvec;
```
Fellow #rust and #lldb users, how hard is it to add support for some common library types like SmallVec or SmolStr? I want to inspect my nice inlined types!
ohhh just learned about `allow_attributes_without_reason`! thank you!