You are suddenly dropped into a world where all people write code in assembly.
There is no "High Level Language", only "Assembly Language". There is no C, just ASM. There are no variables, only registers. You are in charge of managing all memory in your programs:
moving data from register to register,
poping data on the hardware supported stack.
How would you write a webserver, or a database? How long would that take? How much longer would it take you to do whatever it is that you are currently doing?
We need not stay here any longer.
Welcome back to reality, where the world is rife with programming languages above assembly
How did this come to be? Why would anyone not want to spend their day to day in assembly?
According to an answer thread on stack overflow,
ASM has poor legibility and isn't really maintainable compared to higher-level languages.
[Assembly] takes more code to do the same thing as in a high-level languge, and there is a direct correlation between lines of code and bugs.
Another take from wikipedia
In contrast to low-level programming languages, [high-level programming languages] may use natural language elements, be easier to use, or may automate (or even hide entirely) significant areas of computing systems (e.g. memory management), making the process of developing a program simpler and more understandable than when using a lower-level language.
Perhaps the abundance of higher level languages comes down to readability versus performance
First code for correctness, then for clarity (the two are often connected, of course!). Finally, and only if you have real empirical evidence that you actually need to, you can look at optimizing.
IMO the obvious readable version first, until performance is measured and a faster version is required.
I would go for readability first.
Great, looks like people are for clarity, so where does that leave us? And what does any of this have to do with rubico?
It looks like you can write a little less to do the same thing with rubico. Is the rubico version more readable? I'd say it's up for debate.
What if we wanted to do multiple asynchronous things in parallel for every item of the array?
Promise.all statements, and two more
map keywords. rubico, on the other hand, has one
map and one
fork. Simpler? It's starting to look like it. More readable? Hold your horses.
What if we now want to do another async thing per item of each of the responses?
I think it's safe to say that rubico is more expressive here. I'll let you be the judge of whether something is more readable; though I will say this: rubico cuts out a lot of cruft.
In contrast to assembly, C uses natural language elements, is easier to use, and automates (but doesn't hide entirely) memory management. C makes the process of developing a program simpler and more understandable than when using assembly.
If this motivated you to see what rubico's all about,
please 🌟read on🌟