Drixtanam I wasting my time with spring webflux? it seems like the official documentation isn't really "on par" with the mvc one; I feel like I am fighting against the grain
dreamrealDrixtan: not really a question we can answer, but... in my experience if you're on java 21 or later you don't need webflux at all
dreamrealYou *could*, but if you're one of the people who DOES need it, you're not asking anyone else if you need it or not, you know it
dreamrealif you're the other 99%+, you're turning on virtual threads and using blocking APIs and getting the benefits that webflux would give you with a MUUUUUCH simpler api
Drixtandreamreal: yeah, with loom, I was wondering if webflux was a dead baby... it's for a pet project, so it's more like a "refreshing my java skills" and "learning" kind of stuff right now. Thx for your input.
dreamrealI don't think it's "dead" but it's really of limited application
dreamrealfor the people who need that extra 2-3% speed advantage over virtual threads, or for those for whom virtual threads are an ecosystem burden due to ... very constrained stack space, etc., I guess, it's still the way to go, but ... the number of projects for which those apply is really quite low
deebo21 still had the problem with thread pinning? or was that the version it was fixed in