Databases
StackOverflow2013
Postsdbo
POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
    primarykey
    data
    text
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USintermension
    1. USintermension
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
      1. This table or related slice is empty.
      1. VTDownMod
    1. COFrankly, I think that the explanation is very simple, the statement is completely wrong. Compiler optimizations *have* advanced some, but not nearly enough to make up for the massively greater abstractions present in the typical modern OO languages and the additional parameter-aliasing and thread-safety restrictions that come along with the more capable modern OS environments. Plus in-lining was everywhere back then, and is less prevalent today for the same reasons. Line-for-line the older languages were easily *much* more machine-language optimal. What saves us today is 10-100x faster HW.
      singulars
      1. POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
      1. USRBarryYoung
    2. COWhoops, I just saw DigitalRoss's answer, he's got it too.
      singulars
      1. POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
      1. USRBarryYoung
    3. CODo you think the assertion that older/procedural programs contained longer methods is correct? If so, what do you think caused people to write longer methods? I'm not sure I agree with the statement I quoted but at the same time I cant see why you'd choose a Long Method style in either paradigm unless there was some good reason to do so. Although merely 'assuming' a good reason for the way anything is done is likely a slipperly slope. :)
      singulars
      1. POHow have "modern OO languages pretty much eliminated [the] overhead for in-process calls"?
      1. USintermension
 

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