What is required for System Programming?

Question

System Programming

Hello. I want to ask if a system programmer needs knowledge of Assembler? I'm learning C myself. Based on your experience, would you need Assembler to write an OS, emulators, drivers, or anything else in the field of system programming? And also one more, perhaps stupid question, how much code is written in systems programming, or is this area related to electronics?

Answer 1

Very useful.

Answer 2

Does a systems programmer need knowledge of assembly language?

Need.
A system programmer, oddly enough, writes system programs :) That is, OS components, the kernel, firewood, various programs that work with hardware. Therefore, it is important for him to know how the processor works, and how, for example, you can optimize the code in a critical section where execution speed is important.
And although you rarely have to write on ASMA itself - only the most critical sections - read listings and dumps, be able to figure out what is written there, know what it all means - it is necessary.

how much code is written in system programming

A lot of stardom. The Linux kernel is a typical example of a system program :)

Answer 3

The assembler will be needed mainly for reading the source code of the assembler output of the compiler or disassembler. You don’t have to write so often on it, mostly assembler inserts / procedures inside the Java language.
For code size, ask GNU or Microsoft. If you only adapt existing developments, you won’t have to write much. But there will be nothing new either ← this is a hint in case you undertake to develop your own OS .

Answer 4

Helpful, but not required.
System programming, oddly enough, serves systems. Mainly operating rooms.
If you take any operating system, it has a huge amount of code and individual components, ranging from the kernel, device drivers, virtual drivers (for example, a file system driver), and programs like ping, netstat, and even notepad.exe
ps Too many theoretical questions, too few no practical. Start writing code instead of reading.