why did javascript beat java?

both were put into the browser. java was way faster, had a consistent implementation, better graphics, and a real class system.

http://en.wikipedia.org/wiki/Installed_base

Kebabs made of the flesh of POLECATS!

why not just use fastcgi?

Starting the JVM took too much time and didn't actually manipulate the page on the client. Now that I think about it, could the Java applets manipulate the web page document object model?

>>4
Funny.

Javascript is better than Java for the same reason that Scala is better than Java. Development of the Java language is now frozen that Oracle owns it. Oracle is just milking Java for money as a patent troll. If Java was still being worked on it would grow into what Scala is. Scala is basically statically typed Ruby. So with Scala you get a merging of Java and Javascript that cant happen in Java because Java is dead.

there are still too many idiots who use it though.
java is the new cobol

>>7
Pussy is better than anus for the same reason that oral is better than anus. Development of the anus is now frozen that niggers owns it. Niggers are just raping your anus in showers as black trolls. If anus was still being worked on it would grow into what oral sex is. Oral is basically statically typed hand job. So with oral you get a merging of anus and pussy that cant happen in anus because anus is dead.

Why not use Scheme, it is way faster than Jabfashit.

Why not use Go, it is way more beta than Jabfa.

javascript is an elegant, well-designed, consistent, obscenely powerful language unmatched by any other

it's blazing performance and frugal memory usage contribute to its innovative status as the language of the future

asserting any dominance of java over javascript is unfair and is detrimental to the advancement of computer science. it would be equivalent of performing a cleveland steamer on jesus himself!

>>11
Performance and memory usage depends solely on the interpreter/compiler used, so not relevant when talking about the langage itself.

>>11
A browser scripting language has nothing to do with the state of Computer Science.

>>12

nope. javascript's genius design guarantees those will function as designed

>>11
It's even more impressive that the designer pulled all that off in... what? A week or so?

Meanwhile, all of these other languages have been worked on for years and are pale in comparison.

Java applets was never particularly popular to begin with despite all the applet books. Back in the really old days:
1. Microsoft competed with it in every way possible (ActiveX, J++)
2. The browser could crash from just the applet runtime loading up, which wasn't uncommon when the machine had 16 megs of RAM and a few megs left on the 1 gig hard drive. E-commerce and serious sites are very paranoid of getting in every customer possible so you wouldn't find any applets in use here.

My personal opinion:
1. Mobile devices killed off applets of every type as excess baggage. Hundreds of megs have been saved.
2. Applets of every kind were designer unfriendly compared to CSS making division of labour harder, Java was particularly vicious in the ugly department with the gray square it would leave there while things were loading up, and the AWT made everything looked like a 1970s unix wm inside that box.

JavaScript didn't so much succeeded as it just survived from being integral to modern web page rendering.

>>5
LiveConnect, but I think JavaScript is an required intermediary to the DOM.

>>1
java was way faster
No, it wasn't, and it never has been.
had a consistent implementation
Being consistently broken and bloated does not a Good Thing make.
better graphics
Now you're talking about games, in which case you're ignoring shockwave and flash which had better graphics, was faster, took less memory, and didn't take years waiting for JVM to startup.
and a real class system.
Classes are shit and have always been shit.

I don't even like javashit but it's plainly better than java in every way, for the simple reason that java is nothing but (badly designed) OO and javashit at least has a poorman's implementation of functional programming. Couple that with JVM vs JIT and it's actually amazing that anyone has ever even bothered with java, let alone the fact that it's "lasted" as long as it has. Oh wait I know what's kept it afloat, lots of money poured into convincing ENTERPRISE CERTIFIED TURNKEY SCALABLE MANAGEMENT MUPPETS to force their code monkeys to use it in their businesses.

>>17
/polecat kebabs/

>>18
le epic irony for teh lulz /b/ro xD

>>18
/shalom hymie/

>>20
/newpol/

>>21
/lounge/

>>22
/anus/

I wish we had a /leah/ board. I'll ask moote.

>>24
I'd wish you would /polecat kebabs/

>>24
http://images.4chan.org/f/src/4dogs.swf

>>25
They don't know who is Leah Culver. They are pedophiles, just like you and they love japanese cartoons, just like you. Why should I go there?

>>27
You're off topic to the programming board.

>>28
You too.

>>25-29
You too.

>>32-
You too.

Java was way faster

>>皆さん
You too.

Java was slower in practice (probably still is in the browser, idk), doesn't have access to the DOM, you still can't count on the various implementations being consistent and prototypes are way more flexible than classes.

The only desirable thing classes do (apart from being generally better AoT-optimizable) is they sometimes provide compatibility with static typing, which usually contradicts the late binding principle of OO anyway. (Class systems are not OO.)

Java is a terrible scripting language.
/thread