burntsushi

5 ms·

31.
by burntsushi 4mo ago
Thank you. <3 There were lots of reasons that went into me posting this. First and foremost is that this is a disease of chaos that is prone to misdiagnosis. I want to shout this from the roof tops to spread awareness. I don't have
32.
by burntsushi 4mo ago
Thank you. <3 It's been a trip. The worst thing that has happened, but also the best. It has definitely given me a new perspective on life, that's for sure. My favorite side effect is that I now love all foods. Prior to this, I
33.
by burntsushi 5mo ago
I have been thinking about this sort of progression too. One thing I wonder about is network effects. Are they even important? Now, for sure. Will they be so in a year? I don't know. I'm thinking about tooling centralizing on comm
34.
by burntsushi 5mo ago
That's a complaint against how time zones are themselves named and organized. See https://ftp.iana.org/tz/tzdb-2022b/theory.html for all the gory details. Using +4 or +5 explicitly instead of a time zone when
35.
by burntsushi 5mo ago
(I am on the Rust libs-api team. I say "we" below, but I didn't do any of the amazing new range type work.) > Why replace the already existing std::range in-place with the new version We didn't. `std::range` is new. T
36.
by burntsushi 5mo ago
Quite plausible. I built most of it in May 2025 (1 year ago) before I even looked at LLMs for coding, and announced it in Oct 2025[1]. I started it principally as a mechanism to dog-food Jiff[2]. Jiff has not been obsoleted by LLMs and is
37.
by burntsushi 5mo ago
Maybe. But it's longer and already taken on crates.io.
38.
by burntsushi 5mo ago
Oh neat! TIL about `git last-modified`. That looks like a fun one to explore. Thank you.
39.
by burntsushi 5mo ago
Yeah totally right. I just don't know enough about git to figure it out. But a sibling commenter helped a lot. And yeah perf probably doesn't matter much. But, like, running my approach on the Rust compile repo takes at least minu
40.
by burntsushi 5mo ago
Oh interesting! That is indeed quite a bit faster. I'll have to noodle on this one. `bttf tag exec` works with arbitrary commands that can print any kind of date. But your approach require a different access pattern. I can either speci
41.
by burntsushi 5mo ago
ripgrep is a required dependency of codex when installing it via brew on macOS. So you should at least not see it if you fall into that scenario. :-)
42.
by burntsushi 5mo ago
I did. I always do. I just missed this one. Or if I saw it, it didn't register for me and felt like it was just an old archaic tool. Which... is probably still true, but I under-estimated its mindshare. Just an honest unknown unknown.
43.
by burntsushi 5mo ago
My decisions about naming aren't limited or prescribed by what is in a standard or not. :-)
44.
by burntsushi 5mo ago
I've renamed the project to bttf :-)
45.
by burntsushi 5mo ago
Oh yes definitely. Was always the plan. I was honestly just hoping someone would publish a crate to do that for me. To be clear, I don't mean publishing a crate to read an environment variable. Of course. I mean a crate that converts a
46.
by burntsushi 5mo ago
Back to the Future jokes never get old. I love it. I still want one of those hover boards!
47.
by burntsushi 5mo ago
@dang - Could you update the post title please to say "bttf" instead of "Biff"? Thank you!
48.
by burntsushi 5mo ago
You win the naming contest. The project has been renamed: https://github.com/BurntSushi/bttf/pull/14
49.
by burntsushi 5mo ago
Yeah this was before my time. I never did email from a terminal. Which probably explains why I was okay with naming it Biff. In any case, I've renamed the project to bttf: https://github.com/BurntSushi/bttf/pu
50.
by burntsushi 5mo ago
Yes!!! To spell it out (with the new biff -> bttf name): $ bttf time seq monthly -w 2-tue -u 1y | bttf time fmt -f '%c' Tue, Jun 9, 2026, 11:15:11 AM EDT Tue, Jul 14, 2026, 11:15:11 AM EDT Tue, Aug 11, 2026, 1
51.
by burntsushi 5mo ago
Oh nice thank you!
52.
by burntsushi 5mo ago
I like this
53.
by burntsushi 5mo ago
I honestly don't know. Which is... Not Great.
54.
by burntsushi 5mo ago
That's... not terrible. Biff isn't exactly popular (yet?), so a name change isn't out of the question. Both of those names (and `biff`) are already taken on crates.io. Which is maybe not a huge problem. IDK. Naming is hard.
55.
by burntsushi 5mo ago
Yes! dateutils is great! I have a comparison about it here: https://github.com/BurntSushi/biff/blob/master/COMPARISON.md... The comparison with GNU date is also likely informative.
56.
by burntsushi 5mo ago
I'm the author of Bttf. I just wanted to share a really cool example of something that Bttf can do that I _think_ is kinda hard to do otherwise. (And also, I want to make an assertion about it and I hope this will lead to me being wron
57.
by burntsushi 5mo ago
Yeah the name collision is unfortunate, but probably fine. The name Biff was just too good to pass up. The name comes from the fact that Biff is a character in Back to the Future, and it rhymes with Jiff[1]. Jiff is the datetime library t
58.
by burntsushi 5mo ago
This is a fair critique actually. And this shouldn't be the default. It is for now because I haven't gotten around to making Biff read your POSIX locale settings and converting them to a Unicode locale. If you build with `cargo bu
59.
Bttf is a command line datetime Swiss army knife(github.com)
183 points by burntsushi 5mo ago|99 comments
60.
by burntsushi 7mo ago
> for simple string literals it will definitely lose to Hyperscan and Rust regex since they have a high effort left-to-right SIMD algorithm that we cannot easily use I think "simple string literals" undersells it. I think that

More ›