-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
**User story**
In #1128 and the recent meeting, I proposed breaking up our current data types into several simpler data types (see [diagram](https://docs.google.com/drawings/d/1dxDrtjm0Dax13czJbUUD…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…
-
```
What steps will reproduce the problem?
1. Wide, sparse tables are awkward to explore because most columns are empty
(or contain just one item). You have to keep scrolling right and left to see
…