Видео

Do you want to know about how garbage collection works in Java in general, or specifically how it would pertain to something like a template expression?

Thanks!

Threading issues and deadlocks can be some really interesting bugs to solve, which is why those thread dumps can be really useful!

Good catch - its supposed to be (101 + 102 + ...). I must have had the number "1000" in my head. Thanks for noting that!

A checked exception doesn’t necessarily mean an error can be detected at compile time or not (otherwise the compiler would just flag it right away). It just means that you have to provide explicit error handling code. Both checked and unchecked exceptions represent errors that can occur at runtime. The merits of checked exceptions are debatable, but among other checked exceptions, this one makes sense to me because there is reasonable likelihood of code hitting a case like this and you should have specific handling code available for it. Hopefully that helps clarify it a bit!

@@willtollefson thank you

You can use another while loop to do that. For example if you want to keep the number range the same each time but select a different random number for each iteration, you could add a while loop around line 12.

Thanks so much!

You're welcome!

Glad to hear it!

Thank you!

Thanks for the comment and suggestion! Admittedly I sometimes do my filming late at night because there often aren’t enough hours in the day. I’ll do my best to get better at this 🙂

Sometimes adopting new ways of doing things takes time. In this situation they aren’t adding the feature in its current state to the language and will probably preview an updated version in a later JDK. Hopefully you can reason with the other folks at your company one way or the other. I’ve often found logical reasoning works well for programmers that program computer logic everyday 🙂

@@willtollefson Thanks but sometimes you find yourself in a place where stubbornness prevails over rationality and logical reasoning. But it good these days we have people like you who help others to stay up to date with their videos and other content

Glad to hear you liked it! Debuggers can be very useful for sure

That depends. Do you want to see Spring tutorials? 🙂

@@willtollefson of course !!! There are no good ones online. You explain the best both for new programmers and more advanced.

I'll be sure to get to this when I can! I've been taking a short break recently while I have a very little one at home, but I hope to get back into a more regular posting schedule in the future!

@@willtollefson thanks a bunch

Yeah, it was a good concept, but unfortunately had some design flaws that they are working out now. Hopefully it will have a come back in another preview coming up

Greetings! Thanks for the comment 🙂

If I’m understanding your question correctly, you would need to setup a public IP address with this method that is reachable to other networks and as long as you had network connectivity and the same socket protocol, you should generally be able to communicate.

Awesome, glad to hear it!

@@willtollefson Hey, I strongly agree with Mat. I don't write comments either, but finally now I understand lamdas... It's strange that you have so few viewers with such a great content. Thanks a lot!

That’s great! Maybe over time I’ll get more views, but I’m not in any rush. I’m glad to hear that the content is helpful!

Thanks! When I see my dentist in a few months I'll be sure to thank him :)

Thanks!

Since its an object reference, the local variable value (e.g. the reference value) is cached, but the object data itself remains on the heap, so as long as you don't change the object reference, you'll still reference the same heap data across all of the threads. This is why its preferred to mark the object reference as immutable because that helps give you guarantees about the concurrent protection of the value. It doesn't, however, guarantee concurrent modification protection of the underlying object, which is why we're using AtomicInteger.

@@willtollefson thanks, I'm surprised because if I understand correctly then objects are always read from the heap and the cost is significantly higher.

Great point. The JLS (to my knowledge) doesn’t specify any sort of read optimizations in this type of situation. Something like that could probably be implemented per JVM if it can detect situations where a more efficient read can happen on an object reference (and I’m sure it does)

Thanks for the comment! Here are some videos I've done on those topics: Volatile and atomic: ruclips.net/video/31s_DzrkqZc/видео.html Synchronized: ruclips.net/video/FpNRXz696ZY/видео.html I've also done a few videos talking about runnables in general, virtual threads, and structured concurrency. If those don't scratch the itch, let me know and I can do a video on a specific threading topic.

​@@willtollefson Great videos.

Thanks!

Thank you!

Thanks! It’s definitely something I try to follow almost every day

That lock video is on my short list right now of future videos to make. There are multiple flavors of locks - if there's a particular thing you want me to cover in that video, let me know!

You’re welcome, thanks for the comment!

Glad you enjoyed it!

Personal preference I suppose 🙂 I know folks who use it every chance they get and others that wish it was never added to the language. What are your thoughts on it? I agree with a lot of what is stated here: openjdk.org/projects/amber/guides/lvti-style-guide

Thanks for the comment! When I run 1M tasks on my machine with the Java version, I'm getting 10-11 seconds. When I run similar Go code on my machine I'm getting around 5 seconds. Without deep diving the compiled byte code and go binary to really figure out the performance difference, I have a few upfront guesses: 1. Java warm up could be playing a small role here due to lazy initialization for things like the classloader and virtual threads mapping to platform threads 2. Java and Go have different default behavior for the number of routines that can be executed in parallel and the number of OS threads available to the runtime for scheduling. 3. Goroutines are optimized to have a small stack size at the beginning of execution and then expand as needed. I'm wondering if stack allocation for Java virtual threads is more expensive in this case. Both are still MUCH better in this example than the previous Java thread model though :)

Sleeping for 1 second is probably not a very realistic example and goroutine smaller starting stack may explain the difference

Sure! I'll need to do a refresher myself on some of the lower level specifics, but I think this is a great idea

Thanks for the comment! Yes I can do a video on that. I haven't hit on that subject yet

You bet! It’s a difficult balance to maintain for sure

Good point - I probably should have mentioned that :) Per what I’ve seen from Brian Goetz they are reworking it and as of now planning some API changes that will make it into future versions. There are pros and cons to trying out preview features and this is why they call them previews. Glad we’re making the changes now though rather than having them in the main language

Thanks! 👍

Thanks!