skavi

14 ms·

181.
by skavi 2y ago
The people yearn for the Microsoft Courier [0]. [0]: https://youtu.be/UmIgNfp-MdI
182.
by skavi 2y ago
can’t really be handled nicely by macros outside of the case where the drop impl doesn’t need any data from the scope.
183.
by skavi 2y ago
https://news.ycombinator.com/item?id=41996976 See this comment describing how an executor can properly handle cancelations.
184.
by skavi 2y ago
Hi, I’m also from a systems programming background. I’m not sure what your level of experience with Rust’s async model is, but an important thing to note is that work is split between an executor and the Future itself. Executors are not “sp
185.
by skavi 2y ago
> Developers, you among them it seems, don't really understand the requirements of a truly async process and get confused trying to shoehorn it into a "callbacks with context switch" framework like rust async. This is an o
186.
by skavi 2y ago
GB6 is great. Older versions weren’t always very representative of real workloads. Mostly because their working data sets were way too small. But GB6 aligns pretty well with SPEC2017.
187.
by skavi 2y ago
The guarantees given to you by the borrow checker are zero cost. Once you’ve exceeded its capabilities, you have the choice to either pay a runtime cost (use RefCell and friends) or deal with maintaining and validating unsafe code.
188.
by skavi 2y ago
> You never tried to await from within a synchronous function? Whenever necessary I have been able to do this easily. Calling async code from a synchronous context is not an example of something which can’t be done in Rust today. > Or
189.
by skavi 2y ago
That sounds like a few different languages. And I think it’s fine to want a language like Rust that allows you to be less explicit about things. Based on what I’ve heard, you might just be looking for Gleam. But I don’t think it would be th
190.
by skavi 2y ago
Of course. But the common case of calling a synchronous function from a Future is something trivial like a + b.
191.
by skavi 2y ago
A great bit about Rust async is that it’s sufficiently flexible for use in embedded environments. I would really not prefer a Rust that includes a more intrusive runtime. Especially given the API changes things like io-uring may require to
192.
by skavi 2y ago
I haven’t used Go, but I am fairly certain it’s not really trying to do the same things as Rust. IIRC, calling C from Go isn’t zero cost. It also includes a much larger runtime than Rust.
193.
by skavi 2y ago
How so? It’s trivial to block on a Future or to call a function within a Future. I could imagine another language where all “functions” are Futures, but I don’t think that would be the right move for Rust. At the very least, that alternativ
194.
by skavi 2y ago
Yup, that’s an entirely fair characterization. One I probably should have understood from your initial comment :).
195.
by skavi 2y ago
Not to your main point, but I don’t think it’s fair to say Rust “botched” its async impl. There are certain features it’s missing, but nothing about the design really prevents them from being added. And many have been in the past few years.
196.
by skavi 2y ago
https://ziglang.org/documentation/0.13.0/#Hello-World
197.
by skavi 2y ago
Is anyone else experiencing repeated crashes when viewing this article via iOS Safari?
198.
by skavi 2y ago
Is Electron really so different in your experience than a PWA? Personally, I always try to use a PWA when the app is otherwise offered via Electron. If it’s going to depend on a browser engine, it may as well be the one I already have open
199.
by skavi 2y ago
https://parallel-rust-cpp.github.io/ This goes through seven iterations of optimization an algorithm in rust, comparing it to the equivalent c++ at each stage.
200.
by skavi 2y ago
Profiles aren’t always entirely accurate. That’s kinda fine, since (IMO) they’re mainly useful for pointing you in the correct direction. Once you’ve found a small enough chunk of logic that’s worth optimizing, I’d recommend relying more on
201.
by skavi 2y ago
GPU benchmarks in TFA are run on Windows: https://open.substack.com/pub/chipsandcheese/p/lunar-lakes-i...
202.
by skavi 2y ago
also: https://en.wikipedia.org/wiki/Dalvik_(software)
203.
by skavi 2y ago
Could you explain the linking system in another way? it’s not quite clicking for me. What does it mean to unroll the earmarked “indexing” roll to the linked region?
204.
by skavi 2y ago
third generation: https://en.wikipedia.org/wiki/Third-generation_programming_l...
205.
by skavi 2y ago
The retrospective on the Xi editor project has a few notes on issues with JSON (at least in the context of Rust and Swift). This is from someone who initially seemed to have a very similar perspective to you. See the JSON section of the pos
206.
by skavi 2y ago
Intel has historically been pretty great at Linux support. Especially for peripherals like WiFi cards and GPUs.
207.
by skavi 2y ago
You really should update your post wrt the Mutex changes.
208.
by skavi 2y ago
A single SoC, which includes a GPU (two GPUs, kinda).
209.
by skavi 2y ago
Those benchmarks aren’t great. A real world-ish workload made generic over all these types would provide much more interesting results. Especially if heap usage was also tracked.
210.
by skavi 2y ago
It sounds like you’re looking for an absolute solution which, as you suggest, will never exist without the use of state violence. I believe most people would be satisfied if the problem were to simply become rare enough that they didn’t hav

More ›