Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There is a difference between writing a well contained piece of code inside a memory safe language, and using a memory unsafe language for user space applications.

Additionally removing the dependency on C proves the point that C isn't the only game in town, specially given that the same approach would require Assembly with C anyway.



Agreed, but this is for go only, so it's replacing a mix of go and assembly with a mix of go and assembly. How does that make anything safer?


By not introducing a dependency into OpenSSL, which is the point being discussed.


Missed the indent. I agree then.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: