[HN Gopher] Surprising Weak-Ref Implementations: Swift, Obj-C, C...
       ___________________________________________________________________
        
       Surprising Weak-Ref Implementations: Swift, Obj-C, C++, Rust, and
       Vale
        
       Author : verdagon
       Score  : 6 points
       Date   : 2022-04-02 17:48 UTC (5 hours ago)
        
 (HTM) web link (verdagon.dev)
 (TXT) w3m dump (verdagon.dev)
        
       | mc4ndr3 wrote:
       | In the safety comparison matrix I submit that JavaScript, being a
       | dynamically typed language, is not safe. You can save a little
       | type signature by writing tons of unit tests.
       | 
       | Go deserves a spot in the comparison matrix. It's not real time
       | (but neither is JavaScript). However, it is easy to use, safe,
       | and fast.
        
         | verdagon wrote:
         | Thats fair, I suppose it depends on how one defines safety. I'd
         | still lean toward JavaScript being safer from a language design
         | perspective (no comment on VM/interpreter implementations!)
         | because there's no equivalent to golang's unsafe pointers. I've
         | updated the page with the grid [0] to be more specific.
         | 
         | I like the idea of putting Golang in the comparison matrix,
         | since Vale will be a strong choice for servers. I'll see if I
         | can fit that in!
         | 
         | [0]: https://vale.dev/comparisons
        
       ___________________________________________________________________
       (page generated 2022-04-02 23:02 UTC)