Boosted by glyph ("Glyph"):
jonny@neuromatch.social ("jonny (good kind)") wrote:
to be clear - what does this one extremely simple feature reflect for the user?
In the "traditional way," the user can go to a website and see an example of how to do this themselves with information that's derived from the actual values used in computation. cool.
In the "LLM way," the user has no agency, can't see why the LLM might fail because they can't see the system prompt is directly feeding in the metadata about the available fields and thus has no idea that the model is capable of being wrong about its own fucking code and so they are shown wrong fucking values.
So the cost of transforming something to the "just prompt it" modality is "it being completely fucking wrong" even when that thing is literally just a feature that refers to the program state that is entirely owned by the fucking program" - to say nothing about how that pattern of development being recursively applied to the develpoment of the tool causes it to be fucking wrong as a matter of practice.


![screenshot of github comment thread shushtain 2 days ago Yeah, completely dropping support for v0.11 on day 1 of v0.12 release by removing a single check is insane. If the problem is keeping up with constant updates to parsers, there should be at least some grace period. I'm basically cut off from updates until Arch package passes all safety checks. Just because of the "insane burden" lifted by this commit: c82bf96 clason 2 days ago Maintainer OK, I kept my silence because I didn't want to deal with this but: This plugin has officially required Nvim 0.12 for a long time; since people apparently can't read and kept opening issues and PRs about Nvim 0.11, I was forced to make 0.11 a hard error (the dropped compat shim was incidental). And it bears repeating that this plugin is still experimental; there's a pinned issue about the roadmap. If and when we hit stable, then there will be releases. For now, just pin to whatever commit you want and stop upgrading. (People like you are the "insane burden".) shushtain 2 days ago No, it's actually this plugin's docs and commit messages that treat people like burden. I have defended your position on master-main switch, but the current statement is simply not true: the plugin worked in Neovim 0.11 up until that very commit. Unlike you, I try to stick to what people do, not what people are. So please, do go switch to something that doesn't require interacting with people. [...] clason 2 days ago Maintainer OK.](https://files.mastodon.social/cache/media_attachments/files/116/353/418/153/767/462/original/7dd403821d81575d.png)





