StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Other options:</p> <ul> <li><p><strong>Database:</strong> I'd like to point out <a href="http://www.mongodb.org/" rel="nofollow noreferrer">MongoDB</a>. Every time I suggest using it, I get beaten up by SQL-people. But from my personal experience, it proved signifficantly easier going with document-oriented stores.</p></li> <li><p><strong>Platform:</strong> Well is Java just an option? Or are you sure you want to take it? There are many languages out there, each of which has its own advantages. There are two reasons, why you should pick a specific language. 1. the language is good for the job, or 2. you are really good using the language. Personally, I am an advocate of haXe, which is why I just had to mention it :)</p></li> <li><p><strong>Technology:</strong> When it comes to Java, I cannot be of much help. But from what I understand, there are <a href="http://java-source.net/open-source/web-frameworks" rel="nofollow noreferrer">a lot of really great frameworks/solutions</a> around. To my understanding, Struts really is worth looking at. Also, I rememeber I once stumbled upon an all in one solution, that employed GWT in the frontend. Some short, slightly russian-sounding 2-sillable name starting with "v" (if that's any help^^). So far, it was the most impressive I saw, but I forgot its name. :(<br> Basically, you should rather choose a framework that seems fit for your job, and then employ whatever technology it runs on.</p></li> <li><p><strong>Server:</strong> Again, for Java, your call.</p></li> <li><p><strong>Clientside:</strong> GWT is stable. Talking JavaScript, you can go with qooxdoo and sproutcore. Both are aimed at creating RIAs. Other than that, Prototype, jQuery, Ext and MooTools. In contrast to the former two, their role is rather to facilitate common tasks in making HTML pages interactive, than creating persistent JavaScript-apps.</p></li> <li><p><strong>Database Communication:</strong> That really depends on the datastore and platform you use. Usually a framework makes this decision for you. Unless you're really planning to do some heavy datamining, you should rather use the abstraction layer any popular framework provides, than to DIY. The code is mature, robust and tested, removing one possible source of errors and security issues.</p></li> </ul> <p>greetz<br> back2dos</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload