00:58 <Sargun> SeanTAllen: Side-question: Pony provides many of the same guarantees as Rust. Have you ever thought of pushing these?

00:59 <SeanTAllen> what do you mean?

01:04 <Sargun> SeanTAllen: A lot of what rust talks about is how they don't experience memory and type safety issues

01:05 <Sargun> I haven't heard any of this rhetoric from Pony

01:13 <slfritchie> IIRC I ran across a "Pony's safety guarantees are the same as Rust's" (paraphrasing here), and I stole it for the Code BEAM talk that I gave last month about Erlang vs. Pony actor model implementations. But I don't recall where I'd read it/heard it.

01:41 <SeanTAllen> Well, it's part of the why use Pony on the website so I'm not sure why you haven't come across it and it's a major point of all the Pony talks. Perhaps you mean something different

03:58 <Sargun> SeanTAllen: The intro to the Rust website:

03:58 <Sargun> > Rust is a systems programming language that runs blazingly fast, prevents segfaults, and guarantees thread safety.

03:58 <Sargun> The Pony site says this in a lot more words, but it's not as straighforward

04:06 <doublec> Sargun: what would you use as a replacement wording on the pony site?

04:33 <Sargun> doublec: Let me as

04:33 <Sargun> This came up because I was taling about Pony with friends

04:37 <doublec> "Pony is a capabilities-secure, actor-oriented, memory safe programming language that is high performance with compile time thread safety guarantees"

04:38 <doublec> still wordy

04:45 <Sargun> "Pony is an actor-oriented, memory and type safe language for getting things done whilst not compromising performance or correctness"

17:58 <Sargun> SeanTAllen: Do you know if WSL could eliminate the need for a separate asio stack on windows?

17:59 <SeanTAllen> It wouldn't.

18:24 <strmpnk> Sargun: WSL is nice for using linux programs but it doesn't allow a single process to blend Win32 and linux APIs. So I wouldn't could WSL as Windows support by itself.

19:05 <strmpnk> s/could/count/ *