BINARY! vs. BYTES! vs BLOB!

So the number of reasons to call the datatype BLOB! has gone up.

With the distinction between LIST! and array, we now talk about a Rebol "List" as having an array (and an index, and a binding)... not being an array.

  • Not only is choosing the more "nebulous" term better for suggesting its weird additional properties... but the shorter term is friendlier.

  • The terminology helps users, but also greatly helps the implementation be clear--you know what an Array is (a "Flex"-derived flexible data Array, implemented via "Stub") and know it as distinct from a List (a "Cell")

We stand to reap a similar benefit by using Binary inside the implementation for the data store (the "Flex"-derived Binary), and calling the Cell a BLOB!

Giving users a shorter name that doesn't trip over the loaded term of "binary" seems like a clear win to me.