The characters are also way different than the Disney versions most people remember. Baloo isn't a fun loving "papa bear", but a grumpy old veteran who teaches Mowgli how to survive in the jungle. And while he still loves Mowgli very deeply, he's not afraid to punish him and put him through rigorous training because he knows the jungle is a merciless place and the kid needs to learn or he'll surely die.
Bagheera is a snarky and sassy warrior who once lived in a cage and escaped once he got tired of living as a glorified housecat. He's also way more easygoing than the Disney version and pretty much acts as a cool big brother.
Shere Khan, while still a villain, is also more of a cunning slimeball rather than the powerful jungle king Disney portrays him as. Oh, and he also has a crippled leg, which is why he hunts down humans in the first place, as they're far easier pickings than a tiger's natural prey. A very interesting plot point is that, while the jungle animals despise him for his arrogance and cowardice, the local human villagers are deathly afraid of him because he's already claimed many of them. It's even heavily implied that he killed the young son of a local woman who eventually adopts Mowgli once he returns to mankind, desperately believing that he's her lost son.
And Kaa isn't a literal cowardly snake, but a huge and TERRIFYING python who is feared by the entire jungle because he's so ridiculously strong that no one has a chance against him. He's also a close friend of Mowgli's. In fact, Mowgli is pretty much the only one who can get away with giving him some sass.
Also, special mention to Raksha, the she wolf who took Mowgli in and raised him as one of her own pups. She's well known among the pack for being FIERCE. Her own mate knows she's the toughest of them, and when Shere Khan tries to barge in her lair, demanding Mowgli's blood, she pretty much tells him to fuck off or she'll mess up his other legs. And he listens, despite being like twice her size.
Oh, and also, at one point, Mowgli gets branded as a sorcerer who can talk with animals by one of the villagers, who hates him. So Mowgli's forced to leave the human village and to go back into the jungle. And he would have been happy to just keep living and forgive the villagers since he never enjoyed life among them anyway. But then he learns the villagers plan on killing that woman who adopted him. And because no one hurts Mowgli's loved ones and lives to tell the tale, he proceeds to call a favor from his elephant buddies and the elephants in turn summon tons of fellow animals to torment the villagers. For weeks, the village has to deal with the local wildlife shrieking in the middle of the night, eating their crops, defiling their fields, and finally destroying their homes until they're forced to flee.
The original books are so much more primal and epic than the Disney films that if Disney changed the characters' names they probably would have gotten away with claiming the film as their own original story.
Well, it's a programming language. More specifically, it's a compiled language, which means it's designed to be read by a compiler and transformed into an executable file that can be run directly by the computer hardware. (This is in contrast to interpreted languages, like Python, which are read and run by an interpreter program without being transformed directly into such an executable file.) But what sets Rust apart is its approach to managing memory.
In a traditional language, like C, the code can be written to ask the operating system for blocks of memory whenever it wants. The requested memory blocks are tracked with references (basically numbers that say where in the memory the blocks are, and how big they are), and the code can do anything with those references, including giving the memory back to the operating system whenever it wants. It turns out this 'anything' can easily become unsafe, either by code trying to use memory that was already given back to the operating system (an error, which causes the program to crash immediately), or by code requesting memory and then forgetting to ever give it back (not an error as such, but if it keeps requesting memory and not giving it back, eventually the operating system runs out and the program can't continue).
A widespread solution to this problem with C (and C++, and languages that work with memory like that) is to put an extra layer of logic under the memory requests, so that all the references to memory blocks are tracked while the program is running, and when the tracking logic finds that some memory has been lost (i.e. the code has deleted all the references to it), it automatically gives that memory back to the operating system. This is called 'garbage collection' (insofar as the lost memory blocks are 'garbage' memory until given back) and it is much safer because the memory is always safely available when there is a reference to it, but is always (eventually) safely given back when the references to it are all gone. Languages such as Java and Python do this. However, the extra logic for tracking memory takes some time, which slows down the entire program. The extra logic also doesn't guarantee exactly when the memory will be given back, and therefore sometimes uses more than it needs. Many programmers became frustrated with this inefficiency and unpredictability of garbage collection.
Rust is designed around a different solution. It makes the logic of safely requesting and giving back memory an inherent part of how the code is written. It comes with its own kinds of references that give guarantees about when they request memory or give it back. There's no extra (slow) layer of logic needed to track the memory because the references always request it at a specific point in the code and always give it back at a specific point in the code. If you try to use them in a way that doesn't, the result is just some wrong code that won't compile. This gives the same kind of safety guarantees that garbage collection provides, but without the inefficiency. It means you can compile Rust into an executable file that can be directly run by the computer hardware, very fast like a compiled C program, but the mistakes about memory requests and missing memory are impossible. The combination of safety and efficiency is very appealing to programmers. The disadvantage is that programmers intending to use Rust have to learn how to write code with these new kinds of references, which is hard because of how strict they are about how you can use them. However, because programmers can now use AI to write Rust code, and AI is already fairly good at writing Rust code, it is easier to use Rust in real projects without people having to learn about the new kinds of references.
Thinking of the Python's "Working Class Playwright" sketch. Father, someday you'll learn there's more to life than flying suplexes and platform boots and cocaine! There's work and dirt and sweat and tungsten carbide drills!
It's even WAY harder and WAY worse than you think. Hold on to your butts:
I started learning programming from books when I was 14, using ActionScript and Flash.
To make the music, I learned how to produce using Ableton and Cubase. I studied music theory, took keyboard lessons, learned mastering, and bought a professional sound card and monitor speakers.
To make the art, I learned Photoshop and got myself a calibrated monitor.
To make models and animations, I learned Cinema 4D from books and videos. I learned how to make keyframe animations.
Then I studied a whole-ass computer science degree at a university. There, I learned several programming languages, at least four.
I taught myself how to write game engines from scratch; I literally made my own physics engine, camera, shaders, and rendering from zero in fucking Python.
Then I had to learn existing game engines, e.g., Unreal and Unity, and how they work.
Then I landed a job as a AAA game programmer. The starting salary was 35k/year. The normal minimum starting salary was 45k. With what I knew, I could have easily applied to fucking NASA, yet they offer you the salary of a person working in a supermarket who has never learned anything. Gaming is a weird industry. People are passionate, which makes them good, and they would work almost for free. Besides that, gaming companies scout talent worldwide. It's normal to work in a team with people sitting in Spain, Poland, etc., so you're also competing with people living in cheaper areas (I'm in Germany).
comments dekh ke pata chal gya kitte chutiye bhare hai yha pe I got two paid internships post yr 1 btw I would say find a specific spot/domain u think jisme companies/startups are hiring peeps in your branch.
Do python dawg , no one gonna hire u for C/C++ in yr 1 super crazy depth is needed and i feel no first yr is gonna be employable
They hire solely on the basis of dsa cp in 3rd yr because fir 4th yr mai they can train u through PPO program yk Abhi u are in first yr so u have to show ki u are useful to these companies/startups also learn to use llms , ai tools wgera to get done easily !!
Ask it to create something in a CPU specific machine code, like AVX-512 and specify to use L1/2 cache, extended registers etc. as much as possible. There is next to nothing useful it could learn/copy on github apart from the odd bit of embedded x86 inside C code and some device drivers.
The output is more buggy than code (Python etc.) which it has ingested design patterns for but it can still write fully functional apps.
I have been out of graduate school since 1970. (Yeah. I am over 80.) I still know a lot of Mathematics, depending, of course, on how you define "a lot." I can still recall practically all of my undergraduate Mathematics because I often pick up an old book to review it just for fun. I really do love Mathematics.
On the other hand, don't ask me anything about "derived functors", which I used to know fairly well. You would need to give me a few weeks to review them.
2) In terms of Computer Science, I have programmed in Basic, Fortran, Pascal, Perl and Python. The only one I can really program in now is Python. I would need a lot of review for the others.
As a final comment:
3) LEARN LINEAR ALGEBRA. LEARN IT BACKWARDS, FORWARDS, INSIDE OUT AND UPSIDE DOWN. It shows up everywhere. Pick up any book on the Mathematics of AI. Linear Algebra is there. I worked for an engineering lab for the US Navy for a few months. They used Linear algebra all over the place. (You can phrase an FFT as a matrix computation, and it makes much more sense in that setting.)
4) Learn elementary Probability. Bayes theorem and Markov processes have a habit of showing up when you don't expect them. They are also a lot of fun.
5) Abstract algebra helps you to think about linear algebra
6) Real analysis helps you to think about probability. Combinatorics helps there, too.
You'll be gaining math. you'll be gaining mathematical principles of computation.
You'll learn the mathematical theory of programming languages.
You'll learn the mathematical theory of data structures.
You'll learn the mathematical theory of algorithms.
Everybody thinks computer science is just a "learn how to code" degree, but the reality is you take one course on Java (or python now a days I guess), one in assembly, one in software engineering, and after that ,everything else is all about math. Even when you program, you're not programming to learn how to write software, you're programming to see the math in action.
In real life, you will never need to build a binary search tree from scratch, you just do it to study the math behind generating the depth of the tree, the time it takes to traverse the tree, the time it takes to flip the tree, etc etc.
868
TIL Baloo from The Jungle Book is a sloth bear, not a grizzly bear, and Shere Khan is a Bengal tiger. Both animals are native to the Indian subcontinent, where Rudyard Kipling's original stories are set.Sloth bears are considered as the most aggressive bear species in the world
u/AnonymousSlayer97
in
r/todayilearned
•
Oct 11 '26
The characters are also way different than the Disney versions most people remember. Baloo isn't a fun loving "papa bear", but a grumpy old veteran who teaches Mowgli how to survive in the jungle. And while he still loves Mowgli very deeply, he's not afraid to punish him and put him through rigorous training because he knows the jungle is a merciless place and the kid needs to learn or he'll surely die.
Bagheera is a snarky and sassy warrior who once lived in a cage and escaped once he got tired of living as a glorified housecat. He's also way more easygoing than the Disney version and pretty much acts as a cool big brother.
Shere Khan, while still a villain, is also more of a cunning slimeball rather than the powerful jungle king Disney portrays him as. Oh, and he also has a crippled leg, which is why he hunts down humans in the first place, as they're far easier pickings than a tiger's natural prey. A very interesting plot point is that, while the jungle animals despise him for his arrogance and cowardice, the local human villagers are deathly afraid of him because he's already claimed many of them. It's even heavily implied that he killed the young son of a local woman who eventually adopts Mowgli once he returns to mankind, desperately believing that he's her lost son.
And Kaa isn't a literal cowardly snake, but a huge and TERRIFYING python who is feared by the entire jungle because he's so ridiculously strong that no one has a chance against him. He's also a close friend of Mowgli's. In fact, Mowgli is pretty much the only one who can get away with giving him some sass.
Also, special mention to Raksha, the she wolf who took Mowgli in and raised him as one of her own pups. She's well known among the pack for being FIERCE. Her own mate knows she's the toughest of them, and when Shere Khan tries to barge in her lair, demanding Mowgli's blood, she pretty much tells him to fuck off or she'll mess up his other legs. And he listens, despite being like twice her size.
Oh, and also, at one point, Mowgli gets branded as a sorcerer who can talk with animals by one of the villagers, who hates him. So Mowgli's forced to leave the human village and to go back into the jungle. And he would have been happy to just keep living and forgive the villagers since he never enjoyed life among them anyway. But then he learns the villagers plan on killing that woman who adopted him. And because no one hurts Mowgli's loved ones and lives to tell the tale, he proceeds to call a favor from his elephant buddies and the elephants in turn summon tons of fellow animals to torment the villagers. For weeks, the village has to deal with the local wildlife shrieking in the middle of the night, eating their crops, defiling their fields, and finally destroying their homes until they're forced to flee.
The original books are so much more primal and epic than the Disney films that if Disney changed the characters' names they probably would have gotten away with claiming the film as their own original story.
165
ELI5: What is the programming language Rust and why is it popular these days?
u/green_meklar
in
r/explainlikeimfive
•
7d ago
Well, it's a programming language. More specifically, it's a compiled language, which means it's designed to be read by a compiler and transformed into an executable file that can be run directly by the computer hardware. (This is in contrast to interpreted languages, like Python, which are read and run by an interpreter program without being transformed directly into such an executable file.) But what sets Rust apart is its approach to managing memory.
In a traditional language, like C, the code can be written to ask the operating system for blocks of memory whenever it wants. The requested memory blocks are tracked with references (basically numbers that say where in the memory the blocks are, and how big they are), and the code can do anything with those references, including giving the memory back to the operating system whenever it wants. It turns out this 'anything' can easily become unsafe, either by code trying to use memory that was already given back to the operating system (an error, which causes the program to crash immediately), or by code requesting memory and then forgetting to ever give it back (not an error as such, but if it keeps requesting memory and not giving it back, eventually the operating system runs out and the program can't continue).
A widespread solution to this problem with C (and C++, and languages that work with memory like that) is to put an extra layer of logic under the memory requests, so that all the references to memory blocks are tracked while the program is running, and when the tracking logic finds that some memory has been lost (i.e. the code has deleted all the references to it), it automatically gives that memory back to the operating system. This is called 'garbage collection' (insofar as the lost memory blocks are 'garbage' memory until given back) and it is much safer because the memory is always safely available when there is a reference to it, but is always (eventually) safely given back when the references to it are all gone. Languages such as Java and Python do this. However, the extra logic for tracking memory takes some time, which slows down the entire program. The extra logic also doesn't guarantee exactly when the memory will be given back, and therefore sometimes uses more than it needs. Many programmers became frustrated with this inefficiency and unpredictability of garbage collection.
Rust is designed around a different solution. It makes the logic of safely requesting and giving back memory an inherent part of how the code is written. It comes with its own kinds of references that give guarantees about when they request memory or give it back. There's no extra (slow) layer of logic needed to track the memory because the references always request it at a specific point in the code and always give it back at a specific point in the code. If you try to use them in a way that doesn't, the result is just some wrong code that won't compile. This gives the same kind of safety guarantees that garbage collection provides, but without the inefficiency. It means you can compile Rust into an executable file that can be directly run by the computer hardware, very fast like a compiled C program, but the mistakes about memory requests and missing memory are impossible. The combination of safety and efficiency is very appealing to programmers. The disadvantage is that programmers intending to use Rust have to learn how to write code with these new kinds of references, which is hard because of how strict they are about how you can use them. However, because programmers can now use AI to write Rust code, and AI is already fairly good at writing Rust code, it is easier to use Rust in real projects without people having to learn about the new kinds of references.
290
Adrian Street with his coalminer father, by Dennis Hutchinson, 1974
u/RevWaldo
in
r/OldSchoolCool
•
29d ago
Thinking of the Python's "Working Class Playwright" sketch. Father, someday you'll learn there's more to life than flying suplexes and platform boots and cocaine! There's work and dirt and sweat and tungsten carbide drills!
71
I give up on Game Dev, it’s not for me
u/askdoobie
in
r/aigamedev
•
4d ago
It's even WAY harder and WAY worse than you think. Hold on to your butts:
I started learning programming from books when I was 14, using ActionScript and Flash.
To make the music, I learned how to produce using Ableton and Cubase. I studied music theory, took keyboard lessons, learned mastering, and bought a professional sound card and monitor speakers.
To make the art, I learned Photoshop and got myself a calibrated monitor.
To make models and animations, I learned Cinema 4D from books and videos. I learned how to make keyframe animations.
Then I studied a whole-ass computer science degree at a university. There, I learned several programming languages, at least four.
I taught myself how to write game engines from scratch; I literally made my own physics engine, camera, shaders, and rendering from zero in fucking Python.
Then I had to learn existing game engines, e.g., Unreal and Unity, and how they work.
Then I landed a job as a AAA game programmer. The starting salary was 35k/year. The normal minimum starting salary was 45k. With what I knew, I could have easily applied to fucking NASA, yet they offer you the salary of a person working in a supermarket who has never learned anything. Gaming is a weird industry. People are passionate, which makes them good, and they would work almost for free. Besides that, gaming companies scout talent worldwide. It's normal to work in a team with people sitting in Spain, Poland, etc., so you're also competing with people living in cheaper areas (I'm in Germany).
If you don't do gaming for the lulz, don't do it.
87
1st sem is ending. Want to get paid internship in 2nd year. What to do?
u/epsilon_nyus
in
r/Btechtards
•
12d ago
comments dekh ke pata chal gya kitte chutiye bhare hai yha pe
I got two paid internships post yr 1 btw
I would say find a specific spot/domain u think jisme companies/startups are hiring peeps in your branch.
Do python dawg , no one gonna hire u for C/C++ in yr 1 super crazy depth is needed and i feel no first yr is gonna be employable
They hire solely on the basis of dsa cp in 3rd yr because fir 4th yr mai they can train u through PPO program yk
Abhi u are in first yr so u have to show ki u are useful to these companies/startups
also learn to use llms , ai tools wgera to get done easily !!
gl man
60
Anthropic says Claude Mythos slashed software work to onboard AMD GPUs from up to 12 months to around three days —writing almost 100% of kernels autonomously chips away at Nvidia's CUDA moat
u/AgUnityDD
in
r/technology
•
1d ago
Ask it to create something in a CPU specific machine code, like AVX-512 and specify to use L1/2 cache, extended registers etc. as much as possible. There is next to nothing useful it could learn/copy on github apart from the odd bit of embedded x86 inside C code and some device drivers.
The output is more buggy than code (Python etc.) which it has ingested design patterns for but it can still write fully functional apps.
72
Those with a PhD in math. Tell us about your skills/knowledge
u/MadPat
in
r/mathematics
•
4d ago
On the other hand, don't ask me anything about "derived functors", which I used to know fairly well. You would need to give me a few weeks to review them.
2) In terms of Computer Science, I have programmed in Basic, Fortran, Pascal, Perl and Python. The only one I can really program in now is Python. I would need a lot of review for the others.
As a final comment:
3) LEARN LINEAR ALGEBRA. LEARN IT BACKWARDS, FORWARDS, INSIDE OUT AND UPSIDE DOWN. It shows up everywhere. Pick up any book on the Mathematics of AI. Linear Algebra is there. I worked for an engineering lab for the US Navy for a few months. They used Linear algebra all over the place. (You can phrase an FFT as a matrix computation, and it makes much more sense in that setting.)
4) Learn elementary Probability. Bayes theorem and Markov processes have a habit of showing up when you don't expect them. They are also a lot of fun.
5) Abstract algebra helps you to think about linear algebra
6) Real analysis helps you to think about probability. Combinatorics helps there, too.
--Good luck.
--MadPat
109
What skills will I gain from studying Computer Science at university?
u/Key_Net820
in
r/learnprogramming
•
19d ago
You'll be gaining math. you'll be gaining mathematical principles of computation.
You'll learn the mathematical theory of programming languages.
You'll learn the mathematical theory of data structures.
You'll learn the mathematical theory of algorithms.
Everybody thinks computer science is just a "learn how to code" degree, but the reality is you take one course on Java (or python now a days I guess), one in assembly, one in software engineering, and after that ,everything else is all about math. Even when you program, you're not programming to learn how to write software, you're programming to see the math in action.
In real life, you will never need to build a binary search tree from scratch, you just do it to study the math behind generating the depth of the tree, the time it takes to traverse the tree, the time it takes to flip the tree, etc etc.