Allen Swift Grammar Master School (Online Bootcamp - 2-Month Course)

[We will never be lenient on copyright issues in the future.]
Recently, I found out (through a tip-off) that someone who had taken my class had copied the "Memory Structure" section of my lecture material almost verbatim and had created a free lecture for himself to teach to others. He had also uploaded the video to YouTube as a free lecture.

Since you used almost the exact contents of the memory structure related to classes/structs, of course there was a copyright issue, so I contacted you, and you spoke with some miraculous logic, saying that the memory structure of code-data-heap-stack was like that to begin with, so why was that a problem(?)? You even asked me if I had the rights to that diagram(?). (Of course, fortunately, I was able to persuade that person and resolve the issue, and we decided not to bring up the issue any further by taking down the upload of the relevant lecture.)

So... I'm going to explain it again in case there are people who misunderstand or don't know about the process of making my teaching materials.

The memory structure of code-data-heap-stack is originally like that. However, in my lecture materials, there are parts that abstract the actual memory structure and explain it more easily, intuitively (excluding parts that you don't necessarily need to know, based on my logic). In other words, the picture that I am explaining in my textbook right now is a picture that I designed and abstracted from the beginning by redesigning the actual memory structure in my own way, so I have the copyright. (There are materials written in the same way, including other languages, and you can't find them in Korea/internationally. Because I designed and created them myself.)

It's not like I knew from the beginning that functions worked that way, and it's not like I knew from the beginning how the method dispatch table existed in the data area. I looked at hundreds of materials because I wanted to know how static and dynamic dispatch actually worked with only the words. Sometimes, I wanted to know the contents of materials in Russian so much that I just put them all through Google translator and looked up dozens of foreign materials. Since there were no materials in Swift, I deliberately wanted to read materials in Java (which had a lot of memory-related materials), so I studied the basic grammar of Java.

The textbook I am explaining to you now was not like this from the beginning. (About 3 years ago) When I was tutoring, the textbook had a slightly different format and pictures than now, and at that time, I still had some questions that I couldn't figure out, but later, as I studied several books on computer architecture and operating systems, I was able to understand the unsolved memory structural contents in the same form as now.

So what I can say with confidence is that the pictures and methods I am explaining are without any copied materials, and they are all about the things I was curious about while studying.

(1) How does a function work and why can't variables inside the function be accessed from outside?
(2) How can the CPU return to its original position and operate after the function is executed?
(3) What is the memory structure of method dispatch?
(4) Why do instances of classes or structures not have method addresses directly?
(5) Why can’t the storage properties be redefined?
(6) How exactly is the internal structure of class inheritance, and how is an instance created (in the form of inheritance)?
(7) What is the memory structure of the protocol?
(8) How does the memory structure of the protocol relate to the memory structure of the class?
(9) How closures are stored on the heap, and how capture data is stored.
(10) How does the memory structure work when multi-threaded?
(11) How does the CPU send and receive values in an asynchronous manner? etc.

In fact, while continuously wondering about the above contents, realizing them one by one, I learned them again, matching them with the memory structure, drawing pictures... This is the content that reflects the contents. It may be just a single page of textbook to you, but there were times when I pondered for months to complete a single picture. Please do not misunderstand that the materials I created were copied from somewhere because it seems like you have studied or seen some crude materials somewhere. I can tell you with certainty that you will not find similar materials anywhere. These are materials that I drew and designed directly from my head.
(As I mentioned during OT, we actually completed and revised all the teaching materials. It took more than a year without a break on weekends. In terms of time, it is material that actually took thousands of hours to create.)

And, I can confidently say that to my students because I designed and created all of this material myself. So, I am sharing what I have learned with you, and I am receiving a certain amount of money for it, and I am conducting the course.

Infringing on copyright is an act of deception against me and is an act that harms my other students (who pay to take my lectures). (Even if your intentions are good when you create a lecture and distribute it for free, if you copy and create something from someone else's material... that is not a good thing.)

There is also a plagiarism problem in the music industry. When a composer/singer plagiarizes another song, it is considered a serious social problem. Please do not simply think that plagiarizing my textbook is... well, it's all original, so it's okay(?). It is a betrayal, a backstabbing, and a crime against me, who spent thousands of hours (without any expectation that the lecture would go well from the beginning) and risked my life to sincerely teach someone.

In the future, if you use content related to memory structures, we will proceed with civil and criminal cases simultaneously without any leniency regarding copyright issues.

I give you some permission to post codes and other summary materials for your learning, but I do not allow any secondary creations or anything related to memory structures. Please be aware of this.