I've lived through this discussion for the past 3 years while writing web applications using Ruby and Rails. Here's what I've learned:
- Using a language that the average stupid programmer can't understand virtually guarantees that you'll increase your success chances, since you and your team-mates will be of a higher caliber. - The world is always going to tell you that using Clojure is a bad idea. - If you think using Clojure is a good idea and you and your team are excited about using Clojure, it's probably a good idea. - If you think using Clojure is great for your application, but bad for your company, look for a new company. - You aren't going to find a job in your favorite city using your favorite language in your favorite domain. Decide what you value the most and go from there. - Don't hire consultants when using bleeding edge technology. I could probably go on for hours. The bottom line is, it's entirely contextual, and you're smart enough to look at Clojure, so make the smart choice on whether it's right for your situation. Cheers, Jay --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
