Chris McCormack wrote:
I think the question that no-one has asked is what happens if you don't
learn and embrace JSF now and get it on your list of skills?
Even if you despise it (I have no preference yet), is it not a good move to
get familiar with it regardless (if you can)?
I think this is dependent on whether or not you'll program anything they
tell you (programming whore) to or if you have a set of criteria for
what you're willing to do. This is the same for any technology, it's
just that J2EE spawns acronyms like a demon-possessed bunny because it
HAS to to survive and even _approach_ usability.
I personally simply don't have the time to "get familiar" with all the
latest acronyms, and the vast majority of sites I work on simply won't
benefit from almost every J2EE acronym/technology I run across.
As an off-topic example, I left a decent game programming position
because I thought spending a year working on a 3DO project would be a
waste of time as I felt the technology would die. Remember the 3DO?
Exactly: good choice. (Although JSF has a WAY better chance of survival
than the 3DO ever did :)
Should I worship every god/dess just in case they're the one/many true
One/s?
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
