Twitter/X

@adxtyahq (posted 2026-05-10) recommends running Qwen 3 27B locally with a 'good…

2026-05-10 · 19:29 UTC ·@adxtyahq ·0 min read

Brief

@adxtyahq argues that running Qwen 3 27B locally with a capable CPU+GPU delivers near-Claude Opus performance and prevents your data from being used to train third-party models, citing @julienc's agreement. Kartik (@codekartik) counters that paying for Cursor in 2024 was a poor decision—bad limits, weak reasoning, low ROI—and recommends Claude Code or Codex.

Why it matters

@adxtyahq (posted 2026-05-10) recommends running Qwen 3 27B locally with a 'good CPU + GPU combo' to achieve near-Claude Opus–level performance and notes @julien_c agrees.

Key details

  • @adxtyahq claims that running the model locally ensures your data isn't being used to train other companies' models.
  • Kartik (@code_kartik) argues paying for Cursor in 2024 was a bad choice due to bad usage limits, poor model reasoning, and poor ROI; he recommends Claude Code or Codex subscriptions and says he paid for Cursor for a full year in 2024.
Source evidence
  • get a good CPU + GPU combo
  • run Qwen 3 27B locally
  • enjoy near Claude Opus-level performance on your own machine (even @julien_c agrees)

and the best part?
your data isn’t being used to train someone else’s model

Kartik (@code_kartik)

if you are using and paying to cursor i think you are living in 2024.

reasons:
- bad usage limits.
- poor model reasoning output
- bad roi

get a claude code or codex subscription they have really good usage limits, great roi and better reasoning.

ps: i paid for cursor subscription for whole 1 year in 2024.

— https://nitter.net/code_kartik/status/2053549856447504572#m