nithril

One thing that bothered me enough to comment on: "transcoding" doesn't seem like the right term in this context. "Encode/decode" is technically correct, but "compress/decompress" would have made the intent much clearer.

Same here, I’m not experiencing so much friction to justify looking for an alternative

Changing the port is not the kind of security measure that will consume a lot of the attacker resources

The news headline is misleading, it does not reflect the actual article title, which is much closer to what they truly did.

They did not replaced RAG because they are still using chunk and embedding. What they changed is the interface.

thank you for sharing your experience

Is there any concern/issue regarding Claude’s context limit?

For anyone that like to do DIY, that's not a work tool, that's a play tool that is coincidentally a work tool to do work.

Not off topics at all. That massive investment must be baked by something with a bigger ROI than just a chatbot.

XSLT/XPath have evolved since XSLT 1.0.

Features are now available like key (index) to greatly speedup the processing. Good XSLT implementation like Saxon definitively helps as well on the perf aspect.

When it comes to transform XML to something else, XSLT is quite handy by structuring the logic.

Appreciate your input, but if you haven’t actually tested the VSCode integration, it’s hard to compare. Reading a feature list isn’t the same as using the tool.

Not comparable.

I did test VSCode and IntelliJ on agentic, MCP, and IntelliJ is for the moment far behind.

Is your affirmation based on a testing of both plugin? I'm genuily wondering the plugin quality as IntelliJ plugin is still in beta and the VScode one not