Such releases often show weaknesses if the intelligence index, because the models that are ranked jointly do not have the same percieved level of quality.
Sure, but having a generic LSP that works with all editors vs. an editor specific integration is still a very different thing.
It's a bit odd for the parent commenter to say "Weird post" and implying that having an editor specific feature would somehow make having an LSP that works for everyone be any less interesting.
Skills for creating good and repeatable benchmarking scripts.
A knowledge base for my research area, with tools for paper ingestion and search.
An md file to html presentation tool, there are several but this one helps me.
A review tool that splits a PR or branch intelligently into modules, and does per module reviews and global reviews for different aspects, and then summarizing that into a report. Can be used with multiple different harnesses. Written as a Python project, but build-time assembled into a single-file Python script with uv run --script shbang line.
If you modify the work, that creates a derived work from whatever copyright the original works has, not a new work that is fully copyrightable.
As the article says in the Tl;DR at the top the code may be contaminated by open source licenses
> Agentic coding tools like Claude Code, Cursor, and Codex generate code that may be uncopyrightable, owned by your employer, or contaminated by open source licenses you cannot see
Composer-2 is based on Kimi K2.5, but with extensive RL. Cursor estimated 3x more compute on their RL than the original K2.5 training run (some details in https://cursor.com/blog/composer-2-technical-report).
I used to hate on Composer 2 but I'm coming around to it. Opus for the big stuff and multi-file operations, Composer for all the small day-to-day IDE tasks works pretty good for me.
I've been prescribed slightly more than 5g per day (2 x 650mg tablets every 6 hours) for pain after an operation jointly with ibuprofen, which is scarily close to the limits.
reply