Yeah ByteByteGo are extremely inconsistent. They often make absolutely garbage videos that explain things wrong, use incorrect concepts... It's so weird because they also make extremely good ones
This is why any developer that has experience outside of web dev just bites their tongue at the cringe in interviews conducted by “tech leads” who’ve only lived in one universe like web dev.
I've always seen it like this: An API is to be consumed. An SDK is software in your language of choice that consumes the API in question, but in a particular, prebuilt way. The SDK is usually built by the company who owns the API. But it is only one of many ways. You don't need the SDK, you could build your own software to call the API in question, but you do need the API. Nevertheless, even if you could build your own software it is worth installing the SDK simply not to reinvent the wheel.
For a succinct 5 minute video you cover the majority of the truth here. Well done. People get nit-picky and want to point out what you didn't cover. Perhaps at the end of your videos suggest resources like online lectures or good books on the subject. Well done mate!
Api doesnt necessarly means its a web service (endpoints) it could be any ressource its could be modules and libraries like the sqrt math library python or hardware
I guess titles of video should begin with web . Its not meant for ppl that builds firmwares or low level programming. He clearly says modern programming and nowadays modern softwares are almost all web based, react native for phone app, electron for desktop app etc..
Maybe he's describing these concepts at a high level and from the perspective of a software developer that is trying to plan how they will implement their product (trying to decide on which technology to use) . But this probably should have been titled REST API and SDKs because not every API follow the REST style, which was described in this video.
Not according to most authorities on the internet. POST to create a resource, PUT to completely replace a resource, and PATCH to partially replace portions of a resource.
The only thing we can agree on about the correct meaning of HTTP methods is that there is no universal agreement. If you think the meanings are consistent and coherent, you haven't thought about HTTP methods deeply enough.
This explains web or rest api, api as a concept is something else
Yeah ByteByteGo are extremely inconsistent. They often make absolutely garbage videos that explain things wrong, use incorrect concepts... It's so weird because they also make extremely good ones
Yeah this was a confusing video
Yeah, REST is a small part of the API universe.
Yeah they made it seem like an api was a universal thing and they all look alike.
This is why any developer that has experience outside of web dev just bites their tongue at the cringe in interviews conducted by “tech leads” who’ve only lived in one universe like web dev.
I've always seen it like this:
An API is to be consumed. An SDK is software in your language of choice that consumes the API in question, but in a particular, prebuilt way. The SDK is usually built by the company who owns the API. But it is only one of many ways. You don't need the SDK, you could build your own software to call the API in question, but you do need the API. Nevertheless, even if you could build your own software it is worth installing the SDK simply not to reinvent the wheel.
For a succinct 5 minute video you cover the majority of the truth here. Well done. People get nit-picky and want to point out what you didn't cover. Perhaps at the end of your videos suggest resources like online lectures or good books on the subject. Well done mate!
Api doesnt necessarly means its a web service (endpoints) it could be any ressource its could be modules and libraries like the sqrt math library python or hardware
Windows api too but I think he showed example of api
This is an amazing video that covers a lot of the basics. 👍
Wow! Useful topic
Your videos are always great! 🤙
Thank you ❤
thank you for this!
This is great explanation.
Great video! Can I know what software you used to make this beautiful video?
Thx ❤
SDK might contain built-in APIs
Hello admin can explain portcontainer architecture and to use it in docker
SDKs often handle the security part as well..
Dude. Not everything is a webapp.
I guess titles of video should begin with web . Its not meant for ppl that builds firmwares or low level programming. He clearly says modern programming and nowadays modern softwares are almost all web based, react native for phone app, electron for desktop app etc..
great!
API and SDK are complete different concepts.
Maybe he's describing these concepts at a high level and from the perspective of a software developer that is trying to plan how they will implement their product (trying to decide on which technology to use) . But this probably should have been titled REST API and SDKs because not every API follow the REST style, which was described in this video.
This video is AMAZING! Super simple. Love it, please keep them coming!
thats the old google mpas logo... good times.
❤❤❤❤🎉
This video created more confusion . 😂
Saying "OAuth" and showing the Auth0 logo is terribly confusing for people who don't know auth
Isn't PUT to create and PATCH to update things?
Not according to most authorities on the internet. POST to create a resource, PUT to completely replace a resource, and PATCH to partially replace portions of a resource.
The one that is meant for creating is
POST
The only thing we can agree on about the correct meaning of HTTP methods is that there is no universal agreement.
If you think the meanings are consistent and coherent, you haven't thought about HTTP methods deeply enough.