Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Api Paradox

jacquesmattheij.com

Post reply on HN
Print view View original

31–40 of 44 posts

Re: The Api Paradox

#31

Post by kiriappeee »

brazzy wrote: post #2

Can we please, pretty please with a cherry on top invent a new word for "public-facing official API that exposes some of a company's core services"? Because I get annoyed every time someone uses "APIs" to make general statements while assuming that specific narrow meaning.

PAPI?

Re: The Api Paradox

#33

Post by Gmo »

jacques_chester wrote: post #24
DanielBMarkham wrote: post #22

Earlier quoted context omitted.

Dang, I'm surrounded by Jacqueses! (Jacuqi?) Thank you. I changed it to the Americanized form of possessive for words ending in s (pronounced or not) I think this could go either way, but I screwed it up no matter which choice an author might take.

Well in all fairness, outside of La Francophonie , "Jacques" is not a common name. And for English speakers it's just chock full of exciting traps. My favourite is putting 'c' and 'q' next to each other. In French that's a single sound; in English it says "new syllable, please! edit: > Jacqueses! (Jacuqi?) Jacqueses would be closest (-ii is a Latin pluralisation, Jacques comes from Jacob which is Hebrew). There's an…

I do think he is from Dutch origin though (Because he talked in the past about one of his experience with QNX in the Netherlands)

Re: The Api Paradox

#35

Post by j4_james »

pjmlp wrote: post #9

When are we going to stop calling API to web services? It always comes to my mind operating system API when I read such titles.

I always thought "protocol" was a more appropriate term for such internet-based APIs. SMTP and HTTP are clearly protocols, and even APIs built on top of HTTP are generally referred to as protocols in the standards world. For example WebDAV (RFC4918) and AtomPub (RFC5023) are both considered protocols.

Re: The Api Paradox

#36

Post by jacques_chester »

Gmo wrote: post #33
jacques_chester wrote: post #24

Earlier quoted context omitted.

Well in all fairness, outside of La Francophonie , "Jacques" is not a common name. And for English speakers it's just chock full of exciting traps. My favourite is putting 'c' and 'q' next to each other. In French that's a single sound; in English it says "new syllable, please! edit: > Jacqueses! (Jacuqi?) Jacqueses would be closest (-ii is a Latin pluralisation, Jacques comes from Jacob which is Hebrew). There's an…

I do think he is from Dutch origin though (Because he talked in the past about one of his experience with QNX in the Netherlands)

I was under the impression he was Belgian.

Re: The Api Paradox

#38

Post by pc86 »

richardjordan wrote: post #3

The key is I distinguish between an API which IS the business - something like a Twilio for example - and an API which lets you leverage a business's other assets in a way that might one day be cut off - like a Twitter. You are safe to build on top of something like Twilio because the service is the API and API consumers are the customers. Consumers of Twitter's API are not customers of Twitter and should not be surp…

I think you're still in a precarious position as the product. Just look at Facebook, Google et. al.

Re: The Api Paradox

#39

Post by Gmo »

jacques_chester wrote: post #36
Gmo wrote: post #33

Earlier quoted context omitted.

I do think he is from Dutch origin though (Because he talked in the past about one of his experience with QNX in the Netherlands)

I was under the impression he was Belgian.

Ha yes, also possible :)

Re: The Api Paradox

#40

Post by thebuccaneer »

SPSteinbeck wrote: post #37
thebuccaneer wrote: post #10

this begs for a 'no s--t sherlock' comment

And your response begs for a downvote.

why? for pointing out that, in 2013, someone had the revelation that if you fish in someone elses pond, be careful... because they might cut off your access?
Post reply on HN