# BINARY! vs. BYTES! vs BLOB!

**URL:** <https://revolt.metaeducation.com/forum/t/binary-vs-bytes-vs-blob/1477>\
**Category:** Naming\
**Created:** [January 27, 2021, 12:47am UTC](https://revolt.metaeducation.com/forum/t/binary-vs-bytes-vs-blob/1477 "2021-01-27T00:47:03Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [September 9, 2024, 7:38am UTC](https://revolt.metaeducation.com/forum/t/binary-vs-bytes-vs-blob/1477/4 "2024-09-09T07:38:13Z")

</div>

> [@hostilefork](#):
>
> But if you want to talk about trends out and about in the world, it seems that BLOB! is pretty common for data of arbitrary content.

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

With the [distinction between LIST! and array](https://revolt.metaeducation.com/forum/t/any-array-vs-any-list/1384/9), 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.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/binary-vs-bytes-vs-blob/1477)._
