🦀 I've improved the implementation behind all the string formatting macros in Rust: println, panic, format, write, log::info, etc. (Everything using format_args!().) They will compile a bit faster, use a bit less memory while compiling, result in smaller binaries, and produce more efficient code! 🎉

here is something that feels so powerful when behavior is baked into the reactivity, rather than compilers or framework. I've remade a few demos trying out the reactivity with manual DOM updates to test it out, starting with Ryan Florence's Select Example
playground.solidjs.com/anonymous/85...

my mind keep going into a distraction, the idea of how to create payment engine sometimes keeping me deep dive into many things that requires many requirement and fear

#rustlang hot take: We should rename .unwrap() to .or_panic(). (And .expect() to .or_panic_with().) "Unwrap" is a terrible name for the panicking function, especially since we also have things like .unwrap_or() and .unwrap_or_default() which never panic.

tired tired

i should write about this. react assumes you’re able to structure your teams by screen, not by technology. react works *either way* but it offers the product-divided teams an advantage. it lets each of them move independently of others, mostly without colliding or slow “over the wall” stalls.

what's up everyone its me rick