@ManishEarth @bascule @munin If the lang can’t do TLS out of the box then it can’t network, so it’s not ready to write software in.
-
-
Replying to @ManishEarth
@ManishEarth@bascule@munin because the bindings are to massive piles of shit?1 reply 0 retweets 0 likes -
Replying to @rantyben
@rantyben@ManishEarth@munin protip: it’s all massive piles of shit, implementing a shitty protocol. Humanity at its best… err, worst2 replies 1 retweet 1 like -
Replying to @bascule
@bascule@ManishEarth@munin nonetheless, I am not going to waste cycles grokking a shiny memory-safe lang that still uses openssl for x5091 reply 0 retweets 1 like -
Replying to @rantyben
@rantyben@ManishEarth@munin check out suruga, but please be aware it’s not exactly at a useful stage yet1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@ManishEarth@munin all I said AT THE START was “someone let me know when this is ready” :)1 reply 0 retweets 0 likes -
Replying to @ManishEarth
@ManishEarth@bascule@munin ok, so now I have to wait for the language to be ready AND some third party lib before I can write software.3 replies 0 retweets 0 likes
@ManishEarth @rantyben @munin there’s suruga as a native Rust TLS implementation:https://github.com/klutzy/suruga
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.