This was from 2012. Arguably, we’re already there. Tons of popular computers run signed bootloaders and won’t run arbitrary code. Popular OS vendors already pluck apps from their walled garden on the whims of freedom-optional sovereignties.

The civil war came and went and barely anyone took up arms. :(

Over half a million people or 2 out of 100 Americans died in the Civil War. There was little innocent folks in general public could do to prevent it or minimize losses Personally, I found his “civil war” to be less scary. The public can stamp these problems out if they merely care.

That they consistently are apathetic is what scares me.

Cory always brings so much more work that needs to be done to the table.

It’s not really a functional language, but fwiw this is also common in modern R code via magrittr pipelines.

You still have to name functions.

That’s a good point…I hadn’t thought of that, and I use method chaining all the time! Do you find in Clojure that it is difficult to debug the intermediate states of a “thread” (not sure what term is appropriate here) such that intermediate variables would be more convenient? (I guess I’m thinking from a perspective of JavaScript’s method chaining, which seems similar…and it is somewhat frequent that I need to log intermediate values in a .map.reduce.filter chain.)

For those Googling zig: https://ziglang.org

Yeah, like Forth!

Why not make a PR?

I listened to a few episodes of this and I don’t get it. I guess it’s a parody podcast? I feel stupid admitting that, because obviously it’s supposed to be funny.

Maybe I’m not a hardcore enough developer to ride this ride :)

PR please

The NTSB has opened an investigation.

I think you’d need to know Haskell and the associated idioms for it to be of any use to you.

That has a really ominous parsing for me.

I assume the intention is something like:

When needed, my skill and knowledge shall be given for the public good, without reservation.

And paid Id add. The markets and taxpayers that cover lots of unnecessary stuff should be able to cover these people working for the public good.

Just learn the tricks for Postgres then you don’t need to learn any other DBs :)

At the very end there’s also a button to un-redact those, so the author obviously doesn’t really think there’s an issue using the name.

The bullet points below your experiences are really nice, they show the reader the main aspects and give a quick overview/feel of what you worked on, without wasting time as you said. The blue tags you have are not really my thing, but I enjoy your resume very much.

Flux capacitor is a better name, though :)

I believe this is the case for Canada and some (many? most?) other countries. My previous employer acquired a couple Canadian companies which triggered a much larger, company-wide, discussion regarding “engineering” job titles (e.g., software engineer, sales engineer, …) I want to say that Texas and a couple of other states are similar in that they require licensure to use the title. I think Microsoft changed some of their certification titles for a similar reason.

bfd is slow. lld is pretty damn fast!

The rust version seems to pick only the first best key rotor, but the C version keeps track of several. Unless I’ve misread the code?

C:

for(elem = base; elem != NULL; elem = elem->next){
    currentkey = &(elem->key);
    ind2 = currentkey->indicator[1];
    ind3 = currentkey->indicator[2];
    for(set2=0; set2<26;set2++){
        for(set3=0; set3<26;set3++){

That’s three loops.

rust:

let (_, msg, key, ring) = iproduct!(key_offset..(key_offset + 676), 0..676)
    .collect::<Vec<_>>()
    .par_iter()
    .map(|&(key_index, ring_index)| {

That’s the same code. The two inner loops are folded together, but I don’t see the iteration over the other keys, the outer loop above.

The rust code uses max_by_key in the top loop where the C code has base = nbest_add(base,&key,score);.