Lot of potential. If I could make a suggestion though, try making the video more closely related to the topic, encoding has far less to do with binary than it does with general data formatting. Almost all types of data formatting is just encoding and for some people they need a more abstracted view of what encoding is to understand it. Maybe include additional demonstrations or examples such as, how utf-8 gets encoded to base64 when you're searching in the browser which then get encoded to binary before being sent as packets. It might help the binary portion make more sense if people can relate something they know down to the binary level rather than starting there.
'Encoding has less to do with binary than it does with general data formatting.' I totally agree, and that was the point I was trying to get across by using 'ruleset' as almost a synonym for encoding. There are 5 videos (currently planned) in this particular little 'Data' series, the last of which is compression, in which I explicitly call out that compression can be thought of as an additional encoding layer. The implication I'm *hoping* to put across is that 'wait, this is all just different expressions of the same concept'. Calling this particular video the 'encodings' video is perhaps a bit of a misnomer, because the only video in the 'module' which covers a topic which can't be thought of as a *sort* of encoding (even binary and number systems can fall under that umbrella IMO), is hashing which is covered tomorrow. Otherwise, it's all 'at a high level, how do computers interpret and work with data'. The main reason I wanted to start with binary is mentioned in that video; it's easy for anyone to conceptualize, one they understand what binary is, that binary is the natural number system for computers because a basic electronic switch is high or low, on or off, and from that we can build everything else.
Wow that's actually a really great video, love the way u're explaining things, that's clear and rapid ! I'm learning coding and it's been a while that i'm thinking about the thing of making a png file only by coding, could you please make videos about the specificities of each file type, that could be a great topic i think :!
Glad you found it helpful! I definitely plan on going more in depth on specific formats, including PNG, JPEG, and exploring h264, h265, etc for video. There are super interesting computer science and mathematical concepts to explore in doing so. I can't say exactly _when_ I'll get to that stuff though-there's a lot I want to cover.
Haha, I'm happy I could surprise you. It's a new channel; everyone starts at zero. Apparently TH-cam has decided to bless this particular video with recommendations, so I can't complain.
Hey man, wish you the best of luck. I also recently started my channel and finally the last video got picked up by the algorithm. Surely for you it’s gonna happen as well :)
@ it certainly was a lesson for me. Worked really hard on it for weeks (next to my full time job) and it got less than 1k views for the initial period. No more large projects until I have a bigger following 😂
bit confused about the title, also I haven't watched further than 7 seconds, but isn't decoding going from numbers to videos and not the other way around?
Fair question! The answer is yes, but 'decoding' is just a verb, while 'encoding' is a verb and a noun. The process of writing video data to a file with a defined format to disk is 'encoding', and the process of reading said file, and interpreting it so it can be turned into pixels on a screen is 'decoding'. What you're missing is 'an encoding' is the ruleset which defines how to do both actions.
Little endian is not faster than big endian, that was only true for a very specific case that intel faced with one line of chips. Instead of being inconsistent with their next chips they decided to just stick to little endian
There are actual advantages to little endian ordering. For example, downcasting an integer on a little endian machine is a noop; you don't even need to calculate an offset. Similarly, addition and subtraction, which work smallest byte to largest byte, are simpler when I[0] is the smallest byte. There are advantages to big endianness for certain tasks too. The difference is usually very small, so when choosing an endianness for a general purpose computer, you go with the endianness which has the minor advantage for the extremely common operations (eg: downcasting, addition). Virtually every modern, widely used computer is little endian; ARM and Risc-V allow for big-endianness, but it's rarely used.
I really like the minimalistic, no bs, direct but clear approach. I hope you keep going and im hopefully the algorithm will pick you up soon
Glad you like the style! More is definitely on the way.
found a gem. subscribed.
Lot of potential. If I could make a suggestion though, try making the video more closely related to the topic, encoding has far less to do with binary than it does with general data formatting. Almost all types of data formatting is just encoding and for some people they need a more abstracted view of what encoding is to understand it. Maybe include additional demonstrations or examples such as, how utf-8 gets encoded to base64 when you're searching in the browser which then get encoded to binary before being sent as packets. It might help the binary portion make more sense if people can relate something they know down to the binary level rather than starting there.
'Encoding has less to do with binary than it does with general data formatting.'
I totally agree, and that was the point I was trying to get across by using 'ruleset' as almost a synonym for encoding.
There are 5 videos (currently planned) in this particular little 'Data' series, the last of which is compression, in which I explicitly call out that compression can be thought of as an additional encoding layer. The implication I'm *hoping* to put across is that 'wait, this is all just different expressions of the same concept'.
Calling this particular video the 'encodings' video is perhaps a bit of a misnomer, because the only video in the 'module' which covers a topic which can't be thought of as a *sort* of encoding (even binary and number systems can fall under that umbrella IMO), is hashing which is covered tomorrow. Otherwise, it's all 'at a high level, how do computers interpret and work with data'.
The main reason I wanted to start with binary is mentioned in that video; it's easy for anyone to conceptualize, one they understand what binary is, that binary is the natural number system for computers because a basic electronic switch is high or low, on or off, and from that we can build everything else.
always wondered about this, thanks for explaining!
Wow that's actually a really great video, love the way u're explaining things, that's clear and rapid !
I'm learning coding and it's been a while that i'm thinking about the thing of making a png file only by coding, could you please make videos about the specificities of each file type, that could be a great topic i think :!
Glad you found it helpful! I definitely plan on going more in depth on specific formats, including PNG, JPEG, and exploring h264, h265, etc for video. There are super interesting computer science and mathematical concepts to explore in doing so. I can't say exactly _when_ I'll get to that stuff though-there's a lot I want to cover.
Damn how is your TH-cam channel so underrated? I thought it was gonna be some ai voice nonsense but wqs pleasantly surprised.
Haha, I'm happy I could surprise you. It's a new channel; everyone starts at zero. Apparently TH-cam has decided to bless this particular video with recommendations, so I can't complain.
Cool video
Glad you enjoyed it ☺️
Hey man, wish you the best of luck. I also recently started my channel and finally the last video got picked up by the algorithm. Surely for you it’s gonna happen as well :)
@@ProgrammingWithJulius cheers! I'm enjoying your CS geoguesser video. 😅
@ it certainly was a lesson for me. Worked really hard on it for weeks (next to my full time job) and it got less than 1k views for the initial period. No more large projects until I have a bigger following 😂
amazing video
Thank you, glad you liked it! 🙂
understood!
bit confused about the title, also I haven't watched further than 7 seconds, but isn't decoding going from numbers to videos and not the other way around?
Fair question!
The answer is yes, but 'decoding' is just a verb, while 'encoding' is a verb and a noun.
The process of writing video data to a file with a defined format to disk is 'encoding', and the process of reading said file, and interpreting it so it can be turned into pixels on a screen is 'decoding'.
What you're missing is 'an encoding' is the ruleset which defines how to do both actions.
0:01 Is that you Obi Wan?
Little endian is not faster than big endian, that was only true for a very specific case that intel faced with one line of chips. Instead of being inconsistent with their next chips they decided to just stick to little endian
There are actual advantages to little endian ordering. For example, downcasting an integer on a little endian machine is a noop; you don't even need to calculate an offset. Similarly, addition and subtraction, which work smallest byte to largest byte, are simpler when I[0] is the smallest byte. There are advantages to big endianness for certain tasks too. The difference is usually very small, so when choosing an endianness for a general purpose computer, you go with the endianness which has the minor advantage for the extremely common operations (eg: downcasting, addition). Virtually every modern, widely used computer is little endian; ARM and Risc-V allow for big-endianness, but it's rarely used.
General Kenobi
swag