You have a lot of duplicate functionality in your language choices. There's a difference between learning programming, and learning enough programming to get an MVP.
I think I would take the idea, break it down, figure out what it is going to take to do it, then, learn the different pieces that will allow you to construct it. Java, PHP, Python duplicate effort. From a webapp deployment standpoint, you might find PHP or Python to be easier to deploy than Java. You might find Python to have some slightly better frameworks available than PHP which leads to more agile development. You've left out Ruby/Rails.
I don't know what you're trying to write, but, Haskell for a front-facing webapp might not be optimal. For many backend tasks, you might find it to be useful.
I don't know how you learn, but, two months immersion into each language will give you a good idea of what each language could do, but, 8 months in Python with a Framework would probably get you very prepared for your two month HTML/Javascript/(XML|JSON)/JQuery stint before executing your idea.
Unless your idea doesn't involve storing data, you may have missed SQL/NoSQL technologies - MySQL/PostgreSQL or CouchDB/MongoDB or key/value stores MemCached/Redis.
Granted there are other technologies - you could probably spend a month reading thousands of benchmarks and come to absolutely no conclusion as to what you want to use, so, use this metric: Find out what people you know are using and use that. You'll have someone to bounce ideas off of, push you through points you don't know, etc.
Now, there is a special exception in the rule above - Redis. Redis is absolutely, positively powerful - beyond a key/value store. antirez frequents HN a bit, is super responsive on Twitter and has been pushing out some really cool stuff. Once you understand lists and sets with Redis, you will find that you aren't really just dealing with key/value. Depending on what you are doing, you could easily use Redis for your MVP (and use it beyond launch).
If you go Python, Pyramid or Django, perhaps Flask.
Ruby on Rails
PHP, cakephp, kohona, codeigniter
Java Play
Any method you choose, I would suspect you could pick pieces and write them along the way rather than waiting until November.
And don't think people aren't interested if you haven't given them a chance. You might find some very valuable feedback or an angle you hadn't considered.
I think I would take the idea, break it down, figure out what it is going to take to do it, then, learn the different pieces that will allow you to construct it. Java, PHP, Python duplicate effort. From a webapp deployment standpoint, you might find PHP or Python to be easier to deploy than Java. You might find Python to have some slightly better frameworks available than PHP which leads to more agile development. You've left out Ruby/Rails.
I don't know what you're trying to write, but, Haskell for a front-facing webapp might not be optimal. For many backend tasks, you might find it to be useful.
I don't know how you learn, but, two months immersion into each language will give you a good idea of what each language could do, but, 8 months in Python with a Framework would probably get you very prepared for your two month HTML/Javascript/(XML|JSON)/JQuery stint before executing your idea.
Unless your idea doesn't involve storing data, you may have missed SQL/NoSQL technologies - MySQL/PostgreSQL or CouchDB/MongoDB or key/value stores MemCached/Redis.
Granted there are other technologies - you could probably spend a month reading thousands of benchmarks and come to absolutely no conclusion as to what you want to use, so, use this metric: Find out what people you know are using and use that. You'll have someone to bounce ideas off of, push you through points you don't know, etc.
Now, there is a special exception in the rule above - Redis. Redis is absolutely, positively powerful - beyond a key/value store. antirez frequents HN a bit, is super responsive on Twitter and has been pushing out some really cool stuff. Once you understand lists and sets with Redis, you will find that you aren't really just dealing with key/value. Depending on what you are doing, you could easily use Redis for your MVP (and use it beyond launch).
http://news.ycombinator.com/item?id=2085351 (written with Redis + Jquery)
Any method you choose, I would suspect you could pick pieces and write them along the way rather than waiting until November.And don't think people aren't interested if you haven't given them a chance. You might find some very valuable feedback or an angle you hadn't considered.