I think the core caution is this is not type-level checks. Anything this validates still needs to be eval'd. It's not a guarantee of correctness for all inputs but does look to be a fairly light (and useful) tool to make unexpected states easier for you and others to identify.
I think they're saying that brutalist architecture feels out of context in Brisbane's weather, whereas the gloomy dreary feeling of the building fits in perfectly in the former USSR's gloom
You're entitled to that opinion, but if you give an alternative for how a big multi-storey building for large events and crowds should look then it will move the discussion forward.
If so, one benefit is you can quickly and safely mix up your set of agents (a la Inverse Conway Manoeuvre) without the downsides that normally entails (people being forced to move teams or change how they work).
> It is possible to use the language server for syntax highlighting. I am not aware of any particularly strong reasons why one would want to (or not want to) do this.
This is an area where TS excels. It also supports nesting of different languages so a query can inject other languages [0] and compose different parsers.
As an example, this can be a straight forward as a simple comment parser [1], jsdoc [2], regex [3] etc. Or in more complex cases various DSLs. Each of these can then define their own injections too. When working with CI pipelines in particular it transforms an opaque wall of YAML into slightly more manageable CST which is incredible useful for both humans (syntax highlighting) and any machine parsing you may want to do.
reply