A Java Perspective

I got a lot out of this thread. It’s nothing earth shattering, new, but it does point out a consolidated list of, what I’ve come to think of as a typical web Java developer’s issues with the Flash family. The point isn’t my stereotypical/not-so-accurate classification, but Macromedia’s reaction to the points in the email that I’ve managed to see over the years. He even echoes the server-side dependency, though, to the multiple tiers, I say get another developer and to the server, I say just upload the SWF’s.

The last sentence just made me laugh out loud. Yeah, I coulda’ lol’d, but it just deserved the written out phrase.

“Why Macromedia needed Action Script and not addopted Java instead to develop the Flash Player … or maybe I’m missing something…”

I wanna yell while still laughing, “Where the heck were you at Flash 5?”, but then I remember things for the RIA world were pretty underground then, and I still refused to use that crappy program called Flash because Director ruled the known world, and I was learning to own Director. You know, that doesn’t do it justice, I can’t really summarize the swath of ironic and non thoughts I get all up in my head from reading that; the one thing I do know is it still makes me laugh.

Anyway, blogging here since the list is more for answering questions, not for chatting, and carrying the same crowd, at least for now, to Flashlounge doesn’t seem reasonable/realistic.

One Reply to “A Java Perspective”

  1. You know, I really shouldn’t write blog entries when I’m tired. Basically, I found this email eximplfying expectations I’ve heard time and time again. The Flex server shouldn’t be a server; use a cached SWF instead. ActionScript should be more like Java; it’s growing there, in a maturing fashion at a steady pace, but only to the point it needs to be similiar since it solves different needs. Flash Player is your presentation tier and needs to be easily integrated with a debugging process, whether that means extremely easy debugging, or at least effective unit testing.

Comments are closed.