I think it's a no-go situation for me, frankly. But I'm
having a conference
with the client this morning to find out more about what he
wants. Expect
more later....
--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Chris In Madison"
<cowens@GOAWAYDIRTYRATSPAMMERScnw.com> wrote in message
news:ee92ic$bb2$1@forums.macromedia.com...
> Java is a gigantic technology, to be sure. I've spent a
lot of time
> studying it and still have a hard time with it. Those
that use it swear
> by it, those that don't use it much swear at it.
>
> The other thing that makes Java so difficult in the web
arena is that
> there are so many frameworks that extend the base Java
technology. And as
> Forest Gump says, you never know what you're gonna get.
Dreamweaver codes
> JSPs using the "scriptlet" method, similar to the way
ASP and PHP are
> written. This technique makes most hard-core Java
developers cringe.
>
> I maintain a Java-based system and I do everything I can
to stay away from
> the portions of the system that require me to touch the
code. It's way
> bigger than my brain can handle compared to the other
technologies I'm
> used to.
>
> So, to make a long story longer, unless you know Java or
have an undying
> urge to learn it, it might be best to decline the job.
On the other hand,
> if you want to work for The Man, Java developers tend to
make a large
> chunk of change (and for good reason), and the practice
might be good for
> you :-)
>
> Best regards,
> Chris
>
11
Replies
AdChoices