Viewing profile — withoutboats3

> I don't remember the details with encryption but it was basically you have to ship a breakable version for the rest of the world, and you generally sometimes ship a backdoored ve…

Your anti-semitism is vile and you should be shunned by any upstanding person in society.

This is indeed a great quote (one of many gems from Sir Tony) but I think the context that follows it is also an essential insight: > The first method is far more difficult. It dem…

We can tell you think that when we use your app.

Cuckoo filters outperform bloom filters and allow dynamic insertion and deletion (unlike bloom filters, which only allow insertion). The trade off is that insertion can fail if the…

The problem in this conversation is that you are equivocating between "fixing memory safety bugs" and "preventing memory safety bugs statically." When this blog post refers to "mem…

genuinely so sad to me that you are still grinding this axe. if your fantasy design works so much better - go build it then!

Initial comments as I write this are all negative, and also responding to something the blog post didn't claim. The only time it says faster than C is when talking about a language…

The alternative to C++ that I meant was Rust, which statically prevents data races.

The occurrence of data races depends on the specific non-deterministic sequence of execution of concurrent codepaths. Just because you have 100% code coverage does not mean you've …

This is exactly the attitude this blog post spends its first section pretty passionately railing against.

The IO aspect is not a surprising flaw but it's disappointing to learn that Erlang lets any process enumerate all the other ones.

Joe Armstrong goes to lengths to describe the benefits of "privately addressable" actors in his thesis (though he uses different terminology). As far as I'm aware, Erlang actors ar…

100%. So tiring that the discourse around this is based on 15 minute demos and not actual understandings of the trade offs. Varun Gandhi's post that you link to is great. Based on …

Better newtypes are the answer. Consider Java for example. In Java, interfaces are even more restrictive than traits: only the package which defines the class can implement them fo…

Implementations are not imported at all because they are not named. Like I wrote, named implementations (ala ML modules) is a valid alternative, but one with a much greater annotat…

Your conclusion is correct. I'm very happy with the two that Rust picked and tired of people pretending that there will be a magical pick three option if we just keep talking about…

Implementations are not exported or public at all: they are used in functions and those functions are exported. For correctness, you want those implementations to be resolved consi…

This post is written by a fan of implicits, so it frames it as "better" than traits, though at the end it admits it is in fact a complex trade off, which is the truth. In my opinio…

[flagged]

[flagged]

I freely admit I’m frustrated by the discourse around async Rust! I’m also very frustrated because I feel I was iced out of the project for petty reasons to do with whom I’m friend…

To be fair, I’m not sure if there exists any zero cost IOCP library. The main way people use IOCP is via mio via tokio. To make IOCP present a readiness interface mio introduces a …

[flagged]