My 2 cents worth...
1. PHP is a dying language IMHO. The alternatives are just too compelling unless you have an existing code base in PHP. 2. Javascript is the lingua franca (or assembly lang) of the internet for the time being and probably the foreseeable future. 3. Many webapps are moving to the client-side instead of the server centric PHP/CGI oriented designs of yesteryear. Again, this means Javascript (and/or ClojureScript) primarily. 4. You can adopt Javascript as your primary language for both the server (nodejs) and client (browser.) This way you can use ClojureScript to target both on an as-needed basis. This also lets you leverage lots of existing libraries on both sides. 5. If you need to target mobile devices PHP might be somewhat limited. There are tons of Java (Android) and/or Javascript/ObjC (iOS) options to target mobile clients. 6. My guess is that most API integrations will be via either Java (on the server) or in Javascript on the client. 7. On the server you can serve different endpoints using different technologies. Maybe your support.xyz.com is a hosted PHP forum app but your REST API is built using Clojure/Ring. 8. Many externally exposed APIs are actually network protocols (REST or ZMQ, etc.) and are thus largely language neutral (assuming there is a language binding for your chosen protocol.) However, I suspect that using PHP will be very difficult from a protocol/binding point of view. Hope this helps. Good luck! Alan On Tuesday, March 11, 2014 4:29:06 PM UTC-7, Jarrod Swart wrote: > > Sean, > > Oops I didn't realize you were asking these questions: > > > - What are you building? > - An application for businesses to help leverage the power of > crowds in non-traditional "crowdsource" environments. > - The main use-case for many will be that of integration with-in > their own applications and I suspect the application will be more API > than > App centric. Sorry for being vague but I'm still learning too. I will > know more for sure when I actually have the meeting with the founders. > - Why do _you_ think Clojure is a better choice than PHP? > - Due to the limited number of developers (just me initially) I think > Clojure presents a tool chain that is familiar and fast. Dynamic > programming in a highly iterative development environment means that I > can > solve challenges that the business will face rather than challenges > presented by the programming language. > - Clojure is to programming what Lean\Agility are to business > process > - Wanting to work with a set of tools also goes a long way > toward dealing with the other hardships of an early stage company. > If I'm > making less money and failure is a big part of the equation I want > to enjoy > what I'm doing. I think future hires would agree. > - The heavy amounts of text we will deal with is much easier to > handle with the JVM than with PHP. PHP support for UTF-* is fairly bad > (compared to Golang or Clojure) and I have had enough personal trouble > with > it. > - Again though we are not "Big Data" the first processing > bottleneck will likely be dealing with large quantities of text. This > is > something that Clojure and the JVM have a lot more options for dealing > with. > - The JVM platform means that when it comes time to optimize for > performance we have options rather than an app rewrite. > > > > -- 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 Note that posts from new members are moderated - please be patient with your first post. 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
