| 3 Nov 2024 |
 Ribbon | In reply to @_discord_1223818635491934208:t2bot.io
So what if some crates which you download from the database is intentionally vulnerable to remote attacks???
How can you trust those pesky libs which you download from crates?
- Only popular and well-maintained libraries are used
- The libraries can be forked to improve security
- Linux also relies on external libraries, like XZ. But they are forked because most C programs don't use a dependency manager.
| 16:12:28 |
| Ribbon | 
Download wget-linux.gif | 16:28:28 |
| Ribbon | 
Download tamandua-anteater.gif | 16:30:12 |
| Ribbon | 
Download i-use-arch-btw-arch-linux.gif | 16:30:59 |
| Ribbon | In reply to @draft_isa:matrix.org
sent an image. LMFAO. | 16:31:04 |
| Ribbon | 
Download image.png | 16:47:34 |
 auronandace | You probably generate or find enough memes yourself to warrant a separate memes room. | 16:48:39 |
| auronandace | That was more of a semi serious suggestion. Maybe we can keep this room for random discussion of topics and have a separate memes room for those interested in that. | 16:52:28 |
| Ribbon | In reply to @auronandace:matrix.org
That was more of a semi serious suggestion. Maybe we can keep this room for random discussion of topics and have a separate memes room for those interested in that. I will suggest. | 16:58:01 |
 doriancodes | Hey, you forgot to mention libuv, luv and luarocks ports https://matrix.to/#/!BHaccoJMIJlvJsIroP:matrix.org/$kwaKSgHw_S5xm-mLq82KeOGdjPayE6bhE8iiRuHUXqM?via=matrix.org&via=t2bot.io&via=tchncs.de | 17:58:16 |
| Ribbon | In reply to @doriancodes:matrix.org
Hey, you forgot to mention libuv, luv and luarocks ports https://matrix.to/#/!BHaccoJMIJlvJsIroP:matrix.org/$kwaKSgHw_S5xm-mLq82KeOGdjPayE6bhE8iiRuHUXqM?via=matrix.org&via=t2bot.io&via=tchncs.de True, libuv was packaged a while ago.
Does it work?
| 18:04:44 |
|  erklig joined the room. | 18:05:28 |
| Ribbon | @room We created the Memes room to offload this room, if you have memes post there.
https://matrix.to/#/#redox-memes:matrix.org | 18:25:28 |
| doriancodes | In reply to @draft_isa:matrix.org
True, libuv was packaged a while ago.
Does it work? It was not working, but just a wip. | 18:26:16 |
| 4 Nov 2024 |
| Ribbon | Ron Williams: https://www.quantamagazine.org/novel-architecture-makes-neural-networks-more-understandable-20240911/ | 03:58:53 |
 Ron Williams | Very interesting article. | 04:14:54 |
| Ron Williams | In reply to @doriancodes:matrix.org
It was not working, but just a wip. We generally don't talk about work in progress much in the monthly report, unless it's a key feature and we want people to know we are making progress on it. We would rather focus on completed work, so the audience gets the impression we are "accomplishing" stuff. But we are very grateful for your contributions, moving WIP forward is a big deal, especially when its an important library. | 04:18:30 |
| Ribbon | 
Download image.png | 04:24:50 |
 Nathan Petrangelo | People usually talk about the lack of an ABI as the reason Rust doesn’t do dynamic linking, but I feel like another big reason is the Monomorphization | 05:02:54 |
| Ron Williams | In reply to @holobrine:matrix.org
People usually talk about the lack of an ABI as the reason Rust doesn’t do dynamic linking, but I feel like another big reason is the Monomorphization There was discussion at RustConf on dynamic linking, and Monomorphization was a key concern. | 05:03:44 |
| Ron Williams | "No royalty fees on generated code" meaning that some compilers included royalty fees on generated code. | 05:04:52 |
| Ron Williams | This was usually done by licensing a custom libc. | 05:05:20 |
| Ribbon | In reply to @rw_van:matrix.org
"No royalty fees on generated code" meaning that some compilers included royalty fees on generated code. When you met GCC? | 05:05:43 |
| Nathan Petrangelo | I’m thinking even if you had the best possible ABI for rust, one of Rust’s nice things is only compiling what you need from the generics, and that kinda doesn’t fly with dynamic linking, where you only get what was already compiled for you | 05:05:47 |
| Ron Williams | I don't recall, but I think it was 1989 or so | 05:06:30 |
| Ron Williams | In reply to @holobrine:matrix.org
I’m thinking even if you had the best possible ABI for rust, one of Rust’s nice things is only compiling what you need from the generics, and that kinda doesn’t fly with dynamic linking, where you only get what was already compiled for you I don't think Rust dynamic linking will every produce as good results as full compile. I think there will be a lot of compromises. So it will probably be a choice. | 05:07:37 |
| Ribbon | As everything, there's pros and cons.
Static linking has more pros than cons today. | 05:08:34 |
| Nathan Petrangelo | Yeah
All this said though, from an OS pov, dynamic linking to syscalls with a Rust-like ABI could still make sense because syscalls are already only compiled once for your machine and cannot participate in generics and Monomorphization anyway. Syscalls have constraints keeping them from benefiting from static linking. Maybe Rust already knows this and doesn’t recompile std every time like it does everything else 🤔 | 05:19:46 |
| Nathan Petrangelo | Dynamic linking is probably only conceptually possible if you don’t use generics. Trait objects could probably be allowed though, because they only carry a pointer and a vtable. That would probably be the primary way of carrying type safety through the ABI boundary without making all types concrete. | 05:33:08 |
| Nathan Petrangelo | So a dynamically linked library could have functions with trait objects as parameters when they don’t want to constrain the allowed types to just theirs | 05:34:44 |
