←back to thread

Hacker Typer

(hackertyper.net)
272 points rvnx | 2 comments | | HN request time: 0.422s | source
Show context
SamWhited ◴[] No.41879318[source]
In school I worked as an intern for a U.S. defense contractor (which I feel rather bad about now, but that's neither here nor there). Every now and then some important general or captain type would show up for a meeting and walk around and look at what all the various labs were doing. When they came to the room where all the interns sat we would all pull up hacker typer and just furiously type away while they were looking in the door.

The important person would always be very impressed and say what a good job we were doing, and our boss who was showing them around (and knew exactly what we were doing) would have to nod and sweat bullets and then would get furious with us afterwards (but it was worth it and we did it every time we knew someone was coming to do an inspection).

replies(3): >>41882189 #>>41882638 #>>41884643 #
syncsynchalt ◴[] No.41882638[source]
Ahh, I used to queue this up on another screen when I needed things to look "busy":

    cat /dev/random | hexdump -C | grep 'ca fe'
Note that it runs a lot faster now than it used to in the 90s.
replies(3): >>41883235 #>>41884214 #>>41888373 #
1. 0points ◴[] No.41888373[source]
(Sorry if too off-topic)

I just saw this and thought this was pretty cool! Running your command in nushell, and eventually aborting it gives the following output

    ^CError: nu::shell::terminated_by_signal

      × External command was terminated by a signal
       ╭─[entry #28:1:32]
     1 │ cat /dev/random | hexdump -C | grep 'ca fe'
       ·                                ──┬─
       ·                                  ╰── terminated by SIGINT (2)
       ╰────
Just wanted to random praise the nushell team for this amazing level of detail!
replies(1): >>41918851 #
2. yencabulator ◴[] No.41918851[source]
Ehh. Nushell error handling is poorly built and buggy as hell. I wanted to use it, I really believed in the sales pitch, but it's just utterly unreliable and I have zero faith left in them ever actually fixing it.

- error handling is neglected in the basic design: <https://github.com/nushell/nushell/issues/10633>, <https://github.com/nushell/nushell/issues/10856>, <https://github.com/nushell/nushell/issues/8615>, <https://github.com/nushell/nushell/issues/6617>

- control-C interrupts its internals with obviously-wrong error: <https://github.com/nushell/nushell/issues/8828>, is midhandled in other ways <https://github.com/nushell/nushell/issues/8206>

- something is horribly wrong with the basic design of command-line arguments: <https://github.com/nushell/nushell/issues/9939>, <https://github.com/nushell/nushell/issues/9766>

- they're getting the fundamentals of globs on command lines wrong: if you pass string literals to an external command, they're still processed for globs. this means `ls ""` (internal) and `^ls ""` (external) behave differently: <https://github.com/nushell/nushell/issues/9558>