simonask

35 ms·

661.
by simonask 2y ago
There is no president of the EU. There is a President of the European Council (Charles Michel, elected by member countries' heads of state), there is a President of the European Commission (Ursula von der Leyen, elected by the European
662.
by simonask 2y ago
It's not that she lost, it's that somebody who seems to oppose democracy won.
663.
by simonask 2y ago
In most countries in the world, unionization doesn't mean "get everything you want", it means collective bargaining. It's an approach that cuts both ways, creating stable employment terms, which benefits both employer an
664.
by simonask 2y ago
Ractor is cool, but I've been wondering why it uses the async `async_trait` rather than native async traits. Is it just because it came out before async traits were stabilized, and now code relies on it and it would be a breaking chang
665.
by simonask 2y ago
It doesn't matter for a startup trying to get acquired. It does matter for a company trying to scale its user base while keeping costs down.
666.
by simonask 2y ago
And when the default arena size is often outgrown, you'll known from whatever diagnostics/logging/dashboard solution you are using. Which is incidentally also a great tool when optimizing per-request memory usage. Being expli
667.
by simonask 2y ago
There's a pretty huge difference between implementing a performance optimization that works in your use case, and upstreaming that optimization to be generally usable. The latter is often orders of magnitude more work, and the existing
668.
by simonask 2y ago
I mean, it’s only a problem if your design is based on the Future having exclusive ownership of its read buffer, but io\_uring assumes a kind of shared ownership. The “obvious” solution is to encode that ownership model in the design, which
669.
by simonask 2y ago
I’m using WASM as the modding interface in my game. (I’m using wasmtime from Rust, but same principle.) Main benefits are isolation, binary portability, and hot reload.
670.
by simonask 2y ago
I mean, sure, there may be cultural differences, but let's not ignore how Spain as a country has been fucked by successive rounds of people in power making self-centered decisions, not to mention the relatively recent liberation from l
671.
by simonask 2y ago
I think you might be surprised how rare explicit lifetime annotations actually are in Rust code. But, to the point: It precisely isn’t “noise”. It’s important information that any competent C++ developer will immediately look for in documen
672.
by simonask 2y ago
You can introduce side effects to a proc macro (but please avoid if at all possible), but you cannot control the order in which proc macros are run. If you need to reason about the global schema while generating code, that won’t work.
673.
by simonask 2y ago
Yeah the obvious hole in my pet theory is that there are lots of small languages in Europe, but purchasing power may explain it. I have no idea about the quality of Apple’s localization for Slovenian, Lithuanian, or Albanian, just to name a
674.
by simonask 2y ago
I would bet that a major driving reason for delayed release in the EU is not regulations, but simply linguistics. Localization is a huge effort, even more so around the types of AI features they seem to want to deliver. As a native Danish s
675.
by simonask 2y ago
You can extend diesel in theory, but can you really in practice? In my experience, it's very hard to work with once you get into the weeds. It's a big mess of very complicated generic signatures. Might have improved since last I c
676.
by simonask 2y ago
I mostly agree with this, but the trouble is (probably) that proc-macros are heavy-handed, inflexible, and not great for compile times. In this case, for example, it looks like the generated code needs global knowledge of related ORM types
677.
by simonask 2y ago
Whole-program analysis is not tractable (i.e., not scalable), and Rust has already proven that function signatures are enough, and does actually scale. The analysis can be performed locally at each call site, and doesn't have to recurs
678.
by simonask 2y ago
In Europe in 2024, it is totally unreasonable to expect every visitor to speak the local language at a high enough level. Yes, your language is big and important, but we can't all learn all of English, German, French, Italian, Spanish,
679.
by simonask 2y ago
In practice this is a compiler bug, though, and is treated as such, and not a soundness hole in the abstract design of the type system. There has also not been a single case of this bug being triggered in the wild by accident.
680.
by simonask 2y ago
Wait, when exactly did the soundness rules change since 1.0? When have you had to re-audit unsafe code? The Rustonomicon [1] serves as a decent introduction to what you can or can't do in unsafe code, and none of that changed to my kno
681.
by simonask 2y ago
Sure, I mean, my objection is with the pretense that a reasonable calling convention in 2024 could decide to represent void* differently from any other T . It makes total sense that C programmers expect pointers to be (transitively) convert
682.
by simonask 2y ago
Just so we're clear, yes, it's "hardware-dependent", but literally every single architecture and CPU model does the same reasonable thing, which is to wrap into the negative. Any architecture that doesn't use 2s com
683.
by simonask 2y ago
No, it used to be the case that there were architectures where signed integers were represented as 1s complement, so portable code could not rely on signed integer overflow wrapping around (there would either be 2 bit patterns representing
684.
by simonask 2y ago
Just to nitpick, it's not "virtually" no UB, it's literally no UB. (Barring compiler bugs, of course.)
685.
by simonask 2y ago
Awesome writeup. Always interesting to read what Daniel has to say. I think the fact that it turned out that he was wrong (and UBsan was right, as usual) is a great testament to the shortcomings of C. Lots of people - both inexperienced and
686.
by simonask 2y ago
Wait, I thought PMs were explicitly not allowed in standups, and that standups are explicitly not status meetings.
687.
by simonask 2y ago
Wow, that article makes me appreciate how far we've come in 20 years in terms of font rendering and text layout.
688.
by simonask 2y ago
Good traditional handwriting is not less legible. You're just not as used to it, or you have only seen bad examples (like handwritten letters written by older people with shaky hands, or poor spelling, or misaligned lines). If you spen
689.
by simonask 2y ago
Even more tangentially: This is one of the reasons I'm having a great time developing a game in Rust. You never want lock contention in a game if at all avoidable, and in a lot of cases taking a lock is provably unnecessary. For exampl
690.
by simonask 2y ago
As a musician, glad to see audio production mentioned as an important use case. Even a 10 ms delay is noticeable when playing an instrument. A lot of processing is required to produce a sound: Receive the input over a hardware interface, se

More ›