[Discussion] Project Structure & Organization Improvements

[ElecTwix]

We received some feedback regarding the project structure and root directory clutter.

Points raised:

• The root directory feels 'noisy' with many config files.
• The distinction between application logic and shared libraries isn't immediately obvious (e.g. lack of standard 'frontend/' or 'backend/' folders).
• Benchmarks are currently run via 'go run' scripts instead of standard 'go test -bench'.

We should discuss:

1. Ways to reduce root clutter.
2. If folder naming can be improved to clarify that the core Go logic is a shared library consumed by CLI/Desktop.
3. Standardizing benchmarks.

[Tomaszal]

Regarding root clutter - we could move some of the files into a config folder for tools that support it, but unfortunately there's not too many that do. There have been some discussions around it in the JS ecosystem, but it seems there was not a lot of progress on that:

• the creeping scourge of tooling config files in project root directories nodejs/tooling#79
• https://dot-config.github.io/
• https://deno.com/blog/node-config-hell

[Tomaszal]

As for folder naming and structure - I don't think we'd want to change this too much, apart from maybe improving some names to be less ambiguous (f.e. "client" and "db" could maybe be more explicitly named). However, it would probably be good to add some documentation about the package architecture and structure, which would help people understand the project layout quicker