Comments by "MrAbrazildo" (@MrAbrazildo) on "REWRITING Rollup In RUST???" video.

  1. The issue with files is that they are millions of times slower than L1 cache. And this is slow in any language. So, if it's possible to not use them, or load them during an user-tolerant moment (like load screens in games), then the language comes into account.
    2
  2. ​ @LtdJorge Not exactly. Language A may force 1 to upload the entire file to the RAM, which will be way slower at 1st, to be faster later. But what if the project demands reading the file just 1x? Maybe a better approach would be to keep a pointer to the current line or character, dealing with each 1 at a time. So A and B languages deal 1x with the file, but A had to pick values later from the RAM, which is 100x slower than L1 cache. C/C++ also allow to compile the file alongside the project, as data from it, actual code. So the app won't even has to deal with files at runtime.
    1