secana@programming.dev to Rust@programming.devEnglish · 6 months agoWhat are you working on this week? (June. 16, 2024)message-squaremessage-square16fedilinkarrow-up116arrow-down11file-text
arrow-up115arrow-down1message-squareWhat are you working on this week? (June. 16, 2024)secana@programming.dev to Rust@programming.devEnglish · 6 months agomessage-square16fedilinkfile-text
minus-squarePushButton@lemmy.worldlinkfedilinkarrow-up3·6 months agoI am reinventing everything in crates that requires zero dependencies, no unsafe code and the strict minimum of macro usage. Like I did a simple date/time library last week, I started an error management crate this week, which pushed me to start a logging crate. I am using the “log facade” crate for the logging, for compatibility you know, but that’s it. The goal is to minimize the dependencies and create straightforward crates. Most of the time, we really just need a car instead of the 18 wheeler.
minus-squareburntsushi@programming.devlinkfedilinkEnglisharrow-up2·6 months agoHow are you doing a date/time library without platform dependencies like libc or windows-sys? Are you rolling your own bindings in order to get the local time zone? (Or perhaps you aren’t doing that at all.)
I am reinventing everything in crates that requires zero dependencies, no unsafe code and the strict minimum of macro usage.
Like I did a simple date/time library last week, I started an error management crate this week, which pushed me to start a logging crate.
I am using the “log facade” crate for the logging, for compatibility you know, but that’s it.
The goal is to minimize the dependencies and create straightforward crates.
Most of the time, we really just need a car instead of the 18 wheeler.
How are you doing a date/time library without platform dependencies like
libcorwindows-sys? Are you rolling your own bindings in order to get the local time zone? (Or perhaps you aren’t doing that at all.)