zxspectrum1982

At this point, more than ever, ReactOS could become a serious clone of Windows by using AI. Clones of Adobe Suite, Microsoft Office, AutoCAD and others have been produced in a matter of weeks or months. It's just a matter of time until ReactOS and wine start receiving contributions like that.

Mistake #1: using a monorepo for the whole company. Why this obsession with monorepos since recent times?

Mistake #2: Anthropic essentially reinvented Subversion.

I'm looking forward to seeing Muse devices like Amazon's devices but with superintelligence: - Muse-equivalent of Alexa - Muse-equivalent of Ring security devices: doorbells, cameras, alarms, etc - Muse home automation devices (lights on/off, smart roller, smoke detector, water detecto, etc) - Muse ring ...

I use OpenChamber as my IDE. It uses OpenCode behind the scenes. I've not really noticed a difference in OpenCode v1 vs v2 but I guess it's because OpenChamber does a great job dealing with those details.

Why does every lab producing an LLM want to have their own harness? Lock-in? Is there any other advantage for the lab?

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.

IME Composer 2.5 is too dumb for any serious coding. Grok 4.6 is twice as expensive (but still much cheaper than Claude Opus) and it does a much much better job.

What FPGA are you using? Why?

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 ;-)

I'm expecting the Taalas MSIC version to cost a fraction of that. Then probably have some kind of cheap subscription to Anthropic for updates (yes, Taalas chips can receive a certain kind of updates: they have a small SRAM).

1. How come you didn't make your implementation public? You could be a millionaire now. 2. Especially if AMD has the technology to do what Taalas does, it makes a ton of sense for AMD to acquire Taalas: remove them from the market. Make sure nobody else (Intel, Huawei, Alibaba, NVIDIA, etc) acquires them. It could have been a great acquisition for a rebirth of BlackBerry btw.

I'd gladly pay for a Claude Opus 4.6 Thinking High in silicon and use it for 1-2 years. It's good enough for many coding tasks.

Well, then it provides so little they could have not done anything at all as well. Useful stacked PRs would be something that uses AI to split my large branch/PR into smaller PRs for upstream to review. Claude does that for me.

I don't like this.

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.

KDE for Enterprise needs single sign-on support, for starters. Gnome has had that for ages.