Return to Answer

As in this other thread I would use "in the internet" in the context of Application Programming Interfaces, or APIs. While an Average Joe user reads content off the "front" of an internet website (its Graphical User Interface, or GUI), a function call to an API actually sends a programming thread into the content of the website to retrieve the answer. That retrieval lends a sense of depth, of looking something up in a website, that reading content that's already displayed on the front just doesn't.

As in this other thread I would use "in the internet" in the context of Application Programming Interfaces, or APIs. While an Average Joe user reads content off the "front" of an internet website (its Graphical User Interface, or GUI), a function call to an API actually sends a programming thread into the content of the website to retrieve the answer. That retrieval lends a sense of depth, of looking something up in a website, that reading content that's already displayed on the front just doesn't.

Like in this other thread I would use "in the internet" in the context of Application Programming Interfaces, or APIs. While an Average Joe user reads content off the "front" of a website (its Graphical User Interface, or GUI), a function call to an API actually sends a programming thread into the content of the website to retrieve the answer. That retrieval lends a sense of depth, of looking something up in a website, that reading content that's already displayed on the front just doesn't.

As in this other thread I would use "in the internet" in the context of Application Programming Interfaces, or APIs. While an Average Joe user reads content off the "front" of an internet website (its Graphical User Interface, or GUI), a function call to an API actually sends a programming thread into the content of the website to retrieve the answer. That retrieval lends a sense of depth, of looking something up in a website, that reading content that's already displayed on the front just doesn't.

Like in this other thread I would use "in the internet" in the context of A pplication P rogramming I nterfaces, because they pull information, which has a sense of depth. This is opposed to websites, which push information, not necessarily having the sense of depth.

Like in this other thread I would use "in the internet" in the context of Application Programming Interfaces, or APIs. While an Average Joe user reads content off the "front" of a website (its Graphical User Interface, or GUI), a function call to an API actually sends a programming thread into the content of the website to retrieve the answer. That retrieval lends a sense of depth, of looking something up in a website, that reading content that's already displayed on the front just doesn't.