Many times during my talks covering Java records I was asked if the result of
hashCode() of a record is cached. Let’s see ;-)
It seems “everyone knows” that “with records you don’t have to write
hashCode()”. What if I told you this might not be always true…?
After using Linux for quite a few years now, I’ve accidentally embarrassed myself. I spend a lot of time using terminal in various forms. I’m not sure I know all Vim quirks (not to mention Emacs, but let’s not talk about this operating system now), therefore I was pretty confident I know how to use the terminal emulator… Today I’ve found a nice new feature, really low-hanging-fruit, so I’ve decided to share it with you, along with some other goodies (maybe not some obvious to Linux neophytes) I’m being asked about after my talks.
This post should have a nicer title, but I can’t find it. It’s about security factors and some misperception about them.
I had a great pleasure to take part in the JAVIPS online 2020.
In one of my previous posts I was torturing Java™ Records using Lombok. After receiving some really encouraging comments (‘what a sick idea you have, respect!'), delivering a deep-dive talk "Java 15. What’s new and noteworthy", and some discussions on JVM Poland Slack channel, I’ve decided to keep torturing. Sorry ;-)
shebang in a way which makes it portable?
Some people find it shocking, that it’s possible these days to write a script (which will run in CLI) not only in Bash, Perl, Python or PHP, but also in Java.
The competition is over, the prizes are given away… And despite the trainings still going on, it might be time to show the answer to my little riddle, and make a comment on it.
When explaining Java records online I was asked several times ‘right, what about Lombok?’ In particular this question was ‘if the records are immutable, how are they different from Lombok’s