charm137
Joined 4 months ago
Joined 4 months ago
You can apply it to the RC2 branch so:
git clone --branch dsh-v0.2.0-rc.2 https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
git apply /path/to/dsh-v0.2.0-rc.2-to-local.patch
I'd recommend asking the harness to modify itself though (or a cloned repo in another directory) rather than applying the above.
Over the past two weeks, I have started using a locally modified version of deepseek-harness (modifications include disabling telemetry and querying a provider's model list dynamically through Openrouter, instead of relying on the pre-packaged pi-ai manifest that comes with the base code). So far, that has been the best experience - I really like the caching, tokens/sec stats that it provides. (EDIT: I don't know a lick of TypeScript but AI-driven modification of the harness is good enough for me to make these tweaks).
Sandboxing is a definite issue for me. As you perhaps know already, headless operation is often not an option in graphics/game programming which requires actual render-surface instantiations from windowing systems and then input-context handling (keyboard/mouse/gamepad) as well. So I run most development on a VM. But part of my test-suite and smoke-tests rely on runninng it directly on the host OS (which is not ideal). I'd love to hear suggestions to avoid this.
So they clearly have a product, a strategy around it and perhaps the compliance scaffolding (SOC2 Type II etc) that may be needed before actually being able to charge money for it. They also have the right brand names associated with the founding team. Execution, so far, seems good enough to create a splash, at least.
As an investor, the question(s) to ask is (in my view): "How do they make money? Will that way to make money survive?". The answer to the first: selling input tokens and perhaps subscriptions/credits eventually.The answer to the second: "Yes, but with the risk of unit revenues declining faster than their unit costs". How can they mitigate this problem: by being big (scale / mindshare etc) so that their unit costs (including for customer acq) fall faster than their unit revenues will - I believe that is the question most AI companies are trying to tackle these days. Any new competitor will have to tackle basic fixed costs (of getting started) first before even getting to the stage of having the luxury of worrying about unit-economics.
So yes, they might eventually be competed away but whoever is in their team is trying hard to make a useful product/ecosystem and that should be applauded, not ridiculed with "it's all marketing". This is way more than a simple github/huggingface-based open-source replica solution can hope to achieve without institutional backing (either big-tech or system-integrators).
What should rightly be questioned, of course, are the valuations the VCs are providing to them in hopes of passing this hot potato to a willing buyer (say a hardware maker like NVidia) - the incentives there are very well defined and depend very much on perceived TAM (which lately is on very shaky ground given how far token pricing has fallen causing, among other things, OpenAI to "miss" on the market's expectations for annualized revenues, even before they're listed!) [1]
[1]: https://www.ft.com/content/b66a9858-f8fb-46cb-b506-44bfe26fc...
Progress in humanity's knowledge now has to play second fiddle to narrow corporate interests as IPO timings near (both of which wouldn't exist anyway if generations of mathematicians hadn't paved the way for AIs to become as good as they have).
I cannot point to the reasons as to why. Many of these teams are global teams - so a lot of the same problems apply: marketing costs/timelines, release-time crunch etc. The one difference I can point to is that perhaps executive payouts are not overly dependent on total shareholder returns.