Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The trend in web development is to move more towards the client. This has several consequences:</p> <ul> <li>As the codebase grows on the client, a framework is going to become indispensable. You're going to see a heavy increase in framework usage across the board.</li> <li>The server will become less and less involved with page rendering, and gradually become more of a services provider. The new stuff I build today only talks with the server across JSON-RPC, and in my personal opinion this develops faster and scales much better.</li> </ul> <p>Which frameworks will "rule the roost" is hard to guess, but if I had to ...</p> <ul> <li>JavaFX can be safely ignored, it's going nowhere.</li> <li>Web apps are going to be predominantly javascript-based. For some types of apps flex and silverlight will be the chosen solution (e.g. video, games), but for most business apps the edge is just not there.</li> <li>GWT is going to become the go-to platform for enterprise java web app development.</li> <li>The number of projects that "roll their own" code is going to dwindle to near zero. It just isn't worth the effort anymore given the quality of the frameworks out there.</li> </ul> <p>Within the javascript framework subset (discounting GWT), I'm assuming the following:</p> <ul> <li>JQuery is going to remain the primary solution, but it's going to be augmented with extensive component collections (JQuery UI), so as to match what the other guys can do.</li> <li>Dojo, YUI and Ext are going to fish in the same pond and will all do well marketshare-wise.</li> <li>Prototype is probably going to remain a major player for website augmentation, but is not going to be relevant for web apps.</li> <li>You're going to see a few frameworks grow in marketshare at the expense of all the rest. The market is going to standardize on a few major players. This will happen primarily through the job market, with employers preferring "standard" platforms over "whatever the new guy likes".</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POThe future of web-development (RIA vs. traditional HTML)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJoeri Sebrechts
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POThe future of web-development (RIA vs. traditional HTML)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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