4 ms·
Agreed (I think arena-style "allocation at the top" makes Rust significantly nicer to write in general, and I borrow from a big chunk of the data at the top qui
by sunshowers 2y ago
Agreed (I think arena-style "allocation at the top" makes Rust significantly nicer to write in general, and I borrow from a big chunk of the data at the top quite frequently), though in this case what Lina was describing sounded somewhat close to the big tree of allocations. Now, it could be any or all of:
* inherently required by the hardware, in which case all you can do is shrug
* good for a first-pass implementation and maybe optimized in the future
* simply not an issue in practice.
Without more information, I would trust that Lina made the right decisions and/or will revise her decisions over time based on data.
- gary_0 2y agoMy impression was just that it was the cleanest way for her to map things on top of the existing kernel structures (which are probably tree-ish). And I highly doubt that there are any actual issues with this aspect of her design; it was just picked out as a contrived example by the blog post. I suspect if Lina's DRM patches had not come from a Rust dev or invoked "RAII theory", and were only advertised as improvements for clarity and conformance with expected behavior, they probably would have been accepted far sooner. (She says as much in her Mastodon post.)
- Longlius 2y agoWhy would you trust that Lina made the right decisions? Is it simply because of her past work? Even experienced engineers regularly make mistakes. It seems like you show up in these threads to give Lina all the benefit of the doubt and her detractors none.
- sunshowers 2y agoOh interesting, in what other threads have I shown up? I would trust her general judgment based on a complex list of factors, including my own personal experience and how my own understanding of the world aligns with hers. I'm exercising my own judgment honed over time.
- st3fan 2y agoBecause it is working code. Not just talk.