asa
robotics software and fast cars, undergrad at mit
anglesideangle.dev
- any rust gurus know how i can customize the state machine impl of Future that rustc generates from async fns
- current best idea is to make a proc macro that takes the body of the function and inserts it into a new function eg. fn wrapped_fn() -> impl Future<...> { future_wrapper::new( async {<previous body>} ) }
- the serious thesis here is: design is about empathy, and about compromise, and you just can't do those things properly if you're a chud who thinks women should never have been let out of the home
- [Not loaded yet]
- damn elixir actually seems really cool maybe the vm is worth it...
- nah ruby is irredeemable (i haven't used ruby)
- every programming language will be irredeemably bad until we replace modern cpus with hardware interaction combinator evaluators that compute haskell with unrestricted parallelism
- back to `const constexpr int getter() const` jail you go
- idiomatic code btw
- [Not loaded yet]
- isn't the entire reason behind jai not being public that blow thinks "open source bad, actually" is a contrarian take
- [Not loaded yet]
- very easy to un c-pill someone by showing them how many nasty optimizations their cpu does to interpret their precious assembly
- maybe this comes from how much i use rust, but odin feels like a poorly thought-out reaction to complexity. elements of its design are haphazard and incongruous; it feels like it exists to say something rather than to be used
- i haven't used either zig or odin extensively but i got the impression zig is much a more cohesive c-successor language
