Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As you are already aware, SEO is a big deal. SEO is usually the elephant in the room (e.g. the big deal) for javascript-based web-sites and you either forgo SEO or have to somehow design an alternate path that the search engines can index you via and that doesn't run afoul of their rules about serving different content to search engines.</p> <p>Some potential downsides:</p> <ul> <li><strong>Accessibility</strong> - access via screen readers and other tools that may be geared to the page HTML.</li> <li><strong>Mobile</strong> - Sometimes rendering the page will require larger downloads, more javascript code and more data and more CPU to build the page than a simpler server-rendered page. This may cause compromises on small devices without a lot of bandwidth or horsepower.</li> <li><strong>Performance</strong> - The initial page display time may be slower as you can't render anything until all data and code has been downloaded and run. Subsequent page times might be faster or slower depending upon how the app is written. Sometimes you save server trips by doing client-side rendering (which could be faster), but sometimes it's slower to do things on the client.</li> <li><strong>Security</strong> - Somethings simply can't be secured client-side the way they can server-side.</li> <li><strong>Code secrecy</strong> - Code in browsers is open to the world to see. Code on servers can be kept secret.</li> <li><strong>Same-origin limitations</strong> - Browsers are much more limited in who they can contact than servers are because of the same-origin limitation.</li> <li><strong>Memory</strong> - Lots of code and lots of data can consume a lot more memory for your app than a server-generated HTML page. This probably isn't meaningful on a desktop, but could be on a smaller device.</li> </ul> <p>Some of the upsides:</p> <ul> <li>The content can be dynamically rendered with lots of smarts based on the type of user, the screen size, the capabilities of the device, etc... and this local rendering can generally be done more effectively than trying to do it on the server.</li> <li>You can often do lots of the functions of the app without ever reloading the page, just fetching data from the server or issuing commands to the server with ajax and never reloading the page.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POwhat are the downsides of using javascript to build an entire webpage?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjfriend00
    1. USjfriend00
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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
    1. COThis is the biggest problem, although you can get around it by detecting the robot and serving it custom content (dangerous, if you get caught I believe you get punished pretty harshly.) The whole #! hashbang thing might be able to help in a more legit way too.
      singulars
      1. PO
      1. USdavid
    2. COThe question specifically states that he wants reasons other than SEO.
      singulars
      1. PO
      1. USMartin Hansen
    3. CO@MartinHansen - I know that. I wanted to emphasize that even though they said they were asking about things beyond SEO that it's usually the killer issue with JS page rendering. And, then I added some other issues relative to the question.
      singulars
      1. PO
      1. USjfriend00
 

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