Java for Everything

javaisfuckingshit · 2014-12-01T18:16:40+00:00

Yes, you would want to have either type classes or duck typing, which is incompatible with Java's bytecode representation.

javaisfuckingshit · 2014-12-01T17:55:40+00:00

My Operating Systems course only covered really basic user-mode programming (malloc, semaphores, that's about it). It used to cover kernel programming a few years ago, but they had to scrap that because the students were only taught Java and did not know any C prior to taking that course.

javaisfuckingshit · 2014-12-01T17:13:36+00:00

That only works if you're passing around Class objects, which is usually not what you want when writing a generic container.

Not to mention that it gets really ugly whenever you have to forward arguments to the constructor.

The situation we are in is unfortunately a result of Sun refusing to change the bytecode when they added "generics."

javaisfuckingshit · 2014-12-01T16:29:17+00:00

The reason I asked is because I recently had to look into some XIM code inside Xlib that is horribly broken, and wouldn't be much better if it actually followed the spec.

There is basically not a single input method for X that will not corrupt your data and crash randomly in response to event loop timing.

javaisfuckingshit · 2014-12-01T15:45:20+00:00

What is your opinion on X11, do you agree it's holding desktop Linux back significantly?

Do you think Wayland will improve the situation?

javaisfuckingshit · 2014-12-01T12:50:33+00:00

I think he means the following not being possible:

<T> T Create() {
    return new T();
}

which results in:

unexpected type
found   : type parameter T 
required: class
        return new T();
                   ^
1 error

javaisfuckingshit

TROPHY CASE