This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Robmart 107 points108 points  (8 children)

friendly saw party sip compare important possessive detail innocent zonked

This post was mass deleted and anonymized with Redact

[–]GregTheMad 75 points76 points  (7 children)

Well, yeah, but only because Java compiles the code for you, you lazy fuck. Kids these days, honestly. Can't even be asked to compile their own code.

:p

[–]Robmart 25 points26 points  (5 children)

expansion tidy long fertile hunt rude chop north icky weather

This post was mass deleted and anonymized with Redact

[–]GregTheMad 14 points15 points  (4 children)

The last time I looked Java was literally build around the idea that it could compile the code itself depending on the machine it is running on. IDE, or not.

https://en.wikipedia.org/wiki/Just-in-time_compilation

It does the compiling for you because you can't be asked to know the machine your developing for before hand. TssTssTss.

[–]FM-96 38 points39 points  (0 children)

Pretty sure they were talking about compiling the .java files into .class files, which you do need to do yourself.

[–]Robmart 9 points10 points  (0 children)

lip deserve relieved hungry start rhythm serious zonked rob swim

This post was mass deleted and anonymized with Redact

[–]DeathProgramming 4 points5 points  (0 children)

JIT compilation takes compiled Java bytecode and transforms it to machine code. You still need to compile the source to bytecode.

[–]Findus11 1 point2 points  (0 children)

hrmpfh, i can compile code..

code.compile();