Who fucking thought this was a good idea

Who fucking thought this was a good idea

Who sat down and said, "Java is a good idea"

Other urls found in this thread:

benchmarksgame.alioth.debian.org/u64q/compare.php?lang=java&lang2=gpp
oracle.com/technetwork/java/javase/overview/javahistory-index-198355.html
paulgraham.com/javacover.html
paulgraham.com/trevrejavcov.html
mindviewinc.com/Books/TIJ4/
twitter.com/SFWRedditGifs

>I failed "intro to programming" and now I'm going to vent my frustration to other college dropouts on Sup Forums - the thread

Compared to Visual Basic, it was an improvement.

>Get the garbage collector on this guy, because this is a trash opinion

System.gc()

I guess you're too retarded to remember the days where cross-platform compatibility was a big fucking deal, huh?

Oracle. They're the ones who got a team of amateurs to disassemble the original version of Java and figure out how it worked. As it turns out, no one could figure out how it works.

>too retarded to remember
This makes no sense, I didn't even know what programming was during those days. Am I a retarded for being younger than you? Are you then retarded for not remembering the Napoleonic Wars?

What do you mean they couldn't figure out how it worked

you must be 18 or older to post on Sup Forums

I'm 26, started coding at around 18. Besides C/C++ I never had huge portability issues with a language.

>retarded for not membering 'poleonic wars?
yesh

The JVM is very useful if you don't like java pick one of the many other languages or stop being a double nigger and learn C, Python, and Lisp

It was a good idea back in the 90s, it became even better with HotSpot.
Too bad it has been stagnating for the past 20 years.

Java is a good idea

it made sense in the 90s.

I mean, if you wanted to develop a desktop application your only options were vendor specific, like win32. Which is and was utter garbage.

Java ran on anything and was easy to use, what was not to love?

Of course, sometime later people realize that its inheritance model sucked big balls.

Java is a good idea if you need to hire an army of pajeets to shit out code until it works.
It's one of the safest languages I can think of.

The JVM is top notch. If you don't like Java, use another language like Kotlin, Scala or Clojure.

>g defending java
where is all this reasonableness coming from?

i ironically prefer it to C++ if i need to do OOP

C++ is crap at any OOP beyond encapsulation

Hello I've read "Head First Java" and a book by Barnes and by Liang but I actually haven't programmed even one real Programm.

How can I become a real programmer so I can move to Australia?

Memorize the entire API, write a rocket launch program, and then shill your portfolio

He's not providing his valuable opinion about Napoleonic wars, unlike you.

>implying C++ has encapsulation in the first place

STL does a decent job of it.

Is this about lack of multiple inheritance?

STL is implemented in C++, and since C++ does not actually provide encapsulation (although pretends it does), STL doesn't either.

It was intended for embedded systems programming and represented the idea of unlimited portability across any CPU/other hardware. He wanted something that required no changes in the program for it to run elsewhere, iirc

What's a good book for learning Java if I already know programming basics but not OOP basics?

>It was intended for embedded systems programming
Bullshit.

It was a trip but I learned Java from going through Minecraft decompiled source code (MCP) and making changes to that.

>I learned Java from going through Minecraft
Don't do that btw

This is some Poe's law shit.

It was like a logical puzzle. I love those.
In the end, Minecraft is not as badly written as many consider it to be.

apparently he did

the intent was to have code that could run on any platform that had a java virtual machine

idk if the implementation could have been better, or if "vm code" is naturally slow

Java is not that much slower than C++ and is faster than plenty other languages.

benchmarksgame.alioth.debian.org/u64q/compare.php?lang=java&lang2=gpp

And of course CPU is very often not the bottleneck in the first place.

> (You)
>>It was intended for embedded systems programming
>Bullshit.
oracle.com/technetwork/java/javase/overview/javahistory-index-198355.html

First use was even on an embedded system

It being originally for embedded development is a well accepted fact, just Google it

>>First use was even on an embedded system
>>It was intended for embedded systems programming
Those are not really the same are they?

Java itself is shit


Now if you actually had any experience with Java besides Intro to Programming you'd have used one of the enterprise frameworks such as Spring

The language is bad, the overall ecosystem is fucking amazing and extremely efficient if you're actually doing professional work

>"Java was developed by James Gosling at Sun Microsystems (now part of Oracle Corp.) and released in 1995. Gosling's original concept was the creation of a robust language that could be used to write portable embedded applications. Over the years, Java has found considerable success as a means of running a program (an "applet") in a browser. This enabled developers to run sophisticated applications, hosted on web pages, that would run on any browser on any platform."

