Very cool! I really like the live updates. I’ll definitely keep this in mind!
By the way, is there a name for the query language? It might be useful to have such mini-languages as libraries - a parser that produces an AST, and maybe an interpreter skeleton. The actual interpreter code will likely be specific to the app it’s embedded in, but it’s always nice to be able to “port” your knowledge of primitives to another tool.
Yeah, I intentionally kept the language totally separate – it’s there as the lang module in the repo. There isn’t a name for it, it’s roughly based on the SumoLogic query language which was roughly based on the Splunk query language.
The interpreter is currently tied a bit too tightly to the renderer which would make it hard to reuse. It’s on my TODO list though :-)
It’s true, and great to see! It might be in response to the Rust 2018 roadmap, which specifically highlights:
One of the strongest messages we’ve heard from production users, and the 2017 survey, is that people need more resources to take them from understanding Rust’s concepts to knowing how to use them effectively. The roadmap does not stipulate exactly what these resources should look like — probably there should be several kinds — but commits us as a community to putting significant work into this space, and ending the year with some solid new material.
<plug shameless=true>
For example, I’ve been doing Rust live-coding sessions where we build non-trivial (and useful) Rust crates (e.g., I recently did one on writing an asynchronous SSH client), and those have been pretty well received. It seems like we’re getting more and more Rustaceans who want to try Rust for “real things”, and that’s pretty exciting! It’s good to see the supply meeting that demand.
Love the project… although a chainsaw is a more suitable tool for slicing up logs. Angle Grinders are more for stone or metal 😍😋
Ahhh how did I miss that!!!
Very cool! I really like the live updates. I’ll definitely keep this in mind!
By the way, is there a name for the query language? It might be useful to have such mini-languages as libraries - a parser that produces an AST, and maybe an interpreter skeleton. The actual interpreter code will likely be specific to the app it’s embedded in, but it’s always nice to be able to “port” your knowledge of primitives to another tool.
Yeah, I intentionally kept the language totally separate – it’s there as the
langmodule in the repo. There isn’t a name for it, it’s roughly based on the SumoLogic query language which was roughly based on the Splunk query language.The interpreter is currently tied a bit too tightly to the renderer which would make it hard to reuse. It’s on my TODO list though :-)
There seems to be more “intermediate” level Rust posts recently. OP is a good example.
It’s true, and great to see! It might be in response to the Rust 2018 roadmap, which specifically highlights:
<plug shameless=true>For example, I’ve been doing Rust live-coding sessions where we build non-trivial (and useful) Rust crates (e.g., I recently did one on writing an asynchronous SSH client), and those have been pretty well received. It seems like we’re getting more and more Rustaceans who want to try Rust for “real things”, and that’s pretty exciting! It’s good to see the supply meeting that demand.(OP) I think it’s a virtuous cycle. I got into Rust because I read some good entry level posts that talked about how it was ready for prime time.