If you want to bind the same java method to two HTTP URL patterns you might want to annotate it twice. Just as an example - I don't even know if it would work 😁 So basically it often makes sense, if the annotation has fields. The exact same annotation twice (as in the video) is indeed questionable.

I wanted to annotate a class with multiple references to a spec: @SpecReference(document = Documents.JAVA_ROCKS,chapter = "13") @SpecReference(document = Documents.DUKES_ADVENTURES,chapter = "42") This is how the idea for this short was born.

@@bienadam got it. Thank you

Annotations were introduced with Java 5 / 1.5: docs.oracle.com/javase/1.5.0/docs/api/java/lang/annotation/Documented.html ...in 2004. Thank you for watching!

Old? You confused the podcasts :-) Thrustmaster! Exactly! It was decades before I was born, my grandmother told me stories about it... :-)

Attend airhacks.tv (Q&A livestream) and ask questions: kzfaq.infolive Also: join: discord.gg/airhacks and ask questions.

+1 It is indeed an exception from the rule in my project. Thanks for watching and commenting!

It's a bit of "this is what I am used to doing." Using var does remind us that the type of a variable is determined on the right side of the declaration, not by the type that we declare on the left, which can be a superclass or interface.

Full disclosure, I was born in 1951, so I am pretty much the definition of a Boomer.

Do you have another example, where non-var is better than var?

@@slartidaneverywhere you store the result of a function

I also prefer to *always* use the actual type instead of var, because it makes it easy and clear to see what you're dealing with. If you look at the code at a later point in time you sometimes have no idea what kind of class you're dealing with and what options/methods you have available with it. If you see the Type you immidiately know how the thing works.

Line after it added "hello" after "world", and next line after it added "duke" before "world". So "world" wasn't first or last element in collection.

He didn't print all the elements of the array, only first and last.

The built-in Java HttpClient is a good place to start. I would only use 3rd party libraries for very specific use cases. "No dependencies, no problems. " Thank you for watching!

What isn't educational about learning how Instant works? Using Calendar was a pain.

@@MarkJaeger Apologies for the confusion but I'm just commenting here in general not specifically to this video. Just a video associated with his playlist. The "meet and greet" videos are what I would call non-educational and I'd prefer those were separated from this playlist.

Map.of has just eleven overloaded methods. You just enter key/value pairs. With Masp.ofEntries, you have to instantiate entries.

OK, but complexity is not a desirable design

@@MarkJaeger its not about "complex design" is about complex branching. In a real program, when dealing with loops, usually there are several branches inside a loop. Either normal ifs, switches, vtables, etc. This branching complexity might considerably reduce the prediction of branches, therefore using these operations will notably reduce performance. STILL this is bullcrap in a real application, only relevant for extremely hot code. This seems fine overall. I just program real time applications and I know I wouldn't use these for hot code.

@@tharteon1866 your branching within loops sounds like a direct violation of the Single Responsibility Principle. Hence my reference to design issues.

@@MarkJaeger Don't be mistaken, dynamic dispatch is also a type of branch. What you call single responsibility is basically an application of OOP inheritance or interfacing. When dealing with multiple implementations of a method, then we are also dealing with dynamic dispatch, which is a type of branching, which will lead to failed branch predictions anyways.

I suggest the following: write simple and clear code, measure performance, improve if necessary. Is this a good strategy? Good discussion by the way. Thanks for watching and commenting!

ARM seems also to do well. I recorded this video on an “Apple Sillicon” (ARM). Thanks for watching!

Actually in my case difference is random and sometimes is equal to 100 ms on x86 CPU

…now we have to patch the JDK… Seriously: I recorded this short with the weakest “strength” (docs.oracle.com/javase/8/docs/api/java/text/Collator.html#setStrength-int-). A test with the other strengths (e.g. SECONDARY) is failing. Thanks for watching!

Thank you!

+1 If you cannot always rely on IDE - then you have to be more careful with the “var”. I’m using VSC all the time.

It’s interesting, right? Thanks for watching!

+1 you are right, but I would prefer to declare a variable without the "var" in this case. Thanks for watching!

Thank you for watching and commenting!

@@booyesum1730 if you learn German, that just take in mind, Strasse is simply wrong!

@@walterwatz-vy2re Ich weiß 🙂

Thank you for watching. Recording Java shorts is fun :-)

Thank you for watching!

The best for file handling :-) Thanks for watching!