Check out my latest concurrency themed blog entry about Loom & Fibers! Attempting to visualize execution, Kernel Threads VS Fibers. #loom#fibers#OpenJDK https://t.co/SH4nldCBoB
After three years we are organizing the first in-person event with a special but well-known guest @heinzkabutz
Join us and 'Prepare for what "Loom"s ahead'
Pizzas and beers are included :P thanks to our kind sponsor Advantage FS
See you all there!
https://t.co/DBi7IUpq09
We will be doing our first @skg_jug meetup of the year today! Dimitris Kontokostas will be introducing us to Apache Kafka.
Join us! https://t.co/odiFM99Rxv
There is no trade-off of quality vs. speed in software. There never has been. Low quality means low speed. Always.
The only way to go fast is to go well.
Check out my latest concurrency themed blog entry about Loom & Fibers! Attempting to visualize execution, Kernel Threads VS Fibers. #loom#fibers#OpenJDK https://t.co/SH4nldCBoB
@pressron A common feedback I got and you also point it out is that it is not actually showing a workload that would benefit from the handling of blocks in fibers. I have been pondering if I could apply my original idea to show something on that. I will think on your suggestion with locks.
One of the coolest things about #jcrete is it has an environment that helps people feel comfortable and empowered to be part of this, share knowledge and experiences and contribute to the best of their ability.
You will also find below a session I have convened! 🙂 @JCreteUnconf
@edefazio I am not sure whether a Fiber implementation would help in these workloads/applications. You need high numbers of blocking threads for the new model to help which I believe these applications do not have.
Never ask permission to refactor. Never ask permission to write tests. You do these things because you KNOW they are the best way to go fast.
When you ask permission, you are asking someone else to take responsibility for your actions.
JVM pro-tip: stop catching OutOfMemoryError. Like seriously. Wtf are you doing. Once the JVM goes OOM, you cannot sanely recover. If you write a library that catches and swallows OOM, double-shame on you.
All over the place, I see:
if (someValue != null) { someValue.someAction(); }
being replaced with:
if (someValue.isPresent()) { someValue.get().someAction();}
This is what happens when new tools get adopted but not the new paradigm that comes with it. 🤷♂️
Don't miss our next meetup this Monday, dedicated to Cloud technologies like @kubernetesio and @QuarkusIO and kindly hosted by @okthess
- Special thanks a lot to our sponsor @PRODYNASE
- Guest Speakers : @geoand86
and @El_Papachristos
- RSVP https://t.co/ht6HtJa5m4