I dont get it? 5 years javascript dev here

It can be verbose, but there are other times where it can in fact be less verbose as you don't have any programmatic beaucracy and abstractions to deal with - at least for CISC processors. RISC ones are a different matter, but those are designed with higher level languages in mind so it would be foolish to want to program in assembly on them. Plus a pain in the ass.
It's no different then putting together a puzzle. You have all the pieces, you just need to figure out how to put them together to achieve what you want. I honestly have no idea why people struggle with it so much.
You can write modern, multitasking user land programs in assembly, that has nothing to do with virtualization. You'll of course be writing c/c++ function calls in assembly as OS's are written in them, but everything else in between can be pure assembly.

Most small scale software projects in ASM are untenable for most people. Having the wherewhithal to work on and make progress on such projects takes great a sense of purpose as well as the competence to overcome the inherent drawbacks of the programming form, and to exploit its benefits.
To call it a filter is an understatement. Most developers will call it pointless and, for them, they are correct.
Totally right about it's simplicity, but with certain macros it's bearable to design more complex systems. I created a macro system which aided in just this. It allowed register independent design of functions, allowing one macro to slot into any register set you need to avoid unnecessary scratching, this alone vastly improves the development time as you don't need to, for example, re-write a bin-to-hex algorithm just to print a number to the screen.

I've long since put this, and other macro systems, into a inclusion library for my own use but I have recently decided to make all of these essentially public domain to increase the popularity of assembly programming since I am working on a project which supercedes this one. Here is that library if you are interested.
gitlab.com/instrvmentaicari/mystdasmlib.

Not interested by the lib but impressed by your work and dedication user

Asm as in assembly?
Youre comparing assembly to javascript?
Lol?

Thanks.

>You can write modern, multitasking user land programs in assembly
k but why would you?

I think you could write assembly pretty efficiently if you had an all-purpose macro-library defined first. Back in the day, some people thought those would be the computer language of the future, rather than higher-level langs

I'm just starting to learn assembly and I want to get really good at it, in order to make a compile tool chain from scratch. I plan to make a Forth interpreter, and use it to make a Lisp interpreter in which I will be able to write the compiler itself.
Any advice, on this or on getting good to assembly? Do you have a must-see ressource maybe?

bump

Why would you write such programs in C when you could use Java?
Precision, less chance of feature bloat and, tertiarily, performance.
My suggestion is to start out writing very basic things in asm, but you kind of already knew that. My first projects were on the level of hexadecimal and decimal converters. Of course, I cannot go back to writing anything in assembly without my library, so I'd recommend using that. If you use my head.ah on linux, you don't even need to worry about linking or sections, you just need to assemble and chmod the executable (Brian Raiter's Tiny ELF guide demonstrates much of how I did this). Not to mention the fact that trying to write re-usable, modular code without something like genreg.ah is borderline impossible.

In terms of resources, Felix Cloutier's x86 reference is quite good. I remember just reading through these, trying to figure out what kinds of functions I could use each instruction for. That helped a lot. There are also the Intel and AMD architecture and software development guides which help with best practices and understanding the hardware you are developing for. It's useful if you are in a hot loop and need to make a performance decision on multiple options.

Also, getting to know your assembler's macro system is invaluable. It can literally multiply the speed at which you work. Diligently read the nasmdoc pdf. It is my friend and I suspect it will be your's, too.

Finally, if you haven't already, watch What's a Creel's excellent video on branchless programming. I was learning before watching this but once I found it I went all in on assembly and never looked back.

Some people just like doing things like that.