Yarn has stated before that the goal of Yarn Workspaces is to provide low-level primitives for tools such as Lerna to use, not to compete with them.

What's a primitive?

What's an object (i.e. not a primitive)?

Provides a bunch of primitives to write declarative business logic

I think the main difference between the two are the way API are served. Some smelte components need you to input big chunk of json as props, while i prefer keep props as primitive types and in the other hand give you different components tags to compose.

On one hand Solid just provides a collection simple primitives like createState, createEffect, createMemo, etc.. These can be composed to create much more powerful behaviors.

I couldn't land on how I wanted to box primitives. Should I use a getter/setter, or function form like Knockout, or explicit get/set like MobX? These were all ugly.

This was the easiest way forward until this lib integrates with the Sapper primitives.

Physical texts were already massively addressable before they were ever digitized, and this variation in address was and is registered at the level of the page, chapter, the binding of quires, and the like.