That said, even as a hard-core C++ guy, I can't see why you'd really want to write a web application in C++. If you want C++-like syntax, you'd be better off with Java for web stuff.
That said, even as a hard-core C++ guy, I can't see why you'd really want to write a web application in C++. If you want C++-like syntax, you'd be better off with Java for web stuff.
And start saving money for memory and large amount of servers...
I'd really love to come up with a standardized way of deploying small, context-specific RESTful API servers in either C or C++. I'm starting to think that a possible C++/Python bridge via Thrift is likely the best option. But then again, if I just managed to keep it all in a C++ application without needing to run the Python interpreter, it could totally rock (for an application that is supposed to serve 100k+ users on cheap hardware).
It's cool to see cloud computing going mainstream and now applications written in any language can be reasonably fast with the help of EC2, a load balancer and memcached. But I still think there's great value to coming up with truly lightweight solutions that really use nearly all computing power a single node can possibly offer.
That is compounded with the typical architecture of Java frameworks. Also finding issues sometimes feels like occult magic on modern JVMs. And then, running with compatibility issues on JVM versions and all that.
Java failed in the browser and now it will probably have a crash at the server. There is no more budget for multimillion dollar datacentres everywhere. But thanks for all the jobs! :)
http://shootout.alioth.debian.org/u64/benchmark.php?test=all...
It's no proof, but real life shows something even worse than that against Java. For example the one thread per connection model everywhere or the XML web services throwing away objects faster than the GC can handle.
Hence my statement: > ignoring the way "enterprises" mostly use java (which is just silly)
Of course the thread per connection model is long gone (at least what I have heard, but software tends to not die) and the XML beast is dying... but that it more how people abuse it.
but if its memory you want, you can't do better then using the OS to its full power via C/C++, which is what you are doing when you are using C/C++. Using anything that is a full VM (like jvm, or if you think that is opaque - give erlang a try !) then you kind of tell the OS to "go away" and the VM becomes an OS etc...
You can't generalize like that. It's a language. It works. It scales, and is solid.
Sure, if you're just putting up something that needs quick prototyping then java is probably overkill, but if you're writing something quite complex, java can do a great job.
I think the "golden bullet" for startups is having a good programmer with a passion for something. Language isn't so relevant IMHO.
(Mibbit currently handles around 3.5million visits a month on a single VPS in java which I'm pretty happy with).
Second, please look my other posts 4 and 6 minutes before this one you just did.
On a C++ thread some people above say the thread creator should use Java. I refuted that argument with my opinion and reasoning. It is not bashing:
bash: - To engage in harsh, accusatory, threatening criticism. -ing When you deliberately attack a person using offensive and/or inappropriate language.
See on top of this page: "Suppose I wanted to write a C++ based web application... [...] But what if I just wanted to write plain C++?"
Can't Java people play along? Can't you guys even play pretend? There are very good comments in this thread (both pro and con.) And if you think C++ Web Applications are a bad idea, fine, say so and state your case. There was no need to bring up Java. Of course you are free to do so. But that allows others (moi) to counter-argue with you.
Thank you.
I don't think anyone would have really jumped on the memory comment originally, but what made the thread asbestos-o-riffic however was the assertion that Java is inappropriate for a startup, which is, well, just plain silly.
In a comment 15 hours ago I stated it's probably not worth it due to current cheap hosting prices.
Web apps can work in any language (I wrote a couple in assembly once)...
Choosing the language is not really that important.
Having big images/videos wouldn't really make any difference to which language you choose. That's just static media files which are irrelevant.
I really don't see how having more images on the page would make it harder to scale :/ if only the site were as simple as serving up some images...
Apparently that is all too hard for some web 2.0 startups.
I'm thinking of ditching JSP and have PHP talking to our Java services via Thrift.