Design for sdk core with non-reactive internal implementation + separate reactive api

[jldec]

• MESDK-50
• Continuation of MESDK-6

Context/Problem

The current sdk implementation does not scale well. Reactive solid.js effects for messages and lint reports consume excessive CPU and memory resources as the number of messages grows. (see MESDK-29 and loom)

Proposal

• Remove solid.js from the sdk core
• core should offer an async, not-reactive CRUD api for messages and a subscribe (reactive, watcher) api for events
• offer separate framework adapters for building UIs.

from https://app.excalidraw.com/s/1RmnkzJA3Ph/27CVKAmMGKx

[samuelstroschein]

Requirements that need to be fulfilled:

1. non reactive plain node, js (CLI, paraglide)
2. how to subscribe in plain JS (sherlock, web components)
3. how to subscribe in frameworks (fink [solid], parrot [react])

I recommend prototyping with those three environments

[NilsJacobsen]

Do you plan to remove framework-specific wrapper? @jldec