you can become a GIGACHAD assembly programmer in 10 minutes (try it RIGHT NOW)
Vložit
- čas přidán 7. 05. 2023
- People over complicate EASY things. Assembly language is one of those things. In this video, I'm going to show you how to do a 64-bit assembly Hello World. And it's only going to take you 10 minutes to do. LETSGO.
🏫 COURSES 🏫 Check out my new courses at lowlevel.academy
🙌 SUPPORT THE CHANNEL 🙌 Become a Low Level Associate and support the channel at / lowlevellearning
🛒 GREAT BOOKS FOR ASSEMBLY PROGRAMMING 🛒
Blue Fox: Arm Assembly Internals and Reverse Engineering: amzn.to/4394t87
Practical Reverse Engineering: x86, x64, ARM, Windows Kernel, Reversing Tools, and Obfuscation : amzn.to/3C1z4sk
Practical Malware Analysis: The Hands-On Guide to Dissecting Malicious Software : amzn.to/3C1daFy
The Ghidra Book: The Definitive Guide: amzn.to/3WC2Vkg
🔥🔥🔥 SOCIALS 🔥🔥🔥
Low Level Merch!: www.linktr.ee/lowlevellearning
Follow me on Twitter: / lowleveltweets
Follow me on Twitch: / lowlevellearning
Join me on Discord!: / discord - Věda a technologie
You've got no chance of becoming a gigachad - sorry
shit.
@@LowLevelLearning there's a gigachad in all of us. Don't give up
@@jayshartzer844 1.21 gigachads (jigga-chads :) ) LLL: thank you!
@@kennethbeal "jigga" chads...? 😳
A gigachad can't become a gigachad, because they already are, right? xD
I agree that Assembly itself is easy. The hard part is understanding your hardware, all the opcodes and the memory to name a few.
i mean, I wouldn't call the need for table lookups hard. just tedious and unwieldy. Which is probably the point. I would add that a good general rule is probably that if it's meant to be an industry skill, it's likely not hard because it would therefore not be profitable. That of course doesn't mean it doesn't require a bunch of learning preparation as boilerplate or require an ungodly amount of tedious work. An exception might be something like surgery that is just so fundamentally important that we do it no matter how hard it is and just retroactively structure things to make it profitable. Like give surgeons protections against lawsuits when their patients die in surgery, provided malpractice wasn't happening.
A lot less stuff is hard than people think, and it discourages a lot of people from learning.
It's definitely more work to get various tasks done, especially if you aren't/can't rely on libraries. The difficulty really comes in when you want to actually use it in a way that is beneficial over using some other language which will automate a lot of tasks for you, or you're on a platform where it's simply necessary because of lack of tools or where those tools can't accomplish the task you need or to do it efficiently. You're both pushed in to territory of a language that is very raw to the hardware, but also needing to really think hard on how to get the task done efficiently.
The hard part is when it becomes large you are ending up creating macros and functions, that you reinvent the wheel with your own custom crappy version of pseudo-C.
The hardware of the CPU is not the hard part, that's outlined on 10 pages; it's the rest of the system: operating system, viruses, security, disk drives, web portal, libraries (you need to know the interfaces to the libraries to use them). That stuff requires a LIFETIME to master, & it is constantly changing.
The syntax is gibberish tho
mov eax, dword ptr ss:[esp+] some shit, wtf? I'm trying learn it for hacking games but I find c++, rust etc far easier
The problem is how time-consuming it is to write everything because it's all broken down into little tiny steps.
I considered writing some macros or something before I realized I was inventing C from first principles.
So true, your own custom crappy version of pseudo-C. Assembly is fun to know and is a must if you play around with a 6502
On Arm I only use it now when I needed to preset values for a reset (reboot) to a new fixed address.
I think you can write C code, then ask compiler to generate Assembler code out of it - now you could learn from it or modify ;-)
Fast and tweakable!
Yeah I've been running into that issue myself lately. The thing is, I haven't touched anything besides Assembly in my life yet, and it still happened
Not everything should be written in assembly but some problems are easily solved that way. I've been programing an Arduino in C and I'm quite sure it would be easier in assembly. I have no way of knowing if the C will even work reliably because I have no way to know what code it generated, it is quite possibe my interrupt routines will take longer to execute than time available. This is not something easily tested because the errors will only show up under certain load conditions.
@@igorthelight The nature of compilers in general, they create the intermediate files which are assembly, then feed that through the linker to produce machine code, you are correct that you can set a flag to preserve the assembly code. Generally the compiler toolchain is configured so the compiler breaks down the code, produces an efficient assembly then it will write the object files, run it through a linker then produce a final runnable file.
Learning Assembly isn't nowadays just for embedded, driver, kernel, etc. programmers but for anyone that wants to understand the WHY and HOW of your higher level programming language and your operating system. You'll develop a better understanding of what's happening under the hood so to say.
Thanks for saying this! When you throw away all high level knowledge in computing in favor of learning it all again bottom up, it suddenly becomes scary how many people in software development work with a system they dont understand on any concrete or essential level. It is kinda equivalent to taking your car to your mechanic and they dont even understand basic concepts like torque or gear ratios.
Agreed! Plenty of people “showing” assembly, nobody teaching how to use it and accomplish things.
I still can't believe Chris Sawyer made Roller Coaster Tycoon entirely in assembly. Possibly the biggest chad move in coding ever
That just blew my mind
Coding games in assembly was common in the day
@@SMGJohn Although it was common, it wasn't used for games as complex as this
Completely agree! Assembly is much simpler than most programming languages, learn the basic operations and registers and that's pretty much it. The hard part is keeping track of all what’s going on in your head!
Sure. Assembly is easy, because the opcodes are simple commands. I think what it makes it hard is the real programming. Like, if you want to sort an array .. pretty easy in Python, Java, .... in Assembly not so much, because you have to programm every tiny step of the algorithm.
You have to understantd how the CPU works, how to use the memory addressing and how to control hardware components like interrupt controler, timer chip, keybord, mouse, sound card, how to use BIOS software interrupts from mainboard and graphic card, network cards and a lot more. I do this for many years, but it never end. Actualy i try to learn to program ADLIB 3 register for sound.
@@michaelstoeckel2954 thats the fun part in my opinion, reinventing stuff that already exists is fun for some reason
That's why it's useful to use a simulator that runs step by step and shows you the value of your registers.
@@tomasfiorentini4126 Yes, it is very importent for beginner to know what a single instructions exactly is doing. I began to learn assembly on 6502 CPU with three 8 bit register before i switched to 80286. There are some tiny diffences on how some instructions works and if a flag in the flag-register is touched or not touched for example. I used debug from MS DOS in the first half year. I take a while to understand that to build a routine on x86 is more simple. Only 8 bit instructions is the hell if you have to handle almost with 16 bit calculations.
My understanding of assembly is fairly trivial, but not gonna lie i had fun time learning Intel 8086 assembly in college.
How long ago was this? Intel 8086 brings back memories
@@therealb888 the course officially stopped being taught last year. I think it was picked that assembly because we studied in depth the architecture in the theory lessons and that processor is relatively simple to explain to newbies comparing to more complex processors.
Well I didn't, but nevertheless I felt compelled to implement printf in 8086 16bit assembly, i felt proud and miserable at the same time
Good for you! For simple stuff, x86 asm has basically stayed the same, it's just as brain-bustingly poorly designed as always!
This is why I recommend people take a compilers class. Understanding the intricacies of compilation really helped me to understand how assembly worked; especially when it comes to how the registers are managed and how it interacts with the stack during function calls.
Someday I’m going to try to implement Donald Knuth’s MIX computer architecture (emulate it on qemu), build an assembler for it, and maybe even build an LLVM backend for it and a small compiler to compile a toy programming language down into mix.
I use Assembly for ROM Hacking, and I was really intimidated to learn it at first, and it took me taking a class in ARM Assembly to realize that it's actually not that bad. Once I figured out how 65816 Assembly interacts with SNES hardware and the game itself, I've been able to pull off a lot with it. It's a lot of fun, and it makes you feel really smart when your code works exactly as intended!
6502, the language used in NES rom hacking, there's an youtube channel dedicated to Nes 6502 Assembly btw. It's called NesHacker.
Which class did you take?
The only difficulty of assembly is the fact that is the most machine-like language u'll ever have, If u turn your mind into that and consider what a computer actually does, it turns far easier (it's not easy btw) to learn.
FINALLY, A TUTORIAL I CAN FOLLOW. Not that I couldn't follow along on all the other ones, but I have been banging my head against this wall for years. Somehow, I've never been able to get so much as an actual error message out of the assembler. Seeing "syntax error" because I forgot the leading periods in the asm file made my whole week.
I have occasionally created CPU simulations before, and I create custom versions of machine code. Programming anything was pretty awful.
I bet ChatGPT could've helped you with that
I recommend learning either nasm or fasm as they're far easier to use and understand than GNU `as`. They also implement a much better syntax.
is the wall finally broken? have you finally proved that your head is harder and tougher than the wall?
@@kipchickensout hihi. xd Like in here: mov rdi, qword ptr[rsi]? ;)
Great, great video. Having learned some ASM 6502 this past year made this video feel very accessible. It gets easier with time and practice! Who knew? Thanks for making this.
I just watched your video about return statement and instantly subbed , keep making content like that brow I love low level learning
tis-100 is honestly where most of my assembly knowledge comes from. It''s definitely not the full writing in assembly meme, but it's close enough to understand the high level of how it's working and you get to solve some cool puzzles along the way.
Good grief, that game is something else. I think it's much harder than any 8 bit micro I've ever worked with!
I was thinking about trying that game. I have played shenzhen IO which is fun.
Exapunks is good too
I've been learning 32 bit assembly for a uni class and this has been way more helpful than anything my prof has taught even if 64 bit is a little different
x86 stuff is so much different with x64. I just sugeest you to learn x64 directly not after learning x86
I'm learning 32-bit assembly in class too (MIPS-flavored, idk why...) and this video has been more meaningful than 4 hours in class...
MIPS is pretty easy to work with, and it's the architecture of PlayStation, so if you ever want to hack PSX games you've got a head start.
I very much needed to be reminded, at this exact moment, that I could be doing this thing I'm doing the right way in assembly. Thank you for helping me be my best self. Great vid!
Huh, you managed to make asm acctually understandable. I'll acctually try to pick it up after this considering I am into electronics. Cheers lad. Takes special skill to explain like this.
the fun thing about asm is that its not hard, it is as easy as it can get. but its so incredibly detailed that doing anything big in it takes a lot of work. Not an inhuman amount of work, mind, roller coaster tycoon was written in asm back in the day :D
@@Maric18 Locomotion too obv. and it's currently rewritten into C++ OpenLoco.
that's actually one of the cleanest hello world i have seen in assembly.
Thanks for reminding me of the Assembly programming language. Since I left college I've been into low level language such as the Assembly but I don't have the chance to work on it. And now I do and you made me remember with this simple tutorial
You are such an inspiration man
:)
@@LowLevelLearning It's true, I learned a lot from you. it's extremely hard to find someone passionate and knowledgeable about low level stuff. Almost everyone and their mothers talks about Web Dev and front ends developments but only few talk about the nitty gritty stuff of OS and low level programming.
Hope you delve more into assembly programming and reverse engineering.
Yea, my friends just love when i start talking about assembly... great video, love to see i am not the only one interested in this stuff :)
This is such a simple tutorial that doesn't overcomplicate the use of instructions. Thank you.
Perfect! Thanks for keeping Assembly alive! I believe most of the young programmers won't really appreciate it, but this is a great initiative! Thanks again!
Awesome to see assembly content. A long time ago I would have Microsoft C output asm which I could then edit for optimizations based upon knowledge of the incoming data. 10% to 50% reductions in clock cycles made a huge difference.
I got inspired by your assembly course, got myself a risk-v board and I am now trying to create an assembly only project.
First steps, creating macro's for push, pop and basic string functionality so at least I have some way to debug my code. 🙂
I actually cheat a bit, chatGPT is a big help in assisting me to get the macro's. However sometimes it gives me wrong information.
I could not manage to get my Windows 10 set up correctly, but used an Raspberry pi 4 instead, VS code that can remote connect to the Raspberry pi and off I go.
Programming in pure assembler, you have no idea how easy it is compared to bloated higher level languages that have a steeper learning curve than assembler.
Ah, that takes me back a decade or four. Definitely worth understanding, and cool as hell, but life is too short! Good 10 minute starter.
Great content as always. You rock bro!
Assembly is really useful when you need optimal performance from your hardware, but it's much more time consuming than C or higher level languages.
Back when CP/M and the Z-80 ruled, you'd use inline assembler in Turbo Pascal to speed up graphics calls.
It was also used to emulate hardware peripherals - software serial ports, cassette tape drive IO or composite video outputs ( e.g. Sinclair ZX-80).
Absolutely. Assembly _was_ useful when you needed optimal performance. But Intel chips are CISC and these days there's over a thousand opcodes, one of which may do what you're trying to do 10x faster.
No its not useful anymore
Compilers write way faster code then one could write by hand
REPT 1024
LDI
ENDR
Huh. TIL Turbo Pascal had versions for 8-bit machines. I always assumed it started out life as a DOS program.
@@maticz3923 Well yeah, if you’re a mediocre programmer then of course a compiler can write code just as good if not better than yours. If you’re one of those master assembly programmers like Randy Linden or Chris Sawyer though then no, a compiler is still slower.
Thanks for assembling this tutorial!
Making a genesis game in pure motorola 68000/z80 has been a blast for me. It's a hell of a lot of fun writing out a function then referencing op code cycle times to optimize written functions.
I've never tried inline assembly before in c but that looks like it might be fun.
The most exciting part about assembly language is discovering the different ways different chip manufacturers implement their code, such as the classic little-endian vs big-endian memory addressing, or even how the internal registers look - Microchip PICs are a good example of a totally different strategy from Intel based register architecture.
The point of all this is you can "say" you know how to write code in assembly language, but any other experienced assembly coder will ask you "which one?", as there are as many assembly languages as there are types of CPU. I was fortunate enough to get to learn the assembly language for the AP-101S CPU used on the Space Shuttle!
Once you understand modern computer architecture it's pretty trivial to learn a new flavor. Going from 6502 to x86 would probably be difficult, but going the other direction can be done in about an hour. It's more like learning a accent than learning a language.
Copyright part of it.
thank you for a moment of genuine clarity in my thinking!
With the sort of stuff people (including me) program in nowadays, programming in C and even knowing what a pointer is is already impressive by those standards.
I tried to explain pointers to my JS dev friends, but it's a hopeless endeavor
I had to use JS for my course, and coming from a primarily Rust background (basically Rust, Z Shell, and random tiny patches in other languages), I just could not understand how and when something gets mutated and propagated. Finally I saw somewhere that JS passes by copy of reference and finally I understood it a bit. JS is wack, and it makes people wack too!
It's really something I believe you can't understand until you've done it in ASM. C's piss poor pointer syntax is a huge source of this confusion if you ask me.
@@williamdrum9899 how exactly is it poor in your opinion?
I really fail to understand why people find pointers hard to understand and there's so much hype around it being difficult? I found it to be pretty straight forward and intuitive. The fact that your JS devs friends couldn't wrap their heads around it is beyond me.
This is great - thanks for putting it together. Minor nitpick: "\" = backslash (per iso8859 and utf-8), "/" = slash
Backslash, forwardslash... no iso needed
Thanks a lot for your video. Awaiting the new ones. Assembly is good to understand how processor works. This might me useful for micro controllers also.
A really nice no-nonsense getting started! Thanks!
Understanding assembly also gives a lot of insight of how languages like c++ uses memory and inside stuff works.
Earlier this year I was writing PDP-11 assembly. :p Which is surprisingly kinda easy-mode assembly as far as what it'll let you do, but you do have to make various considerations for performance.
What for?
That was still done in octal.
We had a micro PDP 11 at home for my dad’s work. I was already apt at 8086, 6502 assembly and I really loved the PDP-11. Just didn’t like the RSX11 OS. Neither did my dad at that time they relied on VAC/VMS. But this system that was written 10 years before and still monitored even older systems in field.
OH MY GOD. HOW COOL IS THAT!
Please, Do more assembly videos!!!
Thanks!
Assembly applications in real world can be divided in two categories: 1) learning/fun purporses. The code here will be relativelly small, simple to understand and maintain. Nothing special. 2) real applications/demo scene/games. These WILL require a lot of discipline and patterns to organize files, procedures and naming conventions. In this case, it is also mandatory to grab a good set of libraries to not reinvent the well every single time you start a new project. But that is true for any other language; imagine writing anything in C or C# or Java without any packages/libraries!
Assembly is fascinating. For a few years I have been toying around with high-level languages and always felt like something about it was interesting, and now I know: it was whenever something went wrong on the lower levels
We need a course on writing Secure/Safe C Programming for beginners!
Pretty sure the 'r' in the 64 bit register names is actually shorthand for the "rex" prefix, which I think means literally "register extension". Think: "rex eax".
You need the "r" here because its presence promotes the 4 byte operation to 8 byte and allows twice the possible registers to reference via the lower 4 bits of the prefix used as 3 high bits for each register address included in the mod-r/m byte, which only has 3 bits per register thus why 32bit x86 only had 8 general registers and why even bytewise operations on the high 8 registers need a rex prefix (i.e. an extra byte) so there's less program size advantage to downgrading them.
I think the 'e' in "eax" actually means "extended" too, from Intel's jump from 16 to 32 bits. "extended ax".
x86 is currently a hodgepodge of extensions to its ISA and I actually love it for that.
as soon as i started watching a full video and i saw the helmet come out during the good content i had to hit the like button lo.l thanks man for trying to entertain while teach us meticulous topics! okay back to it im resuming now!
That was really cool. While watching the video, I congratulate myself for dispising OOP, for the fact that, when compiled, the code is always procedural. And today learning ASM is so much easier than in middle 90's, when I messed around with MS-DOS's DEBUG.EXE. I even wrote a small assembly interpreter using MS QBasic (using peek and poke commands to directly execute binary code). Good times.
Nice. The last time I used an Intel assembly language was 1995. With a some good books I learned how to use it. I had 2 options: Borland's Turbo Assembler and Microsoft's C IDE, where asm could be embedded in C. I used them both and it was fun.
Before that I learned to use the somewhat different assembly languages for SIEMENS and IBM Mainframes and later on I used the one for IBM.
This is another time and another assembly language.
Back in the day, i was learning Turbo Pascal and in order to do realtime animation, i learned to write a refresh screen routine in Assembly because TP's refresh was too slow. It was the only time in my life that i had to use Assembly (that was in the 90's, kids.. lol)
This is hands down the best introduction to assembly I've seen. Everything explained super clearly from the beginning and a lot of things just suddenly fell into place that didn't before with other tutorials or examples. Only recently started watching this channel but the more I do the more impressed I get
reminds me of mips programming i did in college a few years ago
You're a great teacher, it is easy enough to follow especially with a devs background but I really didnt think it was simple maybe I'm just an idiot but I had to pause and reference a lot to understand what it is I was actually typing.
Even though I know all this I still watch it because I love assembly too much (I think you already know?).
I learned IBM assembly language, for their S/370 "mainframe" computers back in the 1970s. I later learned assembler for the Zilog Z-80, which was an 8 bit computer which was based on the 8080. I love assembler. But it does take longer to code, at least for me.
Today you could just write C, then ask compiler to generate Assembler out of your input ;-)
Now you can play around with Assembler!
I love you instructional video's, and you're twitch stream. Do you got longer video's that contain more information? :)
This is pretty cool, and may come in handy. Im thinking of making a super small JIT which just emits the byte sequence of some easy instructions to assemble some dynamic, but still pretty performant code together
Woooooow man!!!!! I am just too happy !!!! Just imagine yourself crowd surfing! Please make more videos on assembly like this, maybe devices, maybe network, gpu, idk!
Can you make a longer series about assembly?
Good introduction, and good job busting the asm is hard myth.
God told me to code a game in assembly. I am glad he didn’t tell me to build the next temple after Terry’s hard work. That’s a tough act to follow.
If you want to see how all this "assembly" works under the hood i suggest you watch the Ben eater 6502 series.
Quite a good vid and well presented as it gets straight to the meat and potatoes rather than inundate you with algorithms of how to arrange baby blocks in a straight line.
I wrote my first Motorola 6809 ASM program in 1984 on a SWTPC running the FLEX OS. I've been brain-dead ever since.
Nice job. simple and clean, thanks.
And one dude programmed Roller Coaster Tycoon with this, I still can't believe it.
Asm is very simple in principle, but to use it effectively, you really have to know the hardware you’re working in. Not to mention you have to keep a lot in your head at once such as which registers you can write to, and which registers hold the values you need, and which registers will be overwritten by another op. Not even getting into things like the question of whether your stack is aligned or not, if you popped all registers you pushed off the stack and where your parameter is located in stack relative to the current stack ptr (if you don’t have a base ptr). Add those things together and you end up with a kind of difficult to use effectively language
It is just a a habit. You learn these habits pretty fast.
And you create macro's, functions for it, inventing a language that is optimized for the code challenge.
C is way harder to to learn and write. And there us a lot of bloated historical technical depth in C.
Could you make more videos about assembly? Some ideas:
- What's the difference between MOV and LEA?
- When and how to use segment registers?
- How to do floating point arithmetic?
- CPU extensions. Like AVX and SSE.
"MOV" transfers the value from source to destination, "LEA" stores the memory address of source into destination
"How to do floating point arithmetic?" Avoid the x87 FPU at all costs, just use SSE/AVX.
LEA would be what in C is &table[0] or more correctly use is char* table. You want the address not the first variable in the table.
A C compiler would allow you to put the text with the command and the compiler puts the text after the machine code snippet, so zero terminated string in C is rarely done manually.
Haven't seen assembly in more than a decade back in college. Maybe I'll try it again for fun.
this is my new favorite video! more please!!
Next Tutorial: "Learn Malbolge in 5 minutes (SUPER EASY!)" 💀
After that: " Lets build our own CPU from scratch(super easy if you are near sand)"
@@amj864 😭
I understood a chunk of assembly for the first time! Please make a course for x86-64 assembly!
Assembly is cool. It's neat to see how things get done under the hood. .
Your guide is very informative. It looks a lot like BAL, basic assembly language on the ibm 360 that I used to use 40 years ago. Gave me a little deja vu. The assembly language looks a little simpler than BAL. Thanks for a great video. Well done. I guess you can’t save to a sql database w this? We used to save to flat files
This was pretty cool actually. Thanks
Great tutorial, thank you so much. For some reason, it's the first time that I get it on PC world.
In the PC (OS) world the syscall is a "black box" assembly. Right?
I learned assembly in home computing, whereas you stored to a memory location a value and the hardware made the rest without CPU cycles consumption. No need for "black box" assembly and way faster too. You were able to calculate everything, For this reason I like embedded programming. (no OS).
Yes, you are correct in saying that people overcomplicate things, for sure. I usually point out that ALL other programming languages consist of abstractions and interpretations of abstractions which makes it challenging to wrap your head around. Hence the hopping from language to language trying to reduce the mental anguish. haha Of course you also have the abstractions related to the problem you are trying solve, so you end up with abstractions within abstractions, making it worse. That's fundamentally what's wrong with C++ ... it deepened the level of abstractions with multiple contextual input variables and so on, which is why I avoided it like the plague. Years ago, I was doing a lot of Assembly language programming, primarily because the microcontroller chips I was using simply did not have a 'C' compiler available (or it was at a horrendous price) plus they certainly didn't have much non-volatile memory so you could not afford ANY abstraction that increased the number of instructions being used. Every step had to be carefully weighed for how much code memory was being used and how much time it took to process those instructions. Number of machine cycles, in other words. When you think of it, every single software program in existence could be rewritten in Assembly language and I'd bet that every program would be vastly improved in both performance and energy consumption. It wouldn't be easy but it would be possible. And fun, frankly. 😁
Will be coming back to this video perhaps a few times
I know assembly and this video didn't convince me that its cool to know... You made me cry.
Great intro! Thanks for sharing.
An amazing aproach!
Love it! Could you do a series on assembly where you go into more detail?
Agree
Yes
+1 please make more detailed tutorials about assembly ty
I like assembly because of the minimal overhead. Toolchains, makefiles... I don't have the patience for them. I've got a good setup for assembly development that just works. Does what I tell it to 100% of the time.
awesome man! thanks it' is really cool
Now you can pridefully put the assembly in you resume xD
Not studying this for a class or anything but for me to understand it better for Immunity debugger
also thanks for linking the syscall table site
Thank you, LLL!
I'm definitely adding this to my resume!
I loved assembler! I wrote assembler for the IBM 1401, the 6502 on my Apple, 8080 on CP/M on my Apple, and 8086 assembler on a Windows PC. Give me a macro-assembler, and I can do pretty much anything.
brief and comprehensive video
In python you search for libraries to do stuff for you
In C you make the whole code by yourself looking only for the critical sections
In Assembly you look for instructions, call lists and other stuff just so that you know what to write if you know what to do
It's not hard, but deppends on what you want to do
Really good tutorial. The only criticiam is that the last part with the syscall was a littlw rushed but overall everything else + the introduction was well explained.
Good video, I tried it in Kali, and I could do all but the hello world.
Also the errors I got were different, anyway, thanks man.
Holy crap. Looking up how this is supposed to work is impenetrable. Now there is an explanation.
Best video in Assembly ✨️in 10 minutes
Thanks for this nice course
:D
9:43 Truly asm is extremally simple only took us almost 10 min to write a hello world lol
The tutorial is great thanks a lot.
I attempted to program with machine language on my Apple IIGS. I borrowed a book on Apple machine language programming @ the Hawaii State Library, ages ago.
I just love how you add gigachad pic in the thumbnail
I love that at the end of showing us how to do simple syscalls he said "Assembly isn't that hard"
It is as if you've shown someone who isn't advanced at math how to add and subtract numbers and then you said "Maths isn't that hard"
I really liked the introduction into assembler. It doesn't look that scary anymore.
Ok knowing how to program with assembly isnt the hard part. Its understanding the architecture that your coding on
And no amount of high-level languages can help with that, I'm afraid. I had tried to go from coding a Neo Geo game using 68000 ASM to using C, and I actually found it MORE difficult with C!