I like Mr. Wall w/o the filters, and listening to this episode has
finally got me around to getting this off of my chest. Maybe the rest
of the world will curse him for winding me up, but I'd like to say
thanks.
What I find disturbing is the fracturing of the Java runtime and
language features.
I love what bits I have seen of JavaFX that have worked well. I am
with Joe - the key is now the experience for end users (including me)
on all the browsers: firstly, does everyone have it? if not, how quick/
idiot proof is it to be up and running. I still noticed too many of
the demos were
While GWT is really cool for those who want to write Java, not
JavaScript, it is essentially a giant workaround. The real solution is
better Java Plug-In penetration and just using it. Java 6 Update 10 and
later are actually rather good.
GWT predates Java 6 Update 10 and I can understand
tronda wrote:
I think the main reason is what Carl said. With HTML 5 Google is able
to drive the standard. With JavaFX/Applet/JavaPlugin this isn't the
case. Flash the same. The web standards has served Google good in the
past and I think this will be able to serve Google good in the future.
It's all about the lowest common denominator, which is what Google
really gets. They don't care about Java in the same passionate/
religious way as i.e. Dick, to them it's just a tool and a marked to
be harvested. That was one of the most interesting parts of the latest
podcast, Dick putting Carl
Just looked at the latest docs. Still seems like a tough task to render small
clipboard-friendly elements.
Alexey
From: Joshua Marinacci jos...@gmail.com
To: javaposse@googlegroups.com
Sent: Saturday, June 27, 2009 5:11:53 PM
Subject: [The Java Posse] Re
Great to hear Josh. Of all the todo things, I think the user
experience regarding how is starts up, how it installs if needed, will
make or break this. The rest of it is certainly great, would be a
shame for it to go to waste for the last mile !
On Jun 28, 4:51 pm, Joshua Marinacci
I have to disagree regarding GWT. I've been using it extensively on new and
legacy web app projects. I could kinda see using applets in situations, where
I knew there was no need to ever interoperate with DOM (and the state the
plug-in is in now, still leaves it behind, IMO), but once you are
With the new plugin Java and JavaFX applets can easily interoperate
with the DOM. You can call javascript from java and vice versa. It's
quite nice!
On Jun 27, 2009, at 11:44 AM, Alexey Zinger wrote:
I have to disagree regarding GWT. I've been using it extensively on
new and legacy web
On the subject of HTML 5 driven apps like Google Wave (didn't know it
required html 5 until this last podcast). The pirate bay is releasing
their answer to YouTube via the VideoBay.
Interestingly they will only support HTML 5 browsers and up, so I
guess there's more than just Google already
Reinier's summary seems accurate based on my experience (with both a
LOT of GWT and jQuery) - good advice - the comments on the podcast
seemed factually quite wrong (but no one has experience with GWT, so
not surprising) - I guess (another) interview with someone from the
GWT community/google
give it a try. The browser plugin has made huge strides in the past
year.
re Joshua: yeah I like that idea. Years ago I wanted to do that with
applets and live connect but it wasn't easy, I do like the promise
of it now - but the problem is its still a promise, its a risk to take
over
12 matches
Mail list logo
