From: arne@vajhoej.dk   
      
   On 11/8/2025 6:09 PM, Lawrence D’Oliveiro wrote:   
   > On Sat, 8 Nov 2025 17:14:33 -0500, Arne Vajhøj wrote:   
   >> On 11/8/2025 4:59 PM, Lawrence D’Oliveiro wrote:   
   >>> On Fri, 7 Nov 2025 15:01:23 -0500, Arne Vajhøj wrote:   
   >>>> Anyway the memory safety of Rust makes it clearly different from   
   >>>> C/C++, but if we look at languages typical used for business   
   >>>> applications, then memory safety is common.   
   >>>   
   >>> Do “business applications” need to do network connections?   
   >>   
   >> Absolutely.   
   >>   
   >> Requests coming in over the network. Accessing database servers,   
   >> message queue servers, cache servers etc. during processing.   
   >   
   > Those are well-known sources of memory errors, buffer overflows,   
   > security vulnerabilities caused by (accidentally or deliberately)   
   > corrupted packets etc.   
      
   Yes.   
      
   But I don't think you got the point.   
      
   Rewriting the business application from one   
   memory safe language (Java, C#, Python, Pascal   
   or whatever) to Rust does not help anything.   
      
   If the issue is at the application level, then   
   the old language already prevent buffer overflow   
   and if the issue is in some low level library,   
   then nothing changes by rewriting the application.   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)