Another fun example is a linux display server (like X11): it's a program that has a screen it can display things on and a mouse and keyboard it can read from; graphical programs then connect to it as clients via something like dbus to ask for those inputs and tell it what to display.
X11 clients usually connect via abstract unix sockets. Also if you run graphical programs on a rented 'server' over ssh, your desktop is the server here in X11 context. This is a typical master-slave setting where xorg-server is the master.
DBus is not involved in Xorg/X11. A client (eg. a window manager, a compositor, a status bar, or just a regular application) connects to the X11 socket/port and talks with the server (Xorg) using the X11 protocol, usually using either Xlib or XCB to abstract the communication. The protocol also facilitates IPC, using Window properties and other things, specified in ICCCM (overall communication), EWMH (communication between normal apps and the WM), or various other freedesktop specs, for stuff like clipboard, systray, embedding windows in each other, and more.
Simplifying computer terms in easy explanations is something I am always up for. It's too easy to confuse people and make them lose interest (probably part of the reason why hubs, MODEMs and WiFi access points are combo devices nowadays). I'd welcome more videos like this.
I had quite a big struggle understanding what is a protocol and how are packets built. "Language that computers communicate" did not cut it for me. If you want to make a similar video I would love to watch a deep dive on this topic.
Just a serious question: “isn’t this taught in college anymore? A protocol is just a serious of steps that unify a process, so that there’s the same way of doing something and interoperability is guaranteed.” Creating a packet is of course specific to CS, and depends on where ik the OSI model you are implementing it. A TCP packet is different from for example a abstract HTTP protocol is an application protocol. For example IP is a network protocol and each are implemented differently. Network protocols themselves lay on top of data link protocols (basically describing how the data needs to be send into a network card, you have to Ethernet network cards, but also token ring or these days your DSL modem. Your NIC driver basically translates your network protocol (IP) into a data link protocol. And that hardware communicates again with a physical agreed upon protocol. So how to implement it really depends on where you are in your OSI stack. It can be as trivial as just reading whole lines or even single chats via stdin and stdout. To ask complex as actually toggling physical bit on and off in a set time. On my channel I have a video called “Fixing climate change the hacker way”. I reverse engineer a weather station protocol and spoof it using just and Arduino that toggled a single hit that enabled disables a little transmitter. That is the lowest level of protocol execution- just toggling single but on and off.
protocol is EXACTLY that .. what the word mean. You made protocol by that you made up some rules how to write some information or do some actions. For example lets say "You need to knock on the door three times, then I shoud 'come in!' and then you may come in" and by agreeing on that we created a protocol, by those rules if you knock only two times I wont shout 'come in!' and you cant go in. Of course in real life you may just come in but then it's not by the protocol and unexpected things may happen .. lets update the protocol "If you just go in without knocking, I kick you in the butt" :D
how'd this get in my recommended? EDIT: I was just surprised an unlisted video got in my recommendation when it had only 2 views. I’m already subscribed and I watch all of LiveOverflow’s videos.
Thank You! I have been a programmer for a few years now and these "basic" terms often have so many subtle complexities that videos like this help a lot. Please keep making videos like this!
You also used the term service. If you want to tie that into the explanation, I would define it as this: A *_server_* is a *_program/application_* that *_provides_* a *_service_* by sending a *_response_* to a *_client_* application that sent a *_request_* , so that the client can then *_consume_* this response. What the request and the response contain depend on the service that the server provides. This application can be called a server, but it is also often called a service. The hardware can be called a server, but is usually not called a service, except in the context of Infrastructure As A Service (IAAS), where your hardware is managed for you by a 3rd party, e.g. an (other) company (like a mincraft server host) or even a different department within the same company (which makes it possible for a development team to run their program somewhere in the company, without having to manage those computers themselves). Here the service refers to the management and availability of those computers, not necessarily to the computers themselves. The term service is also used within the code of a program itself. For instance, some piece of code might need access to a database. To do this, it can call a service (another piece of code within the same program) that handles the database access. In this context you might also see the terms *_manager_* or *_repository_*
Stop giving the rent owners more reason to ask for rent. Don't study his definition, kids. Not all of are Peter Parker, most of us are the tubbies from Wall-E.
@@rikschaaf Peter Parker pays his rent by means of even self exploitation. When one says they are providing a service, this entails monetary compensation. There are businesses that thrive on providing you a server and some dirty cpanel experience in exchange for premium lunch money. These services should not exist in the modern world as we are moving to web3 and the metaverse with further p2p and ipfs resources. As tubbies, we the low grade consumer, can do nothing about this "democratization" that happens without our participation. Hope this explains it.
2:31 Exactly! As an ICT student, first thing i have been taught is "throw away the mindset that a server is anything special" being a "server" can be temporary, for example a client working as a minecraft server, there are purpose-built machines for it, but a server is just any host that shares their resources or service. the "status" of any host can be both client and server depending on what it is doing at the particular time
Funny that I literally asked a professor this after class yesterday, his answer was "pretty much everything can be a server". I guess the confusion arises from the fact that it doesn't only refer to specific types of computers/software but to much more. Thank you for the deep dive, really appreciate it :)
This video is perfect for someone like me: the one who has used computer for more than half of their life but still get confused with all the terms. Thank you so much!
Really enjoyed this kind of video! Please keep up the series. The gradual change from solid basic information to more technical details was really informative!
This video is great. I used to be confused about the term as well but the more I interact with it the more I learn that so many things in the "tech sphere" are things that I already knew and interact with daily and have some understanding of, just with slightly more different descriptions of their purpose or implementations. I kind of hate that computers are seen as this mysterious black box when so many aspects of them are just simple concepts we already know, but they're implemented in an unfamiliar way. I like to think about questions like this and answer them in a way that's more relatable to the general human experience, and when I was clicking on the video I was thinking to myself how I would answer the question, landing on the same initial answer as you, like a waiter/server at a restaurant that takes requests and provides a service or response in the form of food.
Thank you for this video. I felt how you felt when you were 17 years old. Currently learning configuration management and I was experiencing some sort of mental block then i decided to break down terms. Especially the server / web server that i thought I already know the meaning of. I truly appreciate this video, your 17 year old self and this lady is happy.
"There is no cloud, there is only someone's else computer ". I remember back in the day when we were using one PC to be a server. Today you can do amazing stuff with things like raspberry pi and really understand that server is essentially a computer.
As a long time windows and Linux administrator, I want to tell you that your video is awesome! 👍 Good explanations, even better illustrations and best of all, personally, metaphors.
The best thing i like about this video is that it starts as beginner and then impressively level up after 50% duration for most advanced concept too. 👏
I'm a backend developer, and a good one at that. My job is to write web servers all day. Yet, most of the contents of this video were either new to me or I have just learned implicitly through experience. Very nice video!
In order to do better data security with people I have to explain client/server computing approaches. It is always good to have a very simple and effective introduction to the topic. It looks like the video is promising in that regard. I'll let everyone know how it goes once I use it!
Awesome video! Doing the videos that you wish you had when you were younger makes for a really interesting and usefull format. It is also motivating to see that you once also had essential misconceptions about certain "basic" topics and that there is nothing wrong with that. The worst thing that one can do is to not ask that "silly" question and remain ignorant. Keep it up!
finally a good explanation about servers, I had that question for a really long time, mostly because of all the ways people explain stuff, everyone explains it differently, and it becomes extremely difficult to understand what is what and which is which. Thanks for the video, and keep up the good videos they definitely help a lot.
Simple but necessary and useful video, when I was teen everyone who was older than me speaking about server, and I was trying figure out what the hell they talking about.
I also asked myself the same question. My answer (super quickly): A server is a role that a program on a computer plays. It serves certain forms of data that the client is requesting. A client is also a role that a program on a computer plays. Aaannd now I'll watch the video :D
I use server in different ways: 1. A server is the program running on the hardware 2. The server is the hardware running a software 3. The server is hardware combined with software which main goal is to serve data (a "linux server", a linux computer set up for the purpose of serving data) When I say I have a server at home, most of the time I mean the last. The last definition also allows me to say I have multiple servers, which can be interpreted as either one softwares running on one system, many softwares running on one system or many softwares running on many hardwares depending on the context.
I am struggling every day with trying to understand the things related to programming I am giving up easily, such materials bringing back my willingness to try one more time. Thank you for excellent explanation.
To be very honest, I had the same question in my mind. The main question I had was why we call a computer a server when it is just another computer? Now I got the answer. Thank you.
I loved this video. I sort of followed along and was impressed with your reverse engineering. My computer knowledge is very rudimentary starting when I was an undergrad at U.C.S.D.! Back then we used a Burroughs B6700 machine which took up the first floor of Building A on Muir campus. I still remember (note I did not say fondly) punching cards as I built a compiler for my computer class. I learned a lesson from a fellow dorm student who figured out how to get control and breach the system. A “clever” line of text inserted onto all printout headers quickly lead the department to shut B6700 down until the student was apprehended and interrogated. This forced the implementation of security advances and one deserved expulsion. All his fellow students can now explain how that one was done since 50 years is far past the statute of limitations. Since you are familiar with Giesel you may be surprised that back in the first 10 years of UCSD it was known as “Central Library” which had no computing ability. All computation was there in building A at the “liberal arts college” Muir College. I suggest changing the coding a bit and boost the census numbers by multiplying the area counted by a factor of 10 or 100. Maybe you get more money for the English department if the Romance Novel stacks suddenly show 300 or 3000 visits instead of a daily census of 3!
This is a GREAT introduction to how it works, you left quite an awesome bit of 'your own research needed here' but explained amazing for someone coming into the world of IT!
I'm in 3rd yr UG, thought this would not help me as I'm too confused and too "already" introduced to the topic. But damnn this was helpful. The crux, "server is just a program" ! thnx
This video approves that every though guy, who seems absolute expert is just an ordinary man with simple questions. But everyone can reach high excellence if he dont give exploring. I admire your content! Good Luck, Liveoverflow!
Thx for the vid. When I was a youngster I also was a bit confused about what exactly is a server. Within Discord one also creates servers. One more example of using the word server ..
I think it may also be useful to note a usage of sockets that doesn’t fit the behavior of “server client”, showing that the two are very different. Otherwise amazing video, and I can’t wait to see more.
I really like the video format and the idea behind it therefore i would enjoy to see you explain more common words/concepts :) (like networking. Which was one of the main things i always wanted to know how it works until i had it in Uni)
My 15 years old self would have thanked you. There was thenewboston at the time but not many people were making videos about client server architecture.
thanks alot for this video, this genuinly helped me (an almost 27 year old) out alot with naming my programs, now i can finally standardize my program namingscemes a bit more.
To avoid the confusion between the computer and the programs running on a server, I tend to define "server" as the computer itself, and then the programs running on there as "service". Now, in my case it gets even more abstract though. That's because I use my workstations as servers as well. The environments are well isolated using containerization software, but now all of a sudden you have a box doing double duty. It's both a workstation and a server at the same time. Back when I took a networking course, I actually had an argument with one of my teachers about this. I defined it as both, but she refused to acknowledge that a laptop running nginx, Postfix+Dovecot and whatnot would be able to be called a server. It appeared that she still lived in that world where all servers had to be measured in rack unit sizes. To me though, anything that has a processor, memory and storage of some kind in it, is all the same. It's an overblown calculator, i.e. a computer. This video really nails that part, throwing phones, game consoles, desktops and servers all in the same bucket. And I think that's okay. You could turn a phone into a Linux server if you wanted to. Not that you should, but with e.g. PostmarketOS you totally could. And you could run a service on it, and reverse proxy it to the internet. You'd be an absolute madman for doing it, but dammit you'd have my respect.
Oh man, I dont understand it %100, but this helps a lot. I have ADHD and had a very hard time in high school. Trying to study pentesting on my own and having a really hard time understanding basic things like this. Its extremly slow and frustrating. I wish I could afford to go to collage but I already tried and messed that up when I was using drugs and was to depressed to stop. I got AID for coursea but that is kinda frustrating as well because I am not able to ask a person anything when I'm just totally lost. So thanks a bunch man! This helps a bunch to try to start to figure this simple problem out I just cant seem to grasp.
you're really amazing, the video is quality made and the explanations are so understandable. thank you for helping the world learn and making it so enjoyable at the same time!
this video was super amazing video ideas next:- on computer graphics also videos on how memory works, cpu works, computer architecture and organizations
Before my studies I had the same thoughts as you! What is actually a server? I thought it's something special. But actually it's just a computer. And even my normal gaming computer can be a server.
17:26 "Was this video a waste of time?" Brother, no video from you is a waste of time. I'm beyond grateful for the content you have provided for free for masses!
It's not just for your 17y/o your/ourself, it's very useful, I guess even for an experienced professional too. Like your "The Same Origin Policy" video, re-understanding the raw/old basics is really helpful because it helps to re-think and understand the roots of more complex problems.
Well explained, I like this kind of videos, and I think we can simplify it as an Input and Output, no matter if there's an imperative or functional program, there are actions after any request from both sides. 👍
As a 17 year old just getting into computer science I think you explained this amazingly! I feel quite stupid because my dad is a senior network architect with a large telecom company who literally holds several patents in the field and he has tried to teach me about computers since I could hold a mouse but I always ignored it because I wanted to go into the medical field. I’m cringing at how many massive multi million dollar data centers he has taken me to and tried to teach me about them while I just rolled my eyes and read whatever Harry Potter book XD
I don't normally give feedback on end-video questions since it's time consuming and I don't think it will be read, or the authors have time to respond back. But somehow I feel that this time is different, since it looks like you are sincerely asking for that. So, the reason I visit this video because I want to learn more on the technical side on making a server. Like real code. The problem I get is that I'm unable to run PHP code even though I have the HTTP-server service running in the terminal. I don't expect this video to explain why my setup doesn't work; I just need it to give me a full, code-oriented picture on how server works. This video does not satisfy me, but it definitely help me clear out many nuances in the terms. Would I recommend my-before-watching-it-self watching it? Most likely yes, but I will definitely recommend with other videos that get directly to the code.
Another fun example is a linux display server (like X11): it's a program that has a screen it can display things on and a mouse and keyboard it can read from; graphical programs then connect to it as clients via something like dbus to ask for those inputs and tell it what to display.
X11 clients usually connect via abstract unix sockets.
Also if you run graphical programs on a rented 'server' over ssh, your desktop is the server here in X11 context. This is a typical master-slave setting where xorg-server is the master.
DBus is not involved in Xorg/X11. A client (eg. a window manager, a compositor, a status bar, or just a regular application) connects to the X11 socket/port and talks with the server (Xorg) using the X11 protocol, usually using either Xlib or XCB to abstract the communication. The protocol also facilitates IPC, using Window properties and other things, specified in ICCCM (overall communication), EWMH (communication between normal apps and the WM), or various other freedesktop specs, for stuff like clipboard, systray, embedding windows in each other, and more.
Thank you!
I was always confused by this.
x11 is the old stuff, wayland is the new
Simplifying computer terms in easy explanations is something I am always up for.
It's too easy to confuse people and make them lose interest (probably part of the reason why hubs, MODEMs and WiFi access points are combo devices nowadays).
I'd welcome more videos like this.
Routers for the win! haha.
why would i want 3 devices in 1 if i can pay more money for power bill when each one has its own power supply ...
I had quite a big struggle understanding what is a protocol and how are packets built. "Language that computers communicate" did not cut it for me. If you want to make a similar video I would love to watch a deep dive on this topic.
Btw, he made the video: ua-cam.com/video/d-zn-wv4Di8/v-deo.html
@@hb20007 Yeah I saw! Nice to know that viewer input is being considered.
Just a serious question: “isn’t this taught in college anymore? A protocol is just a serious of steps that unify a process, so that there’s the same way of doing something and interoperability is guaranteed.” Creating a packet is of course specific to CS, and depends on where ik the OSI model you are implementing it.
A TCP packet is different from for example a abstract HTTP protocol is an application protocol. For example IP is a network protocol and each are implemented differently. Network protocols themselves lay on top of data link protocols (basically describing how the data needs to be send into a network card, you have to Ethernet network cards, but also token ring or these days your DSL modem. Your NIC driver basically translates your network protocol (IP) into a data link protocol. And that hardware communicates again with a physical agreed upon protocol.
So how to implement it really depends on where you are in your OSI stack. It can be as trivial as just reading whole lines or even single chats via stdin and stdout. To ask complex as actually toggling physical bit on and off in a set time. On my channel I have a video called “Fixing climate change the hacker way”.
I reverse engineer a weather station protocol and spoof it using just and Arduino that toggled a single hit that enabled disables a little transmitter.
That is the lowest level of protocol execution- just toggling single but on and off.
protocol is EXACTLY that .. what the word mean. You made protocol by that you made up some rules how to write some information or do some actions.
For example lets say "You need to knock on the door three times, then I shoud 'come in!' and then you may come in" and by agreeing on that we created a protocol, by those rules if you knock only two times I wont shout 'come in!' and you cant go in.
Of course in real life you may just come in but then it's not by the protocol and unexpected things may happen .. lets update the protocol "If you just go in without knocking, I kick you in the butt" :D
how'd this get in my recommended? EDIT: I was just surprised an unlisted video got in my recommendation when it had only 2 views. I’m already subscribed and I watch all of LiveOverflow’s videos.
It is great content. That's why.
Why not?
This guy does hacking into minecarft and understanding how hacks work videos
Subscribe to him he's damn good, i learnt so much stuff from him back then
Quality
Thank You! I have been a programmer for a few years now and these "basic" terms often have so many subtle complexities that videos like this help a lot. Please keep making videos like this!
You also used the term service. If you want to tie that into the explanation, I would define it as this:
A *_server_* is a *_program/application_* that *_provides_* a *_service_* by sending a *_response_* to a *_client_* application that sent a *_request_* , so that the client can then *_consume_* this response. What the request and the response contain depend on the service that the server provides.
This application can be called a server, but it is also often called a service.
The hardware can be called a server, but is usually not called a service, except in the context of Infrastructure As A Service (IAAS), where your hardware is managed for you by a 3rd party, e.g. an (other) company (like a mincraft server host) or even a different department within the same company (which makes it possible for a development team to run their program somewhere in the company, without having to manage those computers themselves). Here the service refers to the management and availability of those computers, not necessarily to the computers themselves.
The term service is also used within the code of a program itself. For instance, some piece of code might need access to a database. To do this, it can call a service (another piece of code within the same program) that handles the database access. In this context you might also see the terms *_manager_* or *_repository_*
Stop giving the rent owners more reason to ask for rent. Don't study his definition, kids. Not all of are Peter Parker, most of us are the tubbies from Wall-E.
@@NickKartha wha? There's probably some comedy in here, but I am completely missing what you even mean...
@@rikschaaf Peter Parker pays his rent by means of even self exploitation. When one says they are providing a service, this entails monetary compensation. There are businesses that thrive on providing you a server and some dirty cpanel experience in exchange for premium lunch money. These services should not exist in the modern world as we are moving to web3 and the metaverse with further p2p and ipfs resources. As tubbies, we the low grade consumer, can do nothing about this "democratization" that happens without our participation. Hope this explains it.
i agree
@@NickKartha you... don't want servers...
and you think meta of all people will stop that?
2:31
Exactly! As an ICT student, first thing i have been taught is "throw away the mindset that a server is anything special"
being a "server" can be temporary, for example a client working as a minecraft server, there are purpose-built machines for it, but a server is just any host that
shares their resources or service.
the "status" of any host can be both client and server depending on what it is doing at the particular time
Funny that I literally asked a professor this after class yesterday, his answer was "pretty much everything can be a server". I guess the confusion arises from the fact that it doesn't only refer to specific types of computers/software but to much more. Thank you for the deep dive, really appreciate it :)
This video is perfect for someone like me: the one who has used computer for more than half of their life but still get confused with all the terms. Thank you so much!
yk what the first part where u say to think of a server like a restaurant waiter actually helped alot
The videos you make for your seventeen-year-old self are making a fourty-year-old man (me) very happy! Thank you so much!
Really enjoyed this kind of video! Please keep up the series. The gradual change from solid basic information to more technical details was really informative!
This video is great. I used to be confused about the term as well but the more I interact with it the more I learn that so many things in the "tech sphere" are things that I already knew and interact with daily and have some understanding of, just with slightly more different descriptions of their purpose or implementations. I kind of hate that computers are seen as this mysterious black box when so many aspects of them are just simple concepts we already know, but they're implemented in an unfamiliar way. I like to think about questions like this and answer them in a way that's more relatable to the general human experience, and when I was clicking on the video I was thinking to myself how I would answer the question, landing on the same initial answer as you, like a waiter/server at a restaurant that takes requests and provides a service or response in the form of food.
What a fantastic deep dive, thank you!
Thank you for this video. I felt how you felt when you were 17 years old. Currently learning configuration management and I was experiencing some sort of mental block then i decided to break down terms. Especially the server / web server that i thought I already know the meaning of.
I truly appreciate this video, your 17 year old self and this lady is happy.
"There is no cloud, there is only someone's else computer ".
I remember back in the day when we were using one PC to be a server.
Today you can do amazing stuff with things like raspberry pi and really understand that server is essentially a computer.
As a long time windows and Linux administrator, I want to tell you that your video is awesome! 👍 Good explanations, even better illustrations and best of all, personally, metaphors.
The best thing i like about this video is that it starts as beginner and then impressively level up after 50% duration for most advanced concept too. 👏
With 19 I got really confused what a server is too. So thank you for uploading this to help others that are new in this field!
I'm a backend developer, and a good one at that. My job is to write web servers all day. Yet, most of the contents of this video were either new to me or I have just learned implicitly through experience. Very nice video!
In order to do better data security with people I have to explain client/server computing approaches. It is always good to have a very simple and effective introduction to the topic. It looks like the video is promising in that regard. I'll let everyone know how it goes once I use it!
How did it go?
This is awesome. I can´t tell you how often I catch myself not being able to truly explain the most simple stuff in IT after using it for +10years.
Awesome video! Doing the videos that you wish you had when you were younger makes for a really interesting and usefull format. It is also motivating to see that you once also had essential misconceptions about certain "basic" topics and that there is nothing wrong with that. The worst thing that one can do is to not ask that "silly" question and remain ignorant. Keep it up!
This video was really helpful! There needs to be more explanations like this that people with less experience are able to understand.
finally a good explanation about servers, I had that question for a really long time, mostly because of all the ways people explain stuff, everyone explains it differently, and it becomes extremely difficult to understand what is what and which is which.
Thanks for the video, and keep up the good videos they definitely help a lot.
Simple but necessary and useful video, when I was teen everyone who was older than me speaking about server, and I was trying figure out what the hell they talking about.
I also asked myself the same question. My answer (super quickly): A server is a role that a program on a computer plays. It serves certain forms of data that the client is requesting. A client is also a role that a program on a computer plays. Aaannd now I'll watch the video :D
I use server in different ways:
1. A server is the program running on the hardware
2. The server is the hardware running a software
3. The server is hardware combined with software which main goal is to serve data (a "linux server", a linux computer set up for the purpose of serving data)
When I say I have a server at home, most of the time I mean the last. The last definition also allows me to say I have multiple servers, which can be interpreted as either one softwares running on one system, many softwares running on one system or many softwares running on many hardwares depending on the context.
I am struggling every day with trying to understand the things related to programming I am giving up easily, such materials bringing back my willingness to try one more time. Thank you for excellent explanation.
this video is SO GOOD. I will send it to all my friends who begin to learn Computer science!
so humble, bless you
To be very honest, I had the same question in my mind. The main question I had was why we call a computer a server when it is just another computer? Now I got the answer. Thank you.
I loved this video. I sort of followed along and was impressed with your reverse engineering. My computer knowledge is very rudimentary starting when I was an undergrad at U.C.S.D.! Back then we used a Burroughs B6700 machine which took up the first floor of Building A on Muir campus. I still remember (note I did not say fondly) punching cards as I built a compiler for my computer class.
I learned a lesson from a fellow dorm student who figured out how to get control and breach the system. A “clever” line of text inserted onto all printout headers quickly lead the department to shut B6700 down until the student was apprehended and interrogated.
This forced the implementation of security advances and one deserved expulsion. All his fellow students can now explain how that one was done since 50 years is far past the statute of limitations.
Since you are familiar with Giesel you may be surprised that back in the first 10 years of UCSD it was known as “Central Library” which had no computing ability. All computation was there in building A at the “liberal arts college” Muir College.
I suggest changing the coding a bit and boost the census numbers by multiplying the area counted by a factor of 10 or 100. Maybe you get more money for the English department if the Romance Novel stacks suddenly show 300 or 3000 visits instead of a daily census of 3!
This is a GREAT introduction to how it works, you left quite an awesome bit of 'your own research needed here' but explained amazing for someone coming into the world of IT!
I'm in 3rd yr UG, thought this would not help me as I'm too confused and too "already" introduced to the topic. But damnn this was helpful. The crux, "server is just a program" ! thnx
Really good work at covering this topic from different angles!
Absolutely love this video. I will no longer feel intimidated when I here the word server in the office.
This video approves that every though guy, who seems absolute expert is just an ordinary man with simple questions. But everyone can reach high excellence if he dont give exploring.
I admire your content!
Good Luck, Liveoverflow!
Thx for the vid. When I was a youngster I also was a bit confused about what exactly is a server.
Within Discord one also creates servers. One more example of using the word server ..
I think it may also be useful to note a usage of sockets that doesn’t fit the behavior of “server client”, showing that the two are very different. Otherwise amazing video, and I can’t wait to see more.
Best video for server explanation on this planet. 🔥
I really like the video format and the idea behind it therefore i would enjoy to see you explain more common words/concepts :)
(like networking. Which was one of the main things i always wanted to know how it works until i had it in Uni)
Thank you fore the video. I have a long journey. I would not even consider myself the 17yr old version of you. Well done!
Nice explanation. I also had this question over server being referred to both program and machine. So this clears it up. Thanx
This was an awesome video! Proof that even the more simpler subject areas can be just as enlightening. Thanks for this!
My 15 years old self would have thanked you. There was thenewboston at the time but not many people were making videos about client server architecture.
Great Explanation! I also didn't know what a 'server' was for a long time. It's just computer, that's beefed up to stay online 24/7.
You've answered my question and I'm aware of the term server . Thanks much.
This video was not a waste of time. Honestly it would be great to get more videos on basic Computer Science topics.
thanks alot for this video, this genuinly helped me (an almost 27 year old) out alot with naming my programs, now i can finally standardize my program namingscemes a bit more.
To avoid the confusion between the computer and the programs running on a server, I tend to define "server" as the computer itself, and then the programs running on there as "service". Now, in my case it gets even more abstract though. That's because I use my workstations as servers as well. The environments are well isolated using containerization software, but now all of a sudden you have a box doing double duty. It's both a workstation and a server at the same time. Back when I took a networking course, I actually had an argument with one of my teachers about this. I defined it as both, but she refused to acknowledge that a laptop running nginx, Postfix+Dovecot and whatnot would be able to be called a server. It appeared that she still lived in that world where all servers had to be measured in rack unit sizes. To me though, anything that has a processor, memory and storage of some kind in it, is all the same. It's an overblown calculator, i.e. a computer. This video really nails that part, throwing phones, game consoles, desktops and servers all in the same bucket. And I think that's okay. You could turn a phone into a Linux server if you wanted to. Not that you should, but with e.g. PostmarketOS you totally could. And you could run a service on it, and reverse proxy it to the internet. You'd be an absolute madman for doing it, but dammit you'd have my respect.
Your comment makes me wanna buy a bunch of cheap phones and run them as a server cluster similar to a PiStack 😁
Thank you for this, I was struggling to understand servers and clients definitions.
man, you're really good at explaining things. got a little too confusing for me personally after the socket thing, but that's me.
Man.. I love this guy, he explains in a better way
Oh man, I dont understand it %100, but this helps a lot. I have ADHD and had a very hard time in high school. Trying to study pentesting on my own and having a really hard time understanding basic things like this. Its extremly slow and frustrating. I wish I could afford to go to collage but I already tried and messed that up when I was using drugs and was to depressed to stop. I got AID for coursea but that is kinda frustrating as well because I am not able to ask a person anything when I'm just totally lost. So thanks a bunch man! This helps a bunch to try to start to figure this simple problem out I just cant seem to grasp.
you're really amazing, the video is quality made and the explanations are so understandable.
thank you for helping the world learn and making it so enjoyable at the same time!
You are a great teacher.
Great Job. I'm new to all this, and you made it easy for me to understand.
this video was super amazing
video ideas next:-
on computer graphics
also videos on how memory works, cpu works, computer architecture and organizations
so true, in a class room they made it so hard. if you do it like this I understand. thanks man.
this is beautiful...humbly thank you.
Before my studies I had the same thoughts as you! What is actually a server? I thought it's something special. But actually it's just a computer. And even my normal gaming computer can be a server.
More of this series please!
This is so great! I love the level of detail you go into, thanks a lot!
17:26 "Was this video a waste of time?"
Brother, no video from you is a waste of time.
I'm beyond grateful for the content you have provided for free for masses!
Great video, I'm a student experiencing the same question in my mind all the time. Thank you for the explanation!
Never imagined there can be a 17 minute video explaining what a server is😮
My younger self would have definitely benefitted from such a great explanation!
The best explanation that I have heard ever about server:)
Wow! Just when I started diving into networking and net security, too! Thank you, you've taught me so much.
this was very good. thank you for making it more clear for me
Incredible explanation, thank you very much! Really needed this
Thanks this is awesome!
LiveOverflow is basically just IT dad now. That's a good thing.
It's not just for your 17y/o your/ourself, it's very useful, I guess even for an experienced professional too. Like your "The Same Origin Policy" video, re-understanding the raw/old basics is really helpful because it helps to re-think and understand the roots of more complex problems.
This is a fantastic video! Thank you soo much 🙏
Well explained, I like this kind of videos, and I think we can simplify it as an Input and Output, no matter if there's an imperative or functional program, there are actions after any request from both sides. 👍
Continue these types of videos... its very helpful
It toke me a long time to understand its concept as well, thanks for validating me
You have an incredible approach of explaining details. Glad you made this ❤
As a 17 year old just getting into computer science I think you explained this amazingly!
I feel quite stupid because my dad is a senior network architect with a large telecom company who literally holds several patents in the field and he has tried to teach me about computers since I could hold a mouse but I always ignored it because I wanted to go into the medical field. I’m cringing at how many massive multi million dollar data centers he has taken me to and tried to teach me about them while I just rolled my eyes and read whatever Harry Potter book XD
I would have paid money for this a year ago when I was deeply confused by the term. Thank you!
Incredibly done brother. Thanks a lot for sharing!
Nice explanation! When I was 17, TCP was still being drafted.
Have had this question on my mind for a while, this is perfect ❤️
These videos are absolutely brilliant. Cheers for all of this really great information.
This is extremely relevant to my studies, thanks!
Fabulous, thanks for sharing!
I don't normally give feedback on end-video questions since it's time consuming and I don't think it will be read, or the authors have time to respond back. But somehow I feel that this time is different, since it looks like you are sincerely asking for that.
So, the reason I visit this video because I want to learn more on the technical side on making a server. Like real code. The problem I get is that I'm unable to run PHP code even though I have the HTTP-server service running in the terminal. I don't expect this video to explain why my setup doesn't work; I just need it to give me a full, code-oriented picture on how server works. This video does not satisfy me, but it definitely help me clear out many nuances in the terms.
Would I recommend my-before-watching-it-self watching it? Most likely yes, but I will definitely recommend with other videos that get directly to the code.
Thank you master, you're really talented. Hope to see more of this deepdive series
I love your intro music sir
I often find myself ruminating over the linguistics in tech spaces. It's both engaging and infuriating, especially when you're first learning.
I liked this video, I went back in time….. really nice, remember those basic but essential concepts are always useful 🎉
Learned the ins and outs of client and server roles and TCP/IP during my Bachelor's degree thesis.
Wish I had this video and its insight before :)
Thanks for the video. I know most of it already or had a good concept of it but still was helpful and definitely learned something
This was super helpful thanks so much!!! ❤️❤️
Very good video!!! Finally understand it :) 8:58 the right guy was you?
This video really helps! Many thanks!
Last part was cool. Good video
this is such great video, thank you so much.