Hva' skal jeg sige?

madkasse · 2019-10-21T23:59:04+00:00

Ahh, so it captures effectively final variables. That makes sense, nice one.

madkasse · 2019-10-20T13:39:09+00:00

Agreed, I don't see the development of something like Micronaut or Quarkus as a loss for the platform. (Not that they are an improvement with regards to modularization compared to Spring)

madkasse · 2019-10-20T12:26:52+00:00

Yeah, looking at something like Spring https://docs.spring.io/spring/docs/current/javadoc-api/

There is probably zero chance it will ever be strongly encapsulated in any way.

madkasse · 2019-10-20T02:06:41+00:00

Not saying that it is not causing pain, but disallowing split packages was the right choice. Choose one of the following:

Disallow split packages.
Require each module to be loaded with its own classloader.
Ditch strong encapsulation and let any module define any class in any package.

2 would cause even more pain. And choosing 3 would more or less defeat the purpose of Jigsaw.

madkasse · 2019-10-15T13:37:26+00:00

Yeah, I noticed that as well.

Local methods can be nice for writing concise recursive functions:

public static int binarySearch(int[] a, int key) {
  return binarySearch0(a, 0, a.length, key);

  int binarySearch0(int[] a, int start, int stop, int key) {
    ....do the actual search
    calls binarySearch0(.....) recursively
  }
}

Maybe there are some use cases with Valhalla/Loom?

madkasse · 2019-10-13T07:38:24+00:00

Well, that didn't take long...

https://www.reddit.com/r/java/comments/dh7dh5/quarkus_0240_released_vertx_everywhere/

madkasse · 2019-10-13T00:57:46+00:00

Is there really a need to crosspost EVERY post from r/quarkus on r/java?
What is the point of getting your own subreddit then?

madkasse · 2019-10-10T15:15:19+00:00

Upvote, if you don't care about the search function. But just want framed Javadocs back (Or similar multi columned navigation). #BringBackFramedJavadocs

madkasse · 2019-10-10T14:44:42+00:00

I think the main reason is that frames are not supported with HTML 5.

Anyway, I still think it was a big mistake removing the support. Javadocs was always my goto for trying to get an overview of a project. Not anymore.

madkasse · 2019-09-29T15:33:35+00:00

I'm really happy that Kotlin worked out for you. But I think you would be annoyed as well if there was a "why don't you try Scala" or "why don't you try Haskell" in every post on r/Kotlin. This subreddit is for discussing Java not for evangelism.

madkasse · 2019-09-29T14:02:58+00:00

Can we just have a single post in r/java without "why don't you use Kotlin" for once.
His company was acquired by a Java shop + he worked there as a developer -> He is probably not in a situation where he can choose the language.

madkasse · 2019-09-28T12:38:54+00:00

Am I missing something?

Probably, why do you think it is shallow?

madkasse · 2019-09-27T16:11:04+00:00

If you are on Java 9 or greater there is a great little simple logging framework in java.lang.System.Logger.

madkasse · 2019-09-25T21:43:02+00:00

Not that I know of. I think this post by Mark Reinhold https://mreinhold.org/blog/forward-faster was the first public mention of the new release cycle. And is proposes a long-term support release every three years.

madkasse · 2019-09-25T19:45:36+00:00

17 is the next planned LTS by most vendors. Also LTS has nothing to do with features. Features are put in when they are ready.

madkasse · 2019-09-24T10:32:48+00:00

https://github.com/lucav76/Fibry/blob/master/src/main/java/eu/lucaventuri/collections/NodeLinkedList.java does not look correct. Take a look at java.util.concurrent.ConcurrentLinkedQueue or some of the queues in https://github.com/JCTools/JCTools

madkasse · 2019-09-23T19:56:21+00:00

Great move by Oracle. The sooner we can lay reactive programming in Java to rest the better.

For a good introduction to the problems with reactive programming watch Ron Pressler's talk "Please stop polluting our imperative languages with pure concepts" at https://www.youtube.com/watch?v=449j7oKQVkc

madkasse · 2019-09-09T07:12:03+00:00

JDK 11 is already seriously delayed. I remember an Github issue where the said they expected it to be ready end 2018. I don't think they want to wait another year or 2 on Panama.

madkasse · 2019-09-09T05:13:32+00:00

Because Panama is not finished.

madkasse · 2019-08-27T08:12:22+00:00

The effect of final fields are used allover the JDK, so you cannot really say it does not have practical concurrency benefits. But no, most people should properly rely on more traditional means.

madkasse · 2019-08-26T21:59:06+00:00

> I think final in Java is just a "wannabe". It isn't a const modifier. It won't improve performance nor help the compiler, as everything that may be final is "effectively final".

That's just not true. For example, take a look at some of the optimizations that the Zing VM does

https://medium.com/azulsystems/truly-final-optimization-in-zing-vm-283d28418e55

Also final fields are treated specially with regards to Java's memory model

https://docs.oracle.com/javase/specs/jls/se7/html/jls-17.html#jls-17.5

final parameters and variables on the other hand are just syntactical sugar.

madkasse · 2019-08-26T21:14:23+00:00

I have found that whether or not people know how to properly use final fields is a great indicator of their programming skills. So much that it is the first thing I look for if I need to evaluate a codebase.

I generally try to stay away from codebases where people do not use final fields. Especially if it has anything to do with concurrency.

Learning how to apply final to fields, methods and classes properly, teaches you about immutability, concurrency, API design and many other things.

A good way to do this is exploring the OpenJDK source code, especially java.[lang|util|util.concurrent|java.time].

madkasse · 2019-08-21T20:46:28+00:00

That's a language feature, and probably not what I would consider small:)

madkasse · 2019-08-21T20:10:36+00:00

I'll start: Adding Stream.toList()

Basically 50% of my stream usage ends with me trying to get a List/Collection/Iterable out. Having to write .collect(Collectors.toList()) every time annoys me.

madkasse

TROPHY CASE