ai

Could you make a video for floating point?? how is it work??

Thanks

Great stuff, thanks!

The 6809 had OS-9 which was an awesome preemptive multitasking OS for the time.

Can I get a peek at your code? I'm also in osdev but I'm quite loss atm.

Would love to see this code

Sorry guys, won’t be able to help you there.

Yes can we get the code please

Thank god I didn't go into computing

Wait what are you doing here😂😂

I was like "Concurrency? Well, context switching, of course..."

lol do you have an SRE interview coming up?

1 and 2 for a short video. 3 is a massive undertaking.

@@camelCase60 No. I have to give a presentation to college freshers who have just joined at the office and I want to make it an animated presentation by simplifying the concepts. I am very bad at creating animations and explaining things in a simplified way. I have been searching up all kinds of materials on UKposts but it's not coming out very well. Such videos will be helpful. Teaching is a skill which I do not possess so I am asking for help.

@@deanvangreunen6457 agree.

​@@phoneix24886so you want him to do your job for free?

I'm working on a video about how computers execute code, you'll love it!

​@@CoreDumpped This was a great video and I subscribed after watching it. This comment is worthy of hitting the bell.

And I'm thinking of how there are many observable asynchronous codes didn't collide with each other

A cool, another developer in C# here, and more languages. Definitely applicable there, as Tasks and async await are very important features in the language. C# was also basically the first language implementing that. Programming language level scheduling systems are basically a solution to move scheduling away from OS level (threads) to the logical level within the application itself, which is especially useful when you have a lot of concurrency, like many IO tasks. Because of using a whole magnitude less resources. OS threads are far more expensive. The scheduling mechanism still maintains multiple threads, but on a queue far more tasks will be scheduled to be consumed by these threads in very similar fashion of how an OS scheduler works.

I love it too!

The AI voice is really high quality tbh

I completely missed it until the voice pointed it out 😮

i genuinely didnt realize it was ai

In the begining, the bing bang happend 13.8 billion years ago.... then humans invented data, and then the ip protocol

A bunch of electrons travel through wires, and hardware/software decode those signals as different things depending on what their purpose is. Tada!!!! Although I'm just joking, this is pretty much what it is lol

fasterthanlime's video on explaining the internet might just be somewhat the video you're looking for in the meantime

I am afraid what you're looking for is not here, this channel is more like a low level way of looking at computer, I would say the programming part of the Operating System, of course networking requires some low level and programming stuff but that wont help you manage cisco, or any networking technology, Start with cisco and their free courses on skills for all platform. Rick Graziani channel is also a good idea for fundamentals, he's maybe a cisco instructor since he was in many skills for all courses, David Bombal has also some free CCNA course

Ben Eater has an excellent series on networking. Her works up maybe the first three or four OSI layers from an electrical engineering perspective. From there, you can find other tutorials to round out your knowledge.

Glad you enjoy it!

N64 from 1996 was scalar, in-order. Itanium was in order super scalar. Dec Alpha could execute out of order as did Cray. Other super scalar CPUs are unsafe: spectre . Branch prediction was invented by IBM and slowed down their processor. Now it allows attacks.

Yes, treads are handled very similar to processes, they're also scheduled. There are some differences tho, for example if the main process is terminated, all of its threads are also terminated (unless otherwise specified). I' ll record a video about more details on this.

A "process" is, in a lot of ways, the same thing as a "program". It can have one or many threads, but the crucial thing is that they all share the same memory space, so, for instance, a pointer from one thread can be used by another thread in the same process without any issue beyond the normal multithreading hazards. By contrast, if you tried to dereference a pointer from another process, you'd very likely crash with a segfault, or at the very least, access the wrong data. A process is the top most level in the OS environment. Each process is given its own address space, and they cannot access memory allocated to other process unless both processes explicitly request the OS to allocate a shared memory buffer. This is why on modern operating systems, a program can (usualy) crash without taking down the entire OS and forcing you to push the reset button. Also, when you bring up the task manager in Windows, it gives you a list of all processes running on the system. Note that some programs will spin up multiple processes in addition to multiple threads in each process. One good example is a client-server model, where you want the option of multiple users interacting in some way, but for single-user situations, it can be convenient to run the exact same server program on the same computer as the client, rather than having an entirely seperate single-user mode. It can also be useful when you're dealing with untrusted code, such as anything on the internet. If your browser, for instance, runs each tab in a seperate process, then you've created an additional barrier between a malicious scripting exploit on one website in one tab and your bank's login screen that you left open on another tab.

Fixed, thanks!

It runs on it? Ben Eater might offer you a more hands down explanation. Real breadboards instead of blackboards.

Thanks, will do!

One after another

The snapshot includes registers too. What it doesn’t include though is main memory (ram). This is the reason why programs with multiple threads can share memory, but also why programming multiple threads is difficult and has many pitfalls. In reality there’s also something called virtual memory, and it makes it so that threads (or even whole processes) can voluntarily share memory, but a rogue process cannot read/write the memory of another process

Hi! There is no noise reduction here because the audio is generated by AI

@@CoreDumpped lol I see. I wonder why it seems like there's words missing then. perhaps it's just me.

Doing things at the same time is one way of dealing with several things at the same time, but not the other way around.

Glad you like them!