Thanks Brian! I just used Virtual threads with Structured Concurrency along with Semaphores for rate limiting. Wow, was it ever easy with so little code.
With respect... it is risky to give yourself the luxury of sweeping everything under the "change is scary" rug. Yes, some portion of people's resistance to change is irrational, but if you let yourself label it all as irrational, you miss a lot of legitimate concerns. I'm not saying this is what happened in the case of Java, which was a roaring success. It's just that it's unwise to paint all objections with a simplistic "change is scary" brush.
And you dont think that they listen is that your message? Of course a talk is never going to go over every minute detail and discussions that are ongoing in the community or inside oracle and amongst the openjdk developers. If you have some particular objections just state it without this well-actualism talk here, then it can be properly discussed if needed.
@@prdoyle you say it is risky in general but you havent proposed any reasons or real examples of concerns for why that is the case here. It is perfectly legitimate for Brian not to go through and debunk every concern that was raised when all of these changes were implemented since this is a summary style of talk, not an academic article.
Thanks Brian! I just used Virtual threads with Structured Concurrency along with Semaphores for rate limiting. Wow, was it ever easy with so little code.
Great Talk!
great as always
16:50
With respect... it is risky to give yourself the luxury of sweeping everything under the "change is scary" rug. Yes, some portion of people's resistance to change is irrational, but if you let yourself label it all as irrational, you miss a lot of legitimate concerns. I'm not saying this is what happened in the case of Java, which was a roaring success. It's just that it's unwise to paint all objections with a simplistic "change is scary" brush.
And you dont think that they listen is that your message? Of course a talk is never going to go over every minute detail and discussions that are ongoing in the community or inside oracle and amongst the openjdk developers. If you have some particular objections just state it without this well-actualism talk here, then it can be properly discussed if needed.
@@Mig440 I meant what I said. It is risky to give yourself the luxury of sweeping everything under the "change is scary" rug.
@@prdoyle you say it is risky in general but you havent proposed any reasons or real examples of concerns for why that is the case here. It is perfectly legitimate for Brian not to go through and debunk every concern that was raised when all of these changes were implemented since this is a summary style of talk, not an academic article.
@@Mig440 I don't think we're disagreeing here?
crazy how all of this doesn't even come close to how better concurrency is in Go.