Funny to hear that. In my professional (paid) web development career, I went from Perl to ColdFusion to Tapestry to Wicket. Of course, I've stuck with Wicket. But, I'm also now doing a little PHP (with Symfony framework - more on that later).
I spent about five years working for a subsidiary of eBay and most of that time worked on a ColdFusion application. We converted it to Tapestry. I could probably safely say that it's about like any scripting language. It has pros and cons. But if you really love Wicket, you're likely not to like CF. And, it seems like in that sort of language, you are much more likely to walk into a rat's nest of nasty code. Some questions to ask: Do they use any of the major CF frameworks? Mach II? Do they use a modern version of CF and use MVC / object oriented code? Or do they have CFM pages that have queries and markup right in the same file? Or do they think that "includes" or "custom tags" are the right way of separating logic and markup? If you find that they are using a modern version, using an MVC framework like Mach II, etc, then it probably won't be too bad. In these modern versions, you can actually tie in java code pretty easily. But if you really love Wicket, my guess is that you won't truly enjoy CF development. But, hey, there are many things that make a job decision. I never thought I would enjoy any PHP development, but this year took a gig doing some PHP development using Symfony - and actually enjoying it - because it gives a clean separation, is oo-based, has a built-in ORM, etc. Surprised even me. Happy (job) hunting! -- Jeremy Thomerson http://www.wickettraining.com On Wed, Oct 7, 2009 at 10:33 PM, Jamie Swain <jpsw...@gmail.com> wrote: > Hey guys, > > I know this is an unusual question for this list, but I was hoping > that I could get some viewpoints and info about something. I recently > interviewed for a job opportunity at a company that runs their core > app, comprised of both web interface and web services, in a cool niche > that I would like to work in. > > Also the company seems very cool over all. It's a nice size, a small > development team, and the guys I met seemed really good. > > The big problem is that I'd be working mostly in ColdFusion. When > they told me that in the initial, pre-interview email, I thought jeez > is anybody using that still. I had never had any hands-on experience > with it, so I spent the weekend with a decent book working through > some exercises on my laptop. What I found was that my initial > impression was, "this language sucks, it is a pain to use." I admit > this is only after spending about 3 days with CF and I really didn't > go into it with my mind wide open. > > So, my question would be, if anyone here has experience with CF, is it > really as bad as it seems? As someone with a passionate, nearly > religious fondness of Wicket, will I hate every minute of CF as much > as I fear I might? Is there any chance that after trying to accept > some of the things I already don't like that I will find that I can > still enjoy programming a cool product even if the underlying system > sucks? > > Thanks for any info/thoughts! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
