From 21a3c564b0e1a3e49fdf2b21abf039dc0a3e0d95 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 15 Mar 2023 01:32:29 +0200 Subject: Update content for html --- gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.html') diff --git a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.html b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.html index 668c8447..7e89d305 100644 --- a/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.html +++ b/gemfeed/2022-12-24-ultrarelearning-java-my-takeaways.html @@ -74,7 +74,7 @@ https://projectlombok.org/

Java needs a clean cut. The clean cut shall be incompatible with previous versions of Java and only promote modern best practices without all the legacy burden carried around. The same can be said for other languages, e.g. Perl, but in Perl, they already attack the problem with the use of flags which change the behaviour of the language to more modern standards. Or do it like Python, where they had a hard (incompatible) cut from version 2 to version 3. It will be painful, for sure. But that would be the only way I would enjoy using that language as one of my primary languages to code new stuff regularly. Currently, my Java will stay limited to very few projects and the more minor things already mentioned in this post.

Am I a Java expert now? No, by far not. But I am better now than before :-).

-

E-Mail your comments to hi@paul.cyou :-)

+E-Mail your comments to hi@paul.cyou :-)
More entries