If you're just starting out with web development chances are you'll be soon overwhelmed with tech jargon. You'll begin to ask yourself "what is AJA...
For further actions, you may consider blocking this person and/or reporting abuse
A few other terms I would suggest, since they are becoming more and more common:
will do!
Nice! Maybe to add Cross-Origin Resource Sharing (CORS)
will do, cheers
Please explain what's that
By default, browsers doesn't allow a domain to get or make calls to domains outside, cors enables that share between domains :)
Can you offer constructive criticism and show us a proper definition for Native APIs?
Google it
Do you have any problem with the stuff I write George?
dev.to/dexygen/comment/jgcc
If so try to offer constructive criticism instead.
Happy holidays.
If that's all you're arguing about; querySelector is part of an API because the function doesn't do just one thing but different things depending on the string passed. It's an API to access the elements in the DOM. Sure we can "Google" and find someone explaining it differently, but OP's explanation has nothing wrong about it and you're being very harsh by saying things like that.
A function doing different things based on the string passed does not make that function anything close to an API. And you, an intern, arguing with me, with 20+ years development experience, is laughable, especially because your argument isn't even close to being correct.
You using people's status to validate your point is laughable. You can say all you want about your 20 years experience but it has literally no value in this argument. Use that experience to make better points instead of just saying everyone is incorrect because a single thing doesn't fit exactly your understanding.
Didn't read your reply, and won't be reading any more of them. If you don't like my replies, flag them. Or more constructively, give the following a read: dev.to/dexygen/dev-to-posts-tagged...
@simon Landry
Like you wrote querySelector is part of API, nobody objects to this. But is not The API.
I hope you are not claiming that the Document object what exposes the querySelector method has 30+ APIs, one for each method. All those methods are part of the same API. Generally speaking: one API -> many objects with many methods.
2 An API is not a toolkit, just a collection of methods to access an application.
Method in this context is not the OOP term for methods of objects, but means any method, i.e. could be an HTTP call, invoking a function exported by a Windows dll or an RPC call. Applications can be both remote and local and this is important to mention because some people think APIs are for remote web servers only.
"a set of tools, a toolbox which is built by other developers and ready for use" is an SDK (Software Development Kit), although sometimes framework term is also used in this context.
6 Web API can also refer to APIs available through web (i.e. HTTP) and I have a feeling that this meaning is more common.
en.wikipedia.org/wiki/Web_API#Serv...
docs.microsoft.com/en-us/aspnet/we...
7 ECMAScript is not an official or alternative name for JavaScript but a standard. JavaScript is only one of the implementations of this standard, even if there are no other notable implementations left.
12 Is node.js used on client side at all?
14 I wouldn't treat web server and web service terms the same. Web servers are typically serving web pages for humans, web services are typically providing services for other services or applications through web. Any service is typically for machine use.
16 JSON can be used in any data interchange, is not limited to web applications or web in general.
17 REST API is definitely not limited to exposing data, it is widely used to execute commands and create data too. Although in many cases there is a database in the background it is not correct to state that a REST API is for interacting with a database.
A REST or RESTful API is an arbitrary API with very specific requirements like has to be stateless. Unfortunately many developers are too ignorant to look up the definition and call any HTTP API REST and this sometimes leads to confusion.
18 Your definition is a very limiting subset of what a transpiler is: a tool what transforms source code to source code in another programming language (translating compiler). A typical example is TypeScript compiler (tsc) what takes TS source code as input and outputs javascript source code, despite being called compiler. The input and output languages and versions are irrelevant, in fact many transpilers can consume and produce different versions of the same language.
19 RFC is a must mention term.
21 Like others mentioned it should be pointed out that vanilla means light, basic in programming terms.
22 XHR is a must mention here.
24 Isn't really the browser what gives permission but the web server and the browser blocks or restricts access based on permissions acquired from the server.
25 Since websocket support has become almost omnipresent it is used in any scenario where server side notifications have to be sent to clients (push notifications) because polling is rather expensive. I.e. Gmail and other web email clients use websocket despite not doing chat or real time.
26 With the rise of Web SQL SQL is no longer a server side language. NoSQL is a must mention on this topic, especially since we have IndexedDB in browsers.
27 GraphQL is a query language but is nothing like SQL. It is in fact somewhat similar to NoSQL what itself is very different to SQL.
You are very enthusiastic what is not a bad thing except when is not backed by proper knowledge. It would also help to ask someone to proofread before publishing, both linguistically and technically. Would be nice (technically mandatory) to provide the source for your quotes, i.e. a link to original. Examples help too. Links to relevant definitions, articles add lot of value.
I appreciate your notes and I adjusted the post a bit. But don't assume anything about me just because here I used some definitions loosely, on purpose.
It's true that we ought to be rigorous when teaching stuff to beginners, but I don't think people is "ignorant" like you said.
I feel like number 15 should be changed to be about HTTP response codes in general (of which the 4xx and 5xx error codes are a subset of) rather than just error codes. Otherwise a beginner might think that all response codes are error codes (which would be wrong).
Number 14 should probably be clarified too..."machine-machine" is ambiguous. My phone (machine) runs a browser that makes HTTP requests to a server (machine), most of which are not exhcnaging JSON data. I think what you really mean is frontend to backend communication exchanges JSON usually? And are trying to distinguish that from browser web page requests? Anyway, I think that phrase should be clarified as it's a bit broad!
I changed #14 a little bit. Let me think about #15. Cheers
Web Worker, an API that work like background processed your statement. Web worker usecases mostly on heavy load fetching a ton of data from REST / GraphQL for plotting a graph, and when you want to make an autosaving input, etc.
Gold!!
I think Vanilla anything should be added. E.g. Vanilla PHP means PHP without using frameworks such as Symphony or Laravel.
Stock is also synonymous to Vanilla in this context
Wish I could share this with a friend .. basic and simple to understand
The easiest way would be to copy/paste
Contrary to popular belief, "npm" does not stand for "node package manager". It actually stands for..... Nothing. The three letter have no official significance.