I have the same problem as I had with modules when they were introduced, I don't use the cli to compile my java application but gradle/maven. Nowhere are we shown how to compile with module awareness and especially a mixed language mixed env like kotlin/java this stuff just gets very tricky. Or used to be, I have no idea since my bad initial experience around those made me to juts not use modules at all (and I've been happy since).
I work on java since JDK 8, worked for more than 4 different companies I think, many projects. Never saw any of then using modules, or even talking about modularizing the project, not even greenfield projects. Its 2023 and I still search for reasons to use module system and the maturity of the ecosystem around it. It needs a rethinking, looks like community don't care about it, brings more warn than good which is sad because the problems it original tracks are real ones.
Personally for me I find most of the new features in Java (Java 11 and onwards) to be completely useless for real life projects. All these features are flashy i.e. when you look at them it feels quite cool but they are not practical and would make a codebase difficult to understand if used extensively. Just my opinion.
I saw the hair.
I saw the Java logo behind Nicolai.
I saw the hair again.
I can't unsee it now.
Omg, now I can't unsee it either! 😮
🤣
I have the same problem as I had with modules when they were introduced, I don't use the cli to compile my java application but gradle/maven. Nowhere are we shown how to compile with module awareness and especially a mixed language mixed env like kotlin/java this stuff just gets very tricky. Or used to be, I have no idea since my bad initial experience around those made me to juts not use modules at all (and I've been happy since).
Thanks for the in depth coverage.
My first bad experience with modules was with split packages.
Awesome information, thank you for the in-depth information allowing me to make great decisions on my project.
Read your book "The Java module System". Thanks for the content 💪
I work on java since JDK 8, worked for more than 4 different companies I think, many projects. Never saw any of then using modules, or even talking about modularizing the project, not even greenfield projects. Its 2023 and I still search for reasons to use module system and the maturity of the ecosystem around it. It needs a rethinking, looks like community don't care about it, brings more warn than good which is sad because the problems it original tracks are real ones.
Personally for me I find most of the new features in Java (Java 11 and onwards) to be completely useless for real life projects. All these features are flashy i.e. when you look at them it feels quite cool but they are not practical and would make a codebase difficult to understand if used extensively. Just my opinion.
@@Adi-yi6qq records are useful, pattern matching
ground truth is, that most modern java projects do not make use of jpms. and it makes it hard when your own projects rely on modules.
Good practical advice on an otherwise dull subject.
Well on the screen everyting is fine and run...
Hello! Thanks, i have your book :)
Theory even practical without showing is much less efficient, at Oracle it should be clear. Still, thanks for sharing.
tbh I easier understand java projects without modules rather than with modules.
Thanks
TIL Java Modules in Real Life are a PITA
Who’s still using modules in 2023?
Modules havent been deprecated, so what do you mean by 'still using' ?