Markus Junginger

Not sure how to tackle this, because not everybody does `core.autocrlf = true` (e.g. I do not). And yes, current plans are to open source the gradle plugin once we...

Yes, at this point it is like you described. This functionality will be added later.

> affects only less, less or equal You're saying that "greater than" and "greater or equal" work (with an index)?

With like 97% of browsers supporting it we might be fine. Another thing to consider: if we'd have the lower-level implemented in Type-/JavaScript, we could use that for plain web...

1) interfaces, yes. separate issue? 2) According to https://stackoverflow.com/a/26428441/551269, you may be able to call TypeScript just like JS. Would suggest a prototype.

While we might not need interfaces (at least for now), it might be that we want them for the flexibility. Just tossing in that thought; more a discussion for later,...

While we'll keep the first steps quite simple, we should also discuss the target architecture we'll want in the end. To start this, I could imagine the following layers from...

Regarding moor: following their docs I landed here: https://github.com/sql-js/sql.js/ which "doesn't persist the changes made to the database", which would not exactly make a good K/V storage for us…

@zs-dima I'm sorry, that does not help. I think you lack some background on the proposed stack and the purpose of the lowest (HAL/storage) layer. sql.js does not look like...

> We rather need storage without SQL. Or, no storage and NoSQL :upside_down_face: Seriously, the idea of being in-memory only might become interesting, at least as an intermediate solution: we...