by steelbrain
1 subcomments
- The mentions of curl on this website are misleading and/or outdated. Curl is dropping the rust/hyper backend. See https://daniel.haxx.se/blog/2024/12/21/dropping-hyper/
- I find it strange that this web site completely ignores the Java ecosystem, which offers memory-safe implementations for most of the protocols and services listed.
- This site is curious in that in incorrectly categorizes go as memory safe.
Perhaps in part because the sponsors are invested in using go and benefit from its inclusion in a list of memory safe languages.
by pizlonator
2 subcomments
- > Languages that are not memory safe include C, C++, and assembly.
False.
C and C++ are not memory safe if you use the most common and most performant implementations, sure.
At some point these folks are going to have to accept that caveat
- The annual report of this org is pretty underspecified. There are numerous directors. Are they getting paid under "ops & admin" (11%)? Is "advancement" (12.3%) marketing?
Prossimo gets 6.8%. Does that money go to programmers? Are people whose works are being rewritten and plagiarized offered money to do the rewrite themselves or does it go to friends and family?
Why does an org that takes donations not produce a proper report?
by checker659
2 subcomments
- I never understood why software has to pay for the lack of memory safety primitives in the hardware.
- Now do type safety.
by squirrellous
4 subcomments
- [flagged]
- [flagged]
by yhhkppqvd62
0 subcomment
- [flagged]
- [flagged]
by redbeeswimming
3 subcomments
- [flagged]