4 ms·
I take these early reports (less than a week or two after a major model release) with a grain of salt. It takes time to get to know a model, and maybe there's s
by jcheng 10mo ago
I take these early reports (less than a week or two after a major model release) with a grain of salt. It takes time to get to know a model, and maybe there's some selection bias in who's posting within 1-2 days of getting access.
(Although in this particular case, the very different knowledge cutoff makes it a lot easier to believe)
- nextaccountic 10mo agoJust for reference I was referring to this https://old.reddit.com/r/sveltejs/comments/1pkzwqd/gpt52_huge_jump_on_sveltebench/ https://old.reddit.com/r/sveltejs/comments/1pkzwqd/gpt52_hug... https://github.com/khromov/svelte-bench https://github.com/khromov/svelte-bench https://khromov.github.io/svelte-bench/benchmark-results-merged.html https://khromov.github.io/svelte-bench/benchmark-results-mer... But OpenAI was caught before cheating on benchmarks so indeed it may not mean much Also the Svelte MCP is https://svelte.dev/docs/mcp/overview https://svelte.dev/docs/mcp/overview IMO it's a must. Besides giving access to up to date documentation, there's a tool that the LLM can call that lints and fixes issues (svelte-autofixer)