I think it’s an American thing primarily in liberal arts / social sciences.

I'm trying to get shock diamonds going, that's how you find the *real* bugs

Also if you find your own pet cause or talking point reflected in this unhinged document, go within yourself, my brother. You are a fellow traveler to some of the dumbest enemies the academic enterprise has ever had.

You can just use your wallet app now, there’s a little bit of set up still but it’s a lot closer.

spanner? s3?

the internet?

It’s been a long held opinion of mine that the American system should rebalance the distinction between software *engineering* and computer *science* degrees. Trying to make CS a universal program means it fails at the science side of things.

Oh yeah I forgot that as well.

I wouldn’t go quite so far, typically includes discrete math, intro to probability & stats. You will find very few logic, semantics or other theoretical cs courses at the undergraduate level. That’s one of the reason I came it Paris for the MPRI

Even if I _can_ solve them, it’s not a good experience when modifying a function deep in your code cause an Axum handler to fail. I understand how the compiler gets to that conclusion though and that’s the problem with auto traits

Yeah I often use the trick of defining an identity function that asserts the bounds I want but it’s annoying since you need figure out which function is causing it.

but that’s solving the “auto-traits problem” by just just not having auto traits no? The same difficulties could occur with any auto trait eg a hypothetical Forget

if there was an easy way to assert that the future returned by an `async fn` satisfied bounds that might at least provide an escape hatch to push the blame down to the correct lines of code.

idk how I would approach this from-scratch and there may not be a pareto improvement either. The experience where modifying an async function deep in your call-graph causes a far-away descendant to fail because some (seemingly) random future is not Send isn't great though.

et pourtant c’est sans doute aussi parmis les points les plus négatifs de l’expérience de chercheur en France! Un changement qui coûte rien (voir fait des économies) et qui améliore le quotidien et la perception des chercheurs c’est rare!