[HN Gopher] Twenty Years of Valgrind (2022)
       ___________________________________________________________________
        
       Twenty Years of Valgrind (2022)
        
       Author : fanf2
       Score  : 120 points
       Date   : 2024-08-28 20:42 UTC (2 hours ago)
        
 (HTM) web link (nnethercote.github.io)
 (TXT) w3m dump (nnethercote.github.io)
        
       | moomin wrote:
       | As for the pronunciation, thanks for the tooling, but we'll take
       | it from here.
        
         | mistrial9 wrote:
         | agree - "grinned" is not at all the feeling I get.."grind" on
         | the other hand, like skating.. yes more like it
        
       | jmclnx wrote:
       | A great tool, I hope these fortune 500 Companies that are involve
       | with Linux are supporting the Valgrind Developers.
       | 
       | In reality I really doubt they are.
        
         | orochimaaru wrote:
         | Fortune 500's rarely contribute but use a lot. I work for one.
         | It's usually a tussle between which vendor has managed to
         | convince c-suite that software engineering is a dying
         | discipline and their new genai tool is the utopia.
         | 
         | Most Fortune 500 c suite are bean counters with abysmal
         | engineering or product know how. They can't see past the next
         | quarter earnings report. I doubt long term contribution to
         | meaningful open source is on their list.
        
       | ChrisArchitect wrote:
       | twenty-four years
       | 
       | (2022)
       | 
       | Some discussion then:
       | https://news.ycombinator.com/item?id=32245136
        
         | munchler wrote:
         | 2024 - 2022 + 20 = 22 years, not 24 years.
        
       | theideaofcoffee wrote:
       | In a complex C codebase, valgrind is absolutely indispensable for
       | finding the last few bits of memory that may have leaked out
       | because you got lazy and didn't free() or maybe you wrote
       | somewhere in memory you shouldn't have, it really is like magic
       | sometimes. I know that more recent languages (and some not so
       | recent, looking at you, Ada!) have a lot of this built in by
       | default, but when you need to do these things, you know you need
       | to and it's nice to have a handy all-in-one tool to help out.
       | It's saved me many times from myself when I was writing network
       | code in C and I couldn't figure out where the leaks were coming
       | from, or a performance regression by inspecting the code alone. A
       | quick run of valgrind had that fixed in minutes.
        
       | michael1999 wrote:
       | I remember how much my work improved when I got to use Purify.
       | The pager just stopped going off after a while.
        
       ___________________________________________________________________
       (page generated 2024-08-28 23:00 UTC)