Live data from Hacker News

Show HN: Ov – feature rich terminal pager

github.com

21–30 of 53 posts

Re: Show HN: Ov – feature rich terminal pager

#21
post #16

Earlier quoted context omitted.

Huh?

I'm not part of the Go cult, so I simply do not get why people would start brand new projects in it when so many other good languages exist that actually seem to have taken off and become popular enough to survive long-term.

Okay but why _not_ use go? You never gave a reason.

Re: Show HN: Ov – feature rich terminal pager

#23
post #19

[flagged]

this is useless bias. Get rid of it.

How is it useless bias? Go has not proven itself that it has what it takes to be a language that a developer would want to use. What problems has it solved that no other language has solved? What problems has it solved better than other languages that also solved them?

The answers to those two questions have not impressed me. So, if my bias is simply using basic logic to evaluate a language, then I think I'm going to keep using my "useless bias".

Re: Show HN: Ov – feature rich terminal pager

#24

Earlier quoted context omitted.

I'm not part of the Go cult, so I simply do not get why people would start brand new projects in it when so many other good languages exist that actually seem to have taken off and become popular enough to survive long-term.

Okay but why _not_ use go? You never gave a reason.

There are multiple lengthy writeups on the good and bad of Go that have made it to the HN front page multiple times over the past 5+ years. The little search bar at the bottom HN works pretty well, sometimes better than Google due to HN's habit of promoting interesting and well written blog posts, podcasts, and talks about technical subjects.

Re: Show HN: Ov – feature rich terminal pager

#26
post #19

Earlier quoted context omitted.

this is useless bias. Get rid of it.

How is it useless bias? Go has not proven itself that it has what it takes to be a language that a developer would want to use. What problems has it solved that no other language has solved? What problems has it solved better than other languages that also solved them? The answers to those two questions have not impressed me. So, if my bias is simply using basic logic to evaluate a language, then I think I'm going to…

It doesn't matter to the person using the software.

Re: Show HN: Ov – feature rich terminal pager

#28
post #19

Earlier quoted context omitted.

this is useless bias. Get rid of it.

How is it useless bias? Go has not proven itself that it has what it takes to be a language that a developer would want to use. What problems has it solved that no other language has solved? What problems has it solved better than other languages that also solved them? The answers to those two questions have not impressed me. So, if my bias is simply using basic logic to evaluate a language, then I think I'm going to…

It's a matter of taste, i do adhere to go simplicity and see point like feature constriction as an alternate approach that make deep sense to me.

Re: Show HN: Ov – feature rich terminal pager

#29
post #18
post #9

If the log-file viewing capabilities look interesting to you, check out lnav, which is built for that and excels at it: https://lnav.org/

Nice! I've been in rapid-response situations where I had to pull logs from various sources (including embedded devices) that weren't unified in a central logging service. I could get the logs onto my workstation, but then manually lining up who-saw-what-when involved a headache, even with Emacs. lnav seems to have a few features to support this. One very useful feature for this I didn't see listed for lnav was to sup…

> One very useful feature for this I didn't see listed for lnav was to support adjusting for timestamps in different timezones, like maybe you have a desktop's log in local time that you're trying to reconcile with servers. (A related but less-important bonus would be to be able to specify smaller arbitrary clock drift/offsets for each log.)

You can adjust the timestamps for a file using the ":adjust-log-time" command (https://docs.lnav.org/en/latest/commands.html#adjust-log-tim...). For example, if you wanted to shift the timestamps back an hour, you can do:

    :adjust-log-time -1h
The shift is applied to the messages in the file that the top line in the view belongs to.

If you want to do the shift programmatically, you can UPDATE the "time_offset" column of the "lnav_file" table directly (see https://docs.lnav.org/en/latest/sqltab.html#lnav-file)

Re: Show HN: Ov – feature rich terminal pager

#30
post #29
post #18

Earlier quoted context omitted.

Nice! I've been in rapid-response situations where I had to pull logs from various sources (including embedded devices) that weren't unified in a central logging service. I could get the logs onto my workstation, but then manually lining up who-saw-what-when involved a headache, even with Emacs. lnav seems to have a few features to support this. One very useful feature for this I didn't see listed for lnav was to sup…

> One very useful feature for this I didn't see listed for lnav was to support adjusting for timestamps in different timezones, like maybe you have a desktop's log in local time that you're trying to reconcile with servers. (A related but less-important bonus would be to be able to specify smaller arbitrary clock drift/offsets for each log.) You can adjust the timestamps for a file using the ":adjust-log-time" comman…

Thanks!
Post reply on HN