6 ms·

I'm a little disappointed that it's not written in Rust.

• emmelaich 6mo ago
  I sense an opportunity for you.
• tstack 6mo ago
  Speaking as the author, I too wish it was written in Rust. But, I started it in 2007 when I needed to get practice with C++ for work. At this point, there's so much code in lnav, rewriting would be a long process. There are some sub-components[1] that are written in Rust though. A new project called logana[2] is written in Rust and is headed in a good direction. Use/contribute to that if you're really interested. [1] - https://github.com/tstack/lnav/tree/master/src/third-party/lnav-rs-ext https://github.com/tstack/lnav/tree/master/src/third-party/l... [2] - https://github.com/pauloremoli/logana/ https://github.com/pauloremoli/logana/
  • Duke64 6mo ago
    Thanks for the reply and the tip about logana. As I mentioned in the following comment[1], that was meant more as a joke. Thanks for your work! [1] - https://news.ycombinator.com/item?id=47514276 https://news.ycombinator.com/item?id=47514276
• kermatt 6mo ago
  How would this improve the functionality of lnav?
  • Duke64 6mo ago
    Just so we're clear, this was more or less a joke! As far as I'm concerned, lnav is just fine as it is. There's no urgent need to rewrite it. Why I wrote the comment: I saw the headline, checked out the website, and thought to myself, “Hey, cool—a new handy tool.” As is typical for “cool new and handy tools,” these are usually written in Rust these days ;) That’s why I was “disappointed” (not really). I didn’t realize until later that lnav was created in 2007. Again: the tool is great, thanks and kudos to tstack for the work.