ClippyCloud VS gramatika

Is that extreme example of splitting? To me it works fine. From couple years I'm working with Vue, Nodejs, Typescript, Ruby on Rails and there this file setup you showed me are totally normal and gives good readability if made properly. I.e. look at this repo. It's kinda extreme to me. Not only about file splitting but also tests for any html component etc. Here are example graphlql api structure I've written for my projects in NodeJS + Fastify + Mercurius (GraphQL server). And you'll probably understand basic purpose of it and what should be found where. That's why I'd like to do same in Rust.

I wrote a lexer generator. It's pretty limited and poorly architected tbh, but feel free to have a look: https://github.com/dannymcgee/gramatika

I'm a huge nerd for programming languages and rendering, and to that end I've been putting together a general-purpose parsing library inspired by syn and using that to power a language server for WGSL.

I'm probably in the minority on this one, but I really hate writing verbose, repetitive code, so I freaking love macros. I will frequently use a one-off macro just to make something like a dispatcher function easier to read by cutting down on all the pomp and circumstance. I'm also working on a small crate that makes heavy use of proc macros, which I've already gotten a ton of mileage out of since it allows me to spin up a serviceable lexer with just a few lines of code. A lot of people really dislike macros because the source is hard to read and they're onerous to debug. They're not wrong on either of those points.