# Maps: Versatile Interface

**URL:** <https://revolt.metaeducation.com/forum/t/maps-versatile-interface/1465>\
**Category:** Datatypes\
**Created:** [January 11, 2021, 6:02pm UTC](https://revolt.metaeducation.com/forum/t/maps-versatile-interface/1465 "2021-01-11T18:02:59Z")\
**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:** [February 10, 2021, 9:01am UTC](https://revolt.metaeducation.com/forum/t/maps-versatile-interface/1465/4 "2021-02-10T09:01:15Z")

</div>

> [@rgchris](#):
>
> I'm not a fan of Red's specific literal notation for this

Over time I just keep getting more convinced that it is a mistake to try to introduce non-BLOCK! source notations for internally complex data structures.

A guy I know wrote a book called [**"Thinking Spreadsheet"**](https://joelgrus.github.io/thinking-spreadsheet/) [(that I offered early feedback on)](https://joelgrus.github.io/thinking-spreadsheet/ts.html#acknowledgements), where he tries to motivate techniques of working with spreadsheets that embrace the medium. He talks about how people use spreadsheets as databases:

> _"On a small scale, you can use spreadsheets as databases. Many people do, and several of our examples will. This is especially convenient when your data fits neatly into a small table and when you intend to interact with your data only through the spreadsheet itself. If your state has issued only 100 license plates, then a spreadsheet might be a good way to store that information."_

Rebol notation is like the spreadsheet; it is supposed to be light and easy. Yet the idea of turning such a medium--a _textual_ one--into something that is a generalized store for maps and objects and runtime representations of functions...and a whole menagerie of as-yet-untold user-defined-types...just doesn't hold water.

So the attempt in Rebol to turn all datatypes into renderable forms that might be LOAD-ed back...as part of a serialization...is I think a dead-end. The BLOCK! format makes sense as something that's a little bit better than TEXT! for serializing... but it's only a _little_ bit.

I pointed out [how I'd moved away from this with actions](https://revolt.metaeducation.com/forum/t/action-mold-shows-cached-name-if-available/1460), and cited this counter-example carried forward from Red:

```
red>> append [1 2] :help-string
== [1 2 func [{Returns information about functions, values, objects, and datatypes.} 
    'word [any-type!] 
    /local ref-given? value
][
    clear output-buffer 
    case [
 ...

```

To me, MAP! is another one of these instances where the strengths of the substrate are being undermined by trying to make it part of the source notation.

I think putting things in a MAP! (or OBJECT! for that matter) should box it up to where you can query it and get BLOCK!s back for serializing them...but you don't expect to mold them and paste them back.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/maps-versatile-interface/1465)._
