Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you were going to build a new language... and you came up with all the semantics and it was complete, and you had some magic box that had a switch between making the language compiled vs. interpreted, the compiled version would be faster than the interpreted version.</p> <p>Why? Because <strong>compiling</strong> brings your semantics down to a lower level on the machine which means it can executed much faster, whereas <strong>interpreting</strong> means the semantics of your language will translated by some <em>thing</em> (i.e. the interpreter) when the user actually uses your site.</p> <p>Having said that... that doesn't necessarily mean that your site is going to 100% run faster on a compiled language vs an interpreted language. There are interpreters out there that are very fast nowadays for various languages (i.e. PHP), and there are even optimizers for interpreted languages that make them faster even still.</p> <p>There are many other things that go into the performance of your site that are agnostic of the language you choose. Hardware setup, Database setup, Network topology, etc. These things can have a bigger impact on you. I would suggest measuring to be sure.</p> <p>For me, finding bugs at compile time is a <strong>huge</strong> time saver, so I tend to prefer compiled languages which are strongly typed. It lets me get my work done faster, but that doesn't make it objectively the best option. Some people have no issue writing weakly typed code, and running test suites on them to verify their functionality, which I would think would work just as well.</p>
    singulars
    1. This table or related slice is empty.
    1. POInterpreted vs. Compiled Languages for Web Sites (PHP, ASP, Perl, Python, etc.)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJoseph
    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. COQuibble: There remains the possibility that a JIT running on an interpreted language can make some optimizations in a *particular running case* that a compiler could not make because they aren't universally reliable. I have seen some claims that Java sometimes. succeeds at being faster than compiled languages because of this.
      singulars
      1. PO
      1. USdmckee
    2. CO@dmckee I would argue the case that if I had a compiled Java and a JITed Java that my compiled Java is always going to run faster. I have yet to see a circumstance where this can be false. However, I'm not making the claim that a JITed Java is always slower than a compiled C#, that to me is comparing apples and oranges in this case.
      singulars
      1. PO
      1. USJoseph
    3. COConsider `for(...){...if(cond){...}else{...}...}` where `cond` is known to fixed in this run, but could be variable over the loop in general. The JIT compiler could drop it the check and shorten the loop, while the general compiler can't. Never seen this matter myself either, but I have heard it claimed.
      singulars
      1. PO
      1. USdmckee
 

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