Some reasons why JAVA rules and your language sucks.
1. Beauty. No legacy underscores. Nuf sed.
2. Java has long, clear, unabbreviated names.
3. With Java, IDEs come standard so that you don't have to type those long names. Phew!
4. Sooo many vendors support Java, except Microsoft. Microsoft supports IronPython, which doesn't help my pro Java arguments, so ssh ssh.
5. Java runs Python and many other languages including Java! Ok, it's not fair comparing a VM to a language, but i couldn't resist.
6. Java has a well funded community, whereas Pythonistas have to be naturally enthusiastic.
7. Java is strongly typed, so we don't have to write unit tests, and can rely on blind luck more.
8. It takes longer in Java, which helps a lot when you're getting paid by the hour. "Wa wa we waa!"
9. Java rules the Enterprise, if you exclude that SAP thingy.
10. Java rules the Web, if you exclude those ASP and LAMP thingies - and Python is only one of three P's in LAMP, so...
11. Java rules the Desktop, if you exclude C/C++, Objective-C, and all the stuff from the desktop monopoly.
12. Java rules the Mobile, period... for now.
13. Java is no good at system tasks, so it gives us a good cop-out for avoiding those.
14. Java never gets compared to, or confused with, Perl.
15. Java has an enterprise version. Quite a few actually.
16. Java has more opensource projects, more toolkits, more IDEs, more jobs, more verbosity, more everything!
I'M THE SUSSMAN
SON OF A BITCH ABELSON
ABELSON IS PIG
DO YOU WANT PYTHON?
DO YOU WANT FORCED INDENTATION OF THE CODE?
ABELSON IS PIG DISGUSTING
GUIDO VAN ROSSUM IS A MURDERER
FUCKING ABELSON
Name:
Anonymous2007-11-10 18:58
Some reasons why COMMON LISP rules and your language sucks.
1. Beaty. No legacy underscores. Nuf sed.
2. CL has long, clear, unabbreviated names.
3. With CL, IDEs come standard so that you don't have to type those long names. Phew!
4. Sooo many vendors support CL, except Microsoft. Microsoft supports IronPython, which doesn't help my pro CL arguments, so ssh ssh.
&c.
Some reasons why Tcl rules and your language sucks:
1. Beauty due to homoiconicity.
2. Simplicity due to having only one operation and an expr language.
3. Robustness due to being easily sandboxed from Tcl itself or C.
4. Fastness due to finishing your work sooner than you would if you were writing C or assembly.
Name:
Anonymous2007-11-12 23:19
>>10
Assembly is not beautiful. Look at any decent-sized listing of assembly code. No beauty. It's like looking at a cervix from the inside.
Assembly is not simple.
Assembly is not robust. In C you can shoot yourself in the foot. In assembly you have to invent your own gun and foot, and bullets, and notions of velocity, and will probably shoot them clear off and everything else around you a million times before you get it right. Anything that supports self-modifying code is inherently non-robust.
Assembly is fast. I'll give you that.
But the above reasons is exactly why I like assembly.
>>12 Anything that supports self-modifying code is inherently non-robust.
Lol wut? Me and my space toad disagree.
Name:
Anonymous2007-11-13 0:54
>>10
you only like assembly because it give you skills (fuck off C fags) capable of breaking/hacking/exploiting every software in existance, admit it, l33th@x0r
>>12 It's like looking at a cervix from the inside.
*fap fap fap*
Anything that supports self-modifying code is inherently non-robust.
You are not suave.
Name:
Anonymous2007-11-13 23:08
;=========================================
; Basic program to change graphics modes
;=========================================
mov ah,00 ;subfunction 0
mov al,18 ;select mode 18 (or 12h if prefer)
int 10h ;call graphics interrupt
;==== Graphics code here ====
mov ah,00 ;again subfunc 0
mov al,03 ;text mode 3
int 10h ;call int
mov ah,04ch
mov al,00 ;end program normally
int 21h
NO BEAUTY
VERY CERVICAL
NOT ROBUST
BUT FAST
Name:
Anonymous2007-11-13 23:28
>>19
You're only saying that because YOU CANT HANDLE THE CODE.
Assembly is like drugs, by itself it looks like patches or plants, nothing special. Once you use it, you feel like a EXPERT HACKER, and then end up shit once the effects gone and you discovered you forgot a dword_ptr.
>>19
oh hi, i optimized ur code. mov ax 18 | int h10
; ==== Graphics code here ===
mov ax 3 | int h10 | mov ax h4c00 | int h21
p.s. toilet-paper code went out of style years ago in the elite Asm communities.
>>29
Byte is generally understood as 8 bits, though I recommend avoiding it formally and using "octet" instead.
Name:
Anonymous2007-11-16 5:10
There used to be popular machines back in the 60s that had bytes of other widths. But on all modern computers, a byte is 8 bits.
Name:
Anonymous2007-11-16 6:46
C#/.Net. Thread over.
Name:
Anonymous2007-11-16 9:13
My other byte is 12 bits.
Name:
Anonymous2007-11-16 9:21
When I use an editor, I don't want eight extra KILOBYTES of worthless
help screens and cursor positioning code! I just want an EDitor!!
Not a "viitor". Not a "emacsitor". Those aren't even WORDS!!!!
ED! ED! ED IS THE STANDARD!!!
Name:
Anonymous2007-11-16 9:43
Java sucks.
Thread over.
Name:
Anonymous2007-11-16 15:12
>>30
shit forgot, fucking Java, havent touched that shit since 1.1 release
char is apparantly 16 bit signed
byte is signed still, no?
Name:
Anonymous2007-11-16 15:39
>>1 7. Java is strongly typed
Fuck yeah. I remember working on this huge Java project with a bunch of incompetent enterprise monkeys. Their Java code still sucked major ass, but at least they were forced to implement the right interfaces.
To imagine, these people writing Python or Perl code... shudder.