It is true that the current neatify scripts to not aim to replicate rustfmt. My personal goal is cross-language standardization, where reading Java, TypeScript, or Rust all follows the same visual "layout".
Of course, I totally understand that people often have very different ideas on formatting, depending on which tool they are generally used to. That's why I made the scripts pluggable.
If someone wants to build a rustfmt compatible formatting script in neatify, they can. The real power comes from being able to apply those same formatting rules to other languages to get a consistent result across a polyglot stack.
The age of MCP is not unlike that of microservices where the primary feature was polyglot implementations. Except now there is the added angle of AI generation.
The goal is to allow absolute freedom in formatting style across a broad range of syntaxes.
I absolutely love the tree-sitter library, I use it in a number of projects. One of those projects is to create syntax-aware embeddings. Currently the rules in that systems are still query based and lack flexibility when it comes to defining context. I'm actually thinking of taking some architectural ideas from Neatify's Rhai-bridge to make my embedding extraction more flexible as well.
Of course, I totally understand that people often have very different ideas on formatting, depending on which tool they are generally used to. That's why I made the scripts pluggable.
If someone wants to build a rustfmt compatible formatting script in neatify, they can. The real power comes from being able to apply those same formatting rules to other languages to get a consistent result across a polyglot stack.
The age of MCP is not unlike that of microservices where the primary feature was polyglot implementations. Except now there is the added angle of AI generation.
The goal is to allow absolute freedom in formatting style across a broad range of syntaxes.
I absolutely love the tree-sitter library, I use it in a number of projects. One of those projects is to create syntax-aware embeddings. Currently the rules in that systems are still query based and lack flexibility when it comes to defining context. I'm actually thinking of taking some architectural ideas from Neatify's Rhai-bridge to make my embedding extraction more flexible as well.