blog

commit: c400edee7e8878604c349735daab2cd2f1e6f2ec
parent 919f5977fc3a0d262cfae94be85c5aba95538b66
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Thu, 29 Aug 2019 00:25:21 +0200

articles/Rust sucks as a system language: s/\.la/\.a/

Thanks [[sroracle]]

Diffstat:
M
articles/Rust sucks as a system language.xhtml
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/articles/Rust sucks as a system language.xhtml b/articles/Rust sucks as a system language.xhtml
@@ -9,7 +9,7 @@
 	<li>Static Linking isn't well integrated in packaging systems (it's more often used for a minimalist rescue system, which tends to be a completely separated system)</li>
 	<li>Dynamic and Static Linking have both points for security and it all goes down if the system/environment is controlled or not (and any code in a broken environment is going to be broken anyway)</li>
 </ul></p>
-<p>Additionally as far as I know, there is also no shared location on the system for static libraries (<code>.la</code> files in C) nor source code either (instead of binaries it could be the source).</p>
+<p>Additionally as far as I know, there is also no shared location on the system for static libraries (<code>.a</code> files in C) nor source code either (instead of binaries it could be the source).</p>
 <p>So we end up with applications packages that are easy to spread out but difficult/impossible to maintain in the long term… I would call that a virus, good or evil.</p>
 
 <h2>npm-like scene for libraries</h2>