Yoric

19 ms·

391.
by Yoric 1y ago
Can confirm. In JS, we designed `await` specifically to hide `.then()`, just as we had designed `.then()` because callbacks made tracking control flow (in particular errors) too complex.
392.
by Yoric 1y ago
But that's the thing: async, by itself, doesn't guarantee that anything is non-blocking. For your fiber (or any other kind of user-land abstraction) to be non-blocking, you MUST ensure that it doesn't perform any blocking cal
393.
by Yoric 1y ago
Defining async is hard. And I'm writing this as one of the many people who designed async in JavaScript. I don't quite agree with the definition in this post: just because it's async doesn't mean that it's correct.
394.
Show HN: Open-Source Quantum Solver for Maximum Independent Set Problems
6 points by Yoric 1y ago|0 comments
395.
by Yoric 1y ago
Out of curiosity, what would you use coroutines for, in Rust? My personal use was clearly `async`/`await`, and this landed quite some time ago.
396.
by Yoric 1y ago
What I'd be interested in would be something I could host on my local server (e.g. with ollama) to get suggestions on my laptop, where I write typst or markdown with Zed or VSCode. I realize I'm a niche :) Does anybody know of suc
397.
by Yoric 1y ago
Interesting. This is a bit reminiscent of how OCaml handles async these days.
398.
by Yoric 1y ago
Hey, I used to have an office close to the dad's :) That's before he went into politics, though.
399.
(Quite) a few words about async(yoric.github.io)
3 points by Yoric 1y ago|0 comments
400.
by Yoric 1y ago
Well, that would definitely have made both my life and theirs miserable, so I won't be passing on the suggestion to my kid :)
401.
by Yoric 1y ago
There is a big difference between LLMs and most other tech improvements, though: with most technologies that I can think of that solve 80% of the problem, it's easy to find out whether the technology works. When you're working wit
402.
by Yoric 1y ago
Ooooohhh coccinelle for Rust? Extremely exciting! As someone who values understanding my code, I'd use it over LLM-based refactoring any day of the week (although I might use a LLM to produce coccinelle patches).
403.
by Yoric 1y ago
Do you really think governments should stop investing in the future?
404.
by Yoric 1y ago
On, nice! I'll be interested in reading how this goes!
405.
by Yoric 1y ago
Is it? I seem to recall that "systems programming" was initially penned meant what we now call "application development" [1]. I realize that these days, the two tasks are considered very different, but as far as I unders
406.
by Yoric 1y ago
Fair enough.
407.
by Yoric 1y ago
For what it's worth, Mozilla has done Electron-on-Gecko at least twice (several years before Electron), and Electron-on-Servo at least once. There was brief interest by the community, and a few applications were written to take advanta
408.
by Yoric 1y ago
Many layers were in C++. Most of the JS code was the applications (including the homescreen).
409.
by Yoric 1y ago
> - It's really unfortunate that Rust wasn't a bit further along during the Firefox OS era. A lot of the Rust UI pieces that are now being developed would make a really strong foundation for something like Firefox OS. And could
410.
by Yoric 1y ago
> As far as I know we don't have decades of research about the improvements in productivity and correctness brought by static type systems. I seem to recall at least some research dating back to the 90s on the topic, which showed ho
411.
by Yoric 1y ago
But that won't survive an upgrade, will it?
412.
by Yoric 1y ago
My bad, I misunderstood your previous comment.
413.
by Yoric 1y ago
> Not "some cases" but "almost all cases". It's a categorical difference. Good point. But my point remains. > First, most stdlib APIs that can fail in ways that are meaningfully interpret-able by callers, do d
414.
by Yoric 1y ago
(not the GP) Indeed, while not being a fan of how this aspect of Go, I have to admit that it seldom causes issues. It is, however, part of the reasons for which you cannot attach invariants to types in Go, which is how my brain works, and p
415.
by Yoric 1y ago
Indeed, you can absolutely handle some cases with combinations of `errors.Is` and `fmt.Errorf` instead of implementing your own error. The main problem is that, if you recall, `errors.Is` also appeared 8 years after Go 1.0, with the consequ
416.
by Yoric 1y ago
Oh, wait, is Elon porting the venerable xchat to Rust? :)
417.
by Yoric 1y ago
Thanks for the clarification.
418.
by Yoric 1y ago
> If you define errors with Errors.New you use string comparison. With `Errors.New`, you're expected to provide a human-readable message. By definition, this message may change. Relying on this string comparison is a recipe for late
419.
by Yoric 1y ago
> I don't see how any good-faith analysis of Go errors as specified/intended by the language and its docs, nor Go error handling as it generally exists in practice, could lead someone to this conclusion. Let me detail my claim.
420.
by Yoric 1y ago
Indeed, I can testify that `?` was very much designed with the do-notation in mind.

More ›