That's because they work on the same data format, have no state, no branching, single input, single output and can be executed serially without needing to be looped. They also don't have dependency problems when installed as a distribution. If that wasn't enough, you can examine each stage by writing it to a file or piping it to display program of your choice.
If they work for what you are doing then using commands and pipes are great, because they avoid a tremendous amount of what makes software difficult.
And to think that all it took was printing off more than $35,000 per tax payer which will then be multiplied by 8x through fractional reserve banking.
The inflation will eventually haunt anyone with an income based off of a static dollar amount, yet those are the people who got a sliver of the avalanche of money.
That's an assertion, but not anything to back it up.
First, threads have been implemented as libraries many times. Second, if checks need to happen theg can happen at debug run time if they can't happen at compile time. I don't know what specifically has to be integrated into a language here that makes throwing away the enormous amount already built in other languages.
I don't understand why something like this would need a separate language. Switching languages means starting over in many ways with regards to tools libraries and semantics. A graph of tasks can be made with a cdecl library.
Zero hedge for some reason had a crazy downward spiral in their comments. Many years ago I don't remember them being out of the ordinary, but one or two years ago I checked back and they were full of insane alt right conspiracies and super pro trump adoration.
Rendering at a higher resolution makes a giant difference, even for low poly games. Old games were not only low res, but didn't have a lot of antialiasing either. On an emulator you can have resolution, antialiasing and better texture filtering.
I think the answer here is that LuaJIT is fast, and that well written native programs would still be faster, not that C "isn't well matched to CPUs". Modern optimizations are more about memory access patterns than anything else, with SIMD and concurrency beyond that. Focusing on assembly is really not the apex is used to be. For starters CPUs have multiple integer and floating point units, and they get scheduled in an out of order CPU. Out of order execution is as much about keeping the various units busy as it is about doing loads as soon as possible to avoid stalling.
I think if you are going to claim that C or C derivatives aren't actually fast and the idea that they are is due to "propaganda" then you should back that up with something concrete, because it goes against a lot of established expertise.
I don't think anyone rejected it because of sandboxing. It is a new API that would only work on windows with that installed. Learning something completely new for a niche target is not very enticing. Also, if you can write something to be sandboxed, there is a good chance it can be a web page instead.
Sandboxing also needs to come from the other direction.
Having programs be made to be sandboxed defeats the purpose. What is needed is the ability to do contain all of a program's files in one place and isolate the access to the file system with permissions for other resources.
There is a difference between attacking someone and being blunt. If you want to ban people and scold them for being blunt then you might as well say that, but to say this is attacking someone is not reasonable. It would be different if there was some sort of uniformity to this, but it seems more like a self righteous crusade to get people to apologize to you personally for not sugar coating what they say.
If they work for what you are doing then using commands and pipes are great, because they avoid a tremendous amount of what makes software difficult.