I'm using Cursor (it's the only way my company allows us to use Grok) and OpenChamber (when using GPT, Muse Spark and others) and I'm happy. If I were to use DeepSeek, I'd use it through OpenChamber too.
* OpenChamber is a GUI for OpenCode.
372 karma · joined August 22, 2020
I'm using Cursor (it's the only way my company allows us to use Grok) and OpenChamber (when using GPT, Muse Spark and others) and I'm happy. If I were to use DeepSeek, I'd use it through OpenChamber too.
* OpenChamber is a GUI for OpenCode.
Since the introduction of the Cursor Token Rate, my company tells us to use Claude and Codex directly with Anthropic (or Vertex AI) and OpenAI, respectively.
https://cursor.com/docs/models-and-pricing#cursor-token-rate
I'm now using Grok 4.6 most of the time. Sonnet some times. But that's it. Cursor-native models 99% of the time. I'm pretty sure Anthropic will follow OpenAI soon in pulling their models out of Cursor because it's now a true competitor.
What exactly did you implement? A full LLM? A subset of it, which collaborates with something running on CPU or GPU? Which LLM? Why?
What language did you use to implement your thing: VHDL, Verilog, Vitis, something else? Why?
I can think of at least 10 blog posts that I'd write before I write a single line of code. Publish early, publish soon ;-)
The case where I need stacked PRs is when I have a ton of changes and I want to upstream them. I have so many changes that I have probably written code in this order: 1. feature1 work 2. feature2 work 3. architecture rework 4. docs 5. feature3 work 6. optimization 7. docs 8. feature4 work 9. security fixes 10. optimization 11. docs 12. last pass security fixes
By the time I want to upstream, I probably want to reorder my commits and generate on PR per theme (arch, feature1 + docs + optimization, feature2+docs + optimization, etc) before I submit a bunch of PRs.
GitHub stacked PRs solve none of my problems. Stacked PRs doesn't take care of the reordering of commits, it doesn't take care of rebasing changes, it adds very little on top of what I was already able to do by saying "this is PR 1 out of 7, this is PR2 out of 7 and build on top of the branch that I used for PR1/7, etc".
Hugely disappointing, bordering useless.
Most of the people saying the kind of things you say don't know how to properly use an AI code assistant.
Did Musk blindly order humongous amounts of GPUs years ago before any of us had any sense of the scale this was going to reach?
https://en.wikipedia.org/wiki/2025_Iberian_Peninsula_blackou...
My point is the way wine works today is: WinAPI --> winelib --> Linux --> x86
I. e. winelib is reimplementing WineAPI on top of Linux.
What if we could just decompile those Windows functions and recompile them on Linux, or even x86, directly?
The workaround all of these console recompilation projects use is you must have the original game in order to have the binaries (the ones you theoretically decompile and recompile, but actually you take pre-decompiled-recompiled ones by someone else) and assets (graphics, sounds, etc). For Windows applications on Linux, we could do the same: bring your own Windows, then we can decompile and recompile.
Back in the day (year 2000, until 10-15 years ago) we had Project Odin to dynamically translate Windows software to run on OS/2: https://github.com/netlabsorg/odin32
S4 provides full S3 API compatibility while requiring minimal resources and configuration.