[HN Gopher] Exploring Linux command-line space time
       ___________________________________________________________________
        
       Exploring Linux command-line space time
        
       Author : bertman
       Score  : 108 points
       Date   : 2023-09-26 17:21 UTC (5 hours ago)
        
 (HTM) web link (fabiensanglard.net)
 (TXT) w3m dump (fabiensanglard.net)
        
       | chrsw wrote:
       | The GitHub repo link is broken
        
         | M95D wrote:
         | https://github.com/fabiensanglard/st
        
       | metadat wrote:
       | This is excellent across a few key dimensions.
       | 
       | - Clear and concise code.
       | 
       | - Clear communication: writing, technical explanations, and
       | conveyance of thought process.
       | 
       | - Thorough and systematic.
       | 
       | Major kudos to the author. It was a fantastic refresher on the
       | mechanics of fork() for me!
       | 
       | This kind of article is the reason I troll HN so much.
       | Occasionally gems pop up.
        
         | otachack wrote:
         | Fabian is a treasure. He also made the Game Engine Black Books
         | covering Wolfenstein 3D and Doom.
         | 
         | https://fabiensanglard.net/gebbdoom/
        
       | bschup wrote:
       | Would be curious to see how a "Hello World!" in Zig compares.
        
       | fsckboy wrote:
       | this is a small personal nit complaint, but increasingly I see
       | "Linux command-line" used to refer to things which have nothing
       | to do with command-lines per se, which to me suggests some cli-fu
       | with p|pes || other tricky \\\&\\\&& if-fi $(things).
       | 
       | Perhaps we need some better vocabulary to separate these ideas,
       | but the world of unix includes "shell" ideas, and their interplay
       | with cli, there's ascii text ttys, there's ansi tty control and
       | TUIs, and what this article is about, traditional unix userspace
       | process-space, system calls, C-libs, compilers vs interpreters
       | got skipped, but C-vs-Rust, just all without the overhead of GUI
       | frameworks which brings a bit more clarity to timings but they
       | don't absolutely, to do timings could be better to write a
       | program to launch all these things and make sure that program is
       | "sticky" in unix space-time.
       | 
       | This is a good article, but because I like to search for things
       | again later, just as a headline I wouldn't really call this
       | exploring Linux command-line space or time
        
       | 5- wrote:
       | > Following process/thread creation is done via netlink(7).
       | 
       | shouldn't ptrace with PTRACE_O_TRACEFORK (etc.) be enough (and
       | much easier)?
       | 
       | the high overhead of strace the author notes is due to it doing
       | PTRACE_SYSCALL, which is not needed here.
        
       ___________________________________________________________________
       (page generated 2023-09-26 23:00 UTC)