3 ms·
I'd rather trust 5 libraries written in a memory safe language than one written in C. Sure, if the memory safe language comes with a package manager that happe
by jopsen 2y ago
I'd rather trust 5 libraries written in a memory safe language than one written in C.
Sure, if the memory safe language comes with a package manager that happens to have postinstall hooks, the picture might be different.
But scanning some go packages to see that they don't do I/O is rather feasible.
- apitman 2y agoWhat type of problem for the author's workflow (rendering markdown files) are you expecting as a result of them using C?
- tuveson 2y agoWhy? It's a static site generator. He controls the inputs - there's basically no attack surface. I can't think of a situation where lack of memory safety would be less of a problem.
- exe34 2y agowhat's the trust model that you think the author should be using here?