Given that there are countless sources to support my view and none to support yours, it's easy to know who is right here

I'm still not convinced.

Don't know what else to say

It's okay. You can't win everything.

java is a language that accomplishes none of its design goals

java is supposed to be portable -- except every serious java application comes wrapped in custom scripts to correctly set up its environment and execute it for each target platform

java's memory model is supposed to relieve you from managing memory -- except every serious java system requires GC tweaking, custom allocators, allocation tweaking, and throws exceptions when you tweak it wrong

java's programming model is supposed to codify and simplify good system design -- except java is notorious for abstruse concepts and long symbol names

with other flawed languages like python, javascript etc. i can at least understand what positive features attract people to those languages. java, however, is an unfathomable pile of shit. it does nothing right

A man by the name of James Gosling.

It was the Go of its time
paulgraham.com/javacover.html (2001)

Be sure to not miss paulgraham.com/trevrejavcov.html

>except every serious java application comes wrapped in custom scripts to correctly set up its environment and execute it for each target platform
That means it /is/ portable, m8. Do you think you can port GTA V from Windows to Linux by writing the right initialization shell script?

>every serious java system requires GC tweaking, custom allocators, allocation tweaking
That means it /does/ relieve you from managing memory. Do you think you can fix memory leaks in C++ by adding -Xmx2048m when you run it?

Jesus christ

Java was literally about to destroy Microsoft because it could be run independent of OS type. Until they developed for Java and ruined their APIs

I was expecting some answers to this


So, serious question

To those of you disliking java, did you ever use it in an enterprise context


If you did, I'd be really interested in hearing what you used and why you think it's shit even in enterprise

because I'd rather kill myself than replace a functioning java system with some hipster nodejs bullshit

Inheritance is a bad idea in the first place. Shit is easier to test if you do dependency injection.
Aggregate rather than inherit.

>Inheritance is a bad idea in the first place. Shit is easier to test if you do dependency injection.

How are those two statements related

I think xe means "composition".

>"java does it differently, therefore java fixes it"
the fact that you think fucking bisecting to the correct heapsize parameter on a per-workload basis "fixes memory leaks" shows that you have truly chugged a ridiculous kool-aid. that's insanely burdensome and idiotic, irregardless of whether C++ memory management was also shit in the 90s

java is the only language on earth where i can download stable code, apply it to correctly formed input, it throws a GC exception, and i get told that's expected behavior, and that i'm supposed to double a parameter and repeat until it can finish running

java is a phantom tollbooth language where every solution creates new problems to solve and therefore endless work, like milo moving a pile of sand back and forth, one grain at a time, with tweezers. there are entire systems -- caches, databases, and serialization pipelines -- whose only performance benefit comes from storing java-specific object representations that needn't otherwise exist. enterprise doesn't love java because it solves problems; enterprise loves java because it creates problems for enterprise to continue solving, endlessly

>enterprise doesn't love java because it solves problems; enterprise loves java because it creates problems for enterprise to continue solving


I know you think that that's a super deep and witty statement to just randomly throw out, but purely from a logical perspective that does not seem very likely considering capitalism and businesses being jews

Hill-climbing algos are Jews, but not very good Jews.

How do I convince the company I work at to switch to Kotlin

Ask them to trial it on a tiny project. How the project to people who matter and explain the benefits.

That doesn't even run the garbage collector, it just suggests that the jvm "should" run it.

*Thinking in Java* by Bruce Eckel. Previous editions are available for free.

mindviewinc.com/Books/TIJ4/

Java came from a forgone time in computing. Computers were not fast enough to run scripts at an effective speed. Java was the cross compatible solution that ran faster than a script. It worked. But as computers became more powerful scripting started to become good enough speed wise. If you don't care about speed why even bother with Java. If you do care about speed use c/c++. However, Java was taught heavily in schools because schools thought it would be the future. It was not. Java was great at solving a problem that does not exist anymore.

This nigga is in every thread talking about Poe's Law.

Java is still the next fastest thing to C++ or C, and requires a lot less hassle to program. I'm a huge C++ defender, but even I have to admit that my Java productivity eclipses my C++ productivity by a factor of at least 3. Not to mention that debugging C++ is a nightmare. Debugging Java code is easier than writing actually good C++ code. Use C++ if you have no time constraints. Use Java if you need a solid program in a short timeframe that's only 80% as fast.

Java can actually be faster than C / C++ in certain circumstances (i.e. CPU intensive work that doesn't do too much stuff on the heap)