java without sucking? Myth or Magic?

/prog/ I am learning java at university, and there seems to be a religiously followed doctrine that OOP is brilliant and that all problems should be put into an OOP system.

to summarise my grimaces:
-terrible ontology for classes
-everything must become an object and have a class and factory (i.e. overzealous use of OOP)
-everything relies on try catch throw statements to fix the 10's of problems that just inventing an object creates
-nothing beautiful, nothing simple, and definitely nothing fast to write, compile or execute.

Now for questions.
1. is it possible to make elegant, good, maintainable code in Java?

2. Challenge mode, is it possible for that code to work with everyone elses' OOP bullshit?

For instance could one simplify programs down to a single class, then for the required OOP methods and classes just call to the arrays etc in that class?
i.e. make the package/program behave as expected for any other class/driver using it, but not use OOP for the code.

3. Will the introduction of lambda expressions in java SE 8 make life better?

4. Should I quit this course before the cancer grows on me and I have to work to scrub it from my mind?

>>1 definitely nothing fast to execute.

lol learn how to program you dumb faggot

>>11 if I were a project manager I probably would use other languages over it (something that weeds the average programmers out)

Brave new world, if you ever become one (unlikely) you will probably be fired after a few months for hiring a bunch of  sperglords to write "a better language" with its own compiler and syntax that turns out to be unmaintainable garbage because you don't have any people skills (evidence: only I understand OOP! Java is terrible even though everyone uses it including google and amazon which are mostly chock-full of proven geniuses!)

>>13 broke plagiarism rules

lol

>>21 lmao

>>19>>20 samefag