raggi

10 ms·

121.
by raggi 10mo ago
> How so? Garbage collection has inherent performance overhead wrt. manual memory management, and Rust now addresses this by providing the desired guarantees of managed memory without the overhead of GC. I somewhat disagree, specifically
122.
by raggi 10mo ago
Can you give some examples of " ... not excruciatingly painful" and why you think they're inherent to RAII?
123.
by raggi 10mo ago
Not enough to say yes in earnest. I help maintain some swift at work, but I put my face in the code base quite rarely. I've not authored anything significant in the language myself. What I have seen is some code where there are multipl
124.
by raggi 10mo ago
People always complain about unsafe, so I prefer to just show the safe version. use std::sync::Mutex; static LIST: Mutex<Vec<String>> = Mutex::new(Vec::new()); fn main() -> Result<(), Box<dyn std::error::Error
125.
by raggi 10mo ago
I really hate the anti-RAII sentiments and arguments. I remember the Zig community lead going off about RAII before and making claims like "linux would never do this" ( https://github.com/torvalds/linux/bl
126.
by raggi 10mo ago
Periodic reminder that just because Go having an easy to use SSH package made these easy to write, connecting to SSH servers and doing TOFU all the time with the keys is far far less safe than webpki, and this service could be relatively ea
127.
by raggi 11mo ago
Back when people were still trying to make ASPs happen, clippy removal was a professional service. Having clippy running over RDP would cripple servers otherwise capable of serving a bunch of office users.
128.
by raggi 11mo ago
Docs though?
129.
by raggi 11mo ago
explorer.exe is both the shell and the file explorer which is an unfortunate state of affairs. There's long been an option to make it multi-process, but the cost of that option has increased with every release since 95. If I remember c
130.
by raggi 11mo ago
I love how one of the screenshots appears to be using the ion window manager, I guess they're very aware of the name collision :D
131.
by raggi 11mo ago
my brain expected the part after `-` to be new speculative execution bugs
132.
by raggi 1y ago
if you can always move the data that's the sweet spot for async, you just pass it down the stack and nothing matters. all of the complexity comes in when more than one part of the code is interested in the state at the same time, which
133.
by raggi 1y ago
The language team tends to look at these kinds of challenges and drive them to a root cause, which spins off a tree of work to adjust the core language to support what's required by the higher level pieces, once that work is done then
134.
by raggi 1y ago
yes
135.
by raggi 1y ago
if you want your actors to be independent computation flows and they're in different coroutines or threads, then you need to arrange that the data source can not modify the data once it arrives at the destination, in order to be safe.
136.
by raggi 1y ago
i forget if this part unwinds to the exact same place, but some of this kind of design constraint in tokio stems from the much earlier language capabilities and is prohibitive to adjust without breaking the user ecosystem. one of the key ad
137.
by raggi 1y ago
_an answer_ is performance - the necessity of creating copyable/copied messages for inter-actor communication everywhere in the program _can be_ expensive. that said there are a lot of parts of a lot of programs where a fully inlined a
138.
by raggi 1y ago
yes, you can produce similar issues with promise guarded states and so on as well, it's a fairly common issue in async programming, but can be surprising when it's hidden by layers of abstraction / far up/down a call-cha
139.
by raggi 1y ago
Those pages are out of date, and AsyncDrop is in progress: https://github.com/rust-lang/rust/issues/126482 I think "practically rudderless" here is fairly misinformed and a little harmful/rude
140.
by raggi 1y ago
Mine too, and I bought an air in the last generation and I barely use it because I thought the 60hz display would be ok, but I've been living with 120's everywhere for long enough the 60hz is actually horrible to use now. First wo
141.
by raggi 1y ago
True, the relays currently use http and have a web socket path. The web based ssh client in the admin panel uses this transport.
142.
by raggi 1y ago
(Tailscalar) I'm very bullish on WebTransport in the future, but, it doesn't solve for NAT traversal. I'm watching keenly as well how Iroh gets on with QAD, relatedly. If it all comes together this may well become more magic
143.
by raggi 1y ago
There is no circulation in hair, hair is dead, and it is produced slowly. Nothing about your commentary passes basic scrutiny.
144.
by raggi 1y ago
There was quite a different context when it was written 15 years ago, but essentially the same root jokes.
145.
by raggi 1y ago
It's also horizontally scalable: https://gist.github.com/raggi/560087#file-shardnull
146.
by raggi 1y ago
i can confirm the above. sadly felt a confirmation might actually be helpful because there's some wild stuff around the threads today.
147.
by raggi 1y ago
> At least the kids are safe. Are they any safer? Roadblocks rarely stopped me as a kid. These kinds of impediments most often resulted in me strategically moving what I was doing to somewhere out of sight of the gatekeepers, most often
148.
by raggi 1y ago
it's 317 unique crates, some of which are internal 305 with helix- removed 258 with gix removed (git stuff in multiple packages from a single upstream group) 240 with windows api wrappers removed. 170 if you remove all subpro
149.
by raggi 1y ago
Honestly I think everyone involved here, and I know most of them, needs to step back and grow up. Despite the formal tone, and the potential legal issues at play here, this situation seems to be descending into needless childishness with po
150.
by raggi 1y ago
> I think you are just agreeing with me? sure, i mean i have no goal of alignment or misalignment, i'm just trying to provide more insights into what's going on based on my observations of this from having also worked on this u

More ›