nomennescio

Will check a `load-all` factor.image. First need to create one. > I'm still curious if we can get 400mb down to 100mb or less. Already compression ratio is 6.7, that...

> You can use the tools.image.analyzer vocabulary to see what’s in the image. It’s a lot of generated code, definitions, documentation. It would be nice to have a smaller footprint....

https://github.com/facebook/zstd BSD License

I've noticed that the Factor images fall roughly into 2 incompatible groups : 32- and 64-bit images. As core parameters need to be the same for both variants, in 64...

Some additional sizes for boot images (`zstd -12`): ``` 4496472 Jan 21 22:22 boot.windows-x86.64.image 545096 Jan 21 22:22 boot.windows-x86.64.image.zst 4502120 Jan 26 19:42 boot.unix-x86.64.image 545504 Jan 26 19:42 boot.unix-x86.64.image.zst ```

As for singlethreading versus multithreading versus multiprocessing; the difference is in on the one hand efficiency, on the other hand resource sharing. Having multiple Factors runnning in different processes is...

As an added benefit, if next to `=`, `` to mean 'convert word into...'. As a further benefit, the class specific words would not need to exist in many cases,...

A suggestion for the name of what exactly? You mean for all the words in math.bits? The current naming scheme is a bit unfortunate, as math.bits are not really bit...

I think this is language independent. If you look at the history of programmable computing, starting with the Turing machine, devices were used to represent two states, and multiple devices...

Note that I write "current `MATH:`", as when having multiple dispatch, it would be easy to mix `boolean` with `integer`