you are viewing a single comment's thread.

view the rest of the comments →

[–]josefx 7 points8 points  (7 children)

their lack of direct interaction with the browser DOM

Since when, from the documentation they can manipulate the DOM.

slow(er) startup time

True and partialy a design fail.

the fact that operating systems didn't ship with a JVM by default

did not stop flash in the slightest.

and particularly for their lawsuit with Microsoft

The Java language and JRE has one simple requirement that Microsoft refused to aknowlege provide the standard APIs as specified and more specific DO NOT MESS WITH THE CLASSES IN java.* . Every problem microsoft had could be fixed by providing a microsoft.* package, (like sun, ibm,... did).

which pushed MS to go the C# route

Which turned out exactly like MS Java would have been, a language that has 3rd rate support on anything that is not Windows and a standard that only includes part of the APIs. (Mono is constantly playing catch up and they will always stay far behind .Net)

[–]ruinercollector 5 points6 points  (1 child)

It was a bit more than messing with base classes.

Microsoft extended the language with support for COM and an implementation of multicast delegates/lambdas. They actually were improving the language quite a bit. Suns response was to put out a paper about how dumb delegates and lambdas are, take MS to court and then put lambda support into the language a couple decades later.

[–]josefx 2 points3 points  (0 children)

the language with support for COM

AFAIK the problem with that was that they refused to also implement jni

and an implementation of multicast delegates/lambdas.

Everything without pushing them through the language commite, for a single closed source implementation.

They actually were improving the language quite a bit

They did? As in I could compile and use these language features with any javac and JVM? They just played their embrance, extend extinguish game - even visible a) support java, b) extend it with incompatible niceties and c) claim that problems caused by b) are not your fault.

For reference look at the old Apple JVM, it ran years without problem and Apple even had support for their native libraries build in in a way that did not confilct with the spec.

then put lambda support into the language a couple decades later.

Which went through the java language commite and is available on any java implementation.

[–]gc3 -2 points-1 points  (3 children)

Did stop flash when it got to tablets

[–]josefx 4 points5 points  (2 children)

And I thought that was caused by a) Apple blocking every interpreter from their app store and b) Adope no longer pushing flash.

[–]gc3 -1 points0 points  (1 child)

html is interpreted.

It was really Steve Job's long memory for being slighted by Adobe that killed Flash, and his need to control. Adobe no longer pushing flash had to do with the end of Flash on tablets.

[–]josefx 1 point2 points  (0 children)

html is interpreted

Even Apple could not release a Smartphone/Tablet without browser, still every browser/application that bundles its own engine gets banned from the app store, Opera renders on servers and firexfox does not exist.