Viewing profile — first_amendment

Jokes aside, semantically "implore" and "swear" are actually really good primitives for static analysis. "swear" is only dangerous because there's a chance it gets out of sync with…

One is a requirement, the other is a promise. The promise "result >= 0" is necessary because the compiler may not be able to prove that on its own.

I'm not talking about unikernels. I'm talking about the VMs that isolate them from each other. The VM isolation mechanism is considered secure enough to isolate malicious users, wh…

Unfortunately containers aren't considered secure enough for malicious users while VMs are.

Hard work and smart investing sustained over a period of 30 years.

As it stands now, adding threading to JS has a negative expected value. There is more potential downside than potential upside. It's illogical and irrational to undertake the effor…

JavaScript can already do concurrent searching. Concurrent is logical, parallel is physical. Efficient parallel GC is non-trivial to implement. In the most common implementation, y…

C++11 allows you to write natural "value-oriented" code without paying a copying cost. This is thanks to RVO (return value optimization) and move semantics.

I made an argument. What's yours? You just made a statement of opinion without any justification. Additionally your opinion is wrong, by simple counter example. Rust's type checker…

For your parallel search example, the data set has to be extremely large for parallel searching to have a significant improvement. When does a client-side JS app have access to man…

This isn't about "paternalistic caution," it's about purposeful and sensible engineering. JavaScript wasn't designed for threading, and it's a less natural fit for it compared to a…

> I just don't think that we have sufficient evidence to conclude that using type systems to aid the development of concurrent code actually leads to better concurrent code. This i…

JavaScript is already concurrent. It isn't parallel though. Is there any real world application that currently cannot exist without this feature? It seems like a solution looking f…

It's unfortunate that the new version still creates __new__ using exec(). Doesn't seem necessary at all. Instead of generating the method as a string with the argument names filled…

Only versions 1.4 and below. Versions 1.5 and above do not require an X server. Version 1.5 has been available for 5+ years: https://ariya.io/2012/03/pure-headless-phantomjs-no-x11…

Feistel is a permutation. That means it's a 1:1 mapping between a 16-bit # to another 16-bit #. You run Feistel for each number 0->65535 (corresponding to the "stage" of the Fizzle…

You should time it :)

Always love seeing applications of Feistel cipher. Used it with AES as the PRF for implementing FPE in legacy systems. Just want to note that this approach (regardless of PRF) prob…

Erlang occupies a similar space compared to Haskell, in terms if it being a functional language with M:N green threads. It is possible, there are many stack swapping libraries in C…

I approximately agree with you but there are lots of reasons I'd prefer Rust over Haskell. All data is thunked and boxed in Haskell, it's all heap-allocated and garbage collected, …

Interesting. The problems section isn't really convincing to me though. Especially, indirect function calls for IO functions seem fine since IO is usually much slower than a functi…

I wonder if Rust could support pluggable concurrency models (with the accompanying runtime support). That's what Haskell does and it seems to work. At the outset that seems like a …

async/await is nice duct tape to integrate cooperative concurrency into a thread-based concurrency model but it has the drawback of creating an incompatible sub-language for functi…

You essentially agree with me. Aborting with a stack trace is still an abort. It doesn't need to be catchable.