squashql VS obsidian-releases

I am building a SQL like query engine with a typescript query builder. It aims to provide multidimensional query capabilities (think about olap cube). The query engine is compatible with several databases (sucks, clickhouse, bigqueryx, snowflake...). Our users are developers building decision making applications. They are using for instance duckdb to develop locally their application and use a cloud provider in production. Here's the link https://github.com/squashql/squashql. Feel free to ask me any questions.

I am building a sort of SQL query engine compatible with several databases (bigquery, snowflake, duckdb, clickhouse, spark) in order to add more power to the SQL query language bringing multi dimensional capabilities to SQL (and more). The project was released few months ago and available on GitHub https://github.com/squashql/squashql

I am building squashql-js for a slightly different use case (database agnostic SQL-like Typescript query builder among others) but Kysely and pypika (for Python) have been a great source of inspiration.

https://github.com/squashql/squashql/blob/main/documentation...

The closest editor that follows our first principle is Obsidian editor:

The solution was already installed on both my computer and my phone: Obsidian.

> why does open source need to "win"

Open source does not need to win.

But your ability to be in control of your computer needs to be preserved. A proprietary fridge cannot control your diet, while a proprietary App Store can control what software you install on YOUR phone (unless you live in EU, hello DMA!). The tail wags the dog, so to speak. Proprietary software has also been shown to break user workflows or remove functions in an update while leaving users with no choice whatsoever.

One alternative to having open source win is to ensure software must come with a robust warranty and other assurances you expect from the things you buy. EU's CRA will make software vulnerabilities in WiFi routers covered by warranty, for example.

You can also ensure robust and interoperable data storage options. For example, https://obsidian.md/ stores all notes in Markdown, not holding the data hostage in case users will not like how future versions will work. GDPR actually has a provision for data portability (Art. 20), but it does not seem to have a requisite effect on the industry yet.

And until the above issues are solved, open source remains the best way to ensure that a software tail cannot wag your computer dog.

[2] https://obsidian.md/

So I've had my fair share of personal websites and blogs. I have built them on stacks ranging from the most basic HTML and CSS, to hosted frameworks like Wordpress and Laravel, to the more modern single page applications built in Vue and React. For a simple content blog I think you can't go wrong with a Static Site Generator though. These days I am almost exclusively writing everything in Obsidian. Which is great because its all in standard markdown format. This allows for a really neat and easy content publishing workflow.

Consider making an Obsidian[^1] plugin, or writing to Obsidian-compatible Markdown files :)

[^1]: https://obsidian.md/

Obsidian is a writing application created to allow for offline / private note taking in markdown format, in an interface that looks a lot like our regular programming IDE. It is very flexible, with a good collection of community plugins that you can use to customize Obsidian to your heart contents.

Obsidian support via our Obsidian Plugin