3 ms·
I don't know why I can't reply to your reply, so I'll post it here. My argument is that Rust _still_ isn't ready for the Cryptography library because it's not
by ghoward 6y ago
I don't know why I can't reply to your reply, so I'll post it here.
My argument is that Rust _still_ isn't ready for the Cryptography library because it's not portable enough.
And I am not a direct user of the Cryptography library. I am an indirect user on x86_64, so I am unaffected. They have kept their implicit promise to me.
- pjmlp 6y agoThe only people that can be pissed off by promises are paying customers. So those paying to Cryptography developers, are the ones to be pissed off, IF their platforms aren't being considered.
- ghoward 6y agoDoes that include the customers of https://fishinabarrel.github.io/ https://fishinabarrel.github.io/, the company owned by one of the Cryptography developers?
- pjmlp 6y agoYes, assuming they are paying for it and are not able to use it on the use cases they are paying for. Then again, they clearly mention on that page: " Please put us out of business. Stop writing C/C++. Probably you should also sandbox your software. "