3 ms·
The only specific statements about Rust quoted in that thread appears to be: > And so Rust has a good set of ingredients there. The problem that I have with it
by aazaa 7y ago
The only specific statements about Rust quoted in that thread appears to be:
> And so Rust has a good set of ingredients there. The problem that I have with it is when I'm working on really hard stuff, I don't exactly know what I'm doing for a long time. And so if the cost of experimentation is driven too high, it actually impairs my ability to get work done.
The rest seems to be a discussion about the problems of memory management in general. It's not clear how much Blow has actually used Rust.
- agumonkey 7y ago> And so if the cost of experimentation is driven too high, it actually impairs my ability to get work done. side note but so far I think that's what made python so wildly used. But that doesn't undermine rust value, there are problems where you want rust features even with the cost.
- faitswulff 7y agoThere's a lot more in the podcast that's discussed in the comments as well, RE: linked lists, multiply owned data structures, and common goals of Rust and the Jai compiler team, but I got lazy with transcribing the audio by hand (it's harder than it sounds!) and left it at that. Besides which, the podcast episode outside of Rust was excellent!
- Santosh83 7y agoIs it possible to use the speech to text feature of your OS to transcribe the podcast quickly? Just curious...
- faitswulff 7y agoA hacky solution is to point your speakers at a device running Google Docs with speech-to-text turned on, but I haven't found anything that handles multiple speakers well - especially with overlapping voices, as happens often in this episode.
- Santosh83 7y agoYup overlapping voices should be a problem. I was thinking more along the lines of you playing the podcast to yourself via headphones and repeating what Jonathan Blow says into your speech to text program. :)
- mikepurvis 7y agoA lot of podcasts get transcribed on Rev, though it isn't free.
- CJefferson 7y agoI'm finding exactly the same problem with Rust -- I am do exploratory programming in GAP (a Python-like language), then rewriting to Rust once I'm confident I have all the basic data structures and code down. The compile speed of Rust alone is painful. Also, when converting C++ code to Rust, I find many places where I'm having to de-optimise code to get it past the borrow checker. Large cyclic data structures which are freed as one piece are annoyingly difficult in Rust.
- adamnemecek 7y agoUse vector granphs.
- anewvillager 7y ago> Large cyclic data structures which are freed as one piece are annoyingly difficult in Rust. If you really are deallocating the cyclic structure all at once, just use an arena and represent each element as an indice. Like https://docs.rs/petgraph/0.5.0/petgraph/ https://docs.rs/petgraph/0.5.0/petgraph/ or https://docs.rs/specs/0.15.1/specs/ https://docs.rs/specs/0.15.1/specs/
- _pmf_ 7y agoJon Blow addresses this in some earlier rant here: https://www.youtube.com/watch?v=4t1K66dMhWk https://www.youtube.com/watch?v=4t1K66dMhWk His point being that now you're effectively implementing a form of manual memory management to circumvent the borrow checker.
- razor45 7y agobruh