It also pragmatically makes for fragmentation in the experience, leading to the same outcome as the current LLM debate: "works great" "not for me"
Seems like it is to me. Storing code inside yaml is pretty obviously a terrible idea and I haven't seen many systems do it (beyond Bash at least).
I don't think SQL queries in code is a very big use case and even there, any that are large enough to need syntax highlighting are probably better off in a separate file.
The biggest use case of multi-language files I've seen is Vue single file components, but in practice they turned out to be a terrible idea precisely because of tooling issues like this.
Wrong, proper tooling can infer that intelligently, or by having the user annotate it with a comment (e.g. #language=bash).
> I don't think SQL queries in code is a very big use case […]
You seem to have very little exposure to mature codebases, then. Embedded SQL without an ORM is widespread, still. You'll also find plenty of advocates on this very forum.
> […] and even there, any that are large enough to need syntax highlighting are probably better off in a separate file.
That isn't up to the tool author to decide.
> The biggest use case of multi-language files I've seen is Vue single file components, […]
…and HTML files, YAML config for CI pipelines, database migration scripts, DevOps configuration files, Postgres extensions, …
> but in practice they turned out to be a terrible idea precisely because of tooling issues like this.
> The Vue ecosystem is very well and alive; also, proper tooling is very capable of solving issues like this.
mdaniel•6mo ago
I also suspect that unlike the JetBrains feature that does this (Language Injection), VSCode doesn't understand the code it just syntax highlights it. Meaning if we take the cited example and change it to the following, would VSCode turn it red?