SirDimples

u/SirDimples@programming.dev
10 posts · 15 comments

Recent posts

Recent comments

Chinese open weights models are no longer niche. I think opencode were betting on the niche angle and over-subscribing far above their capacity to serve hoping most users don't saturate their quotas. But this is no longer the case thanks especially to the new deepseek v4 flash which kinda broke the economy of API resellers.

Personally, I can understand the economic complexity combined with the huge surge in demand. What I don't understand is why be vague about serving capacity and pricing while continuously tweaking usage quotas significantly without any notification to their subscribers.

free to use if you have the hardware. For this model because of its size, the main problem is the hardware availability/cost. But in general there are 3 ways to run an open weights model:

  • pay a provider like DeepSeek/OpenRouter per usage
  • buy hardware that can run it locally: actually not a bad investment for a business
  • rent hardware that can run it from a cloud provider, hardware can be rented dedicated or time-shared (so called serverless).

Everything runs well if one is patient enough 😂

But yeah, with a smaller context and carefully offloading some of the layers to the CPU, it'll run just not very fast. And definitely using Q4 quants.

No you don't need a data center, this can run on any current gaming PC with a GPU that has 16GB+ VRAM.

Although to get good token generation speed and full context you need at least 24GB VRAM.

As a dev, the divide between apps users and computer software users is fascinating. My mom can do things in instagram or whatsapp that I didn't even know possible.. but put her in front of a modern computer with a simple application and she's completely lost! I try to explain that it's exactly the same as her phone its just a larger screen/physical keybaord with different apps, doesn't seem to help.

Totally agree, I've been in the situation where a remote host is 100%-ing and when I want to ssh into it to figure out why and possibly fix it, I can't cause ssh is unresponsive! leaving only one way out of this, hard reboot and hope I didn't lose data.

This is a fundamental issue in Linux, it needs a scheduler from this century.

I like reading about OS journeys like these. Personally I ended up living with immutable fedora despite of its endless challenges, but I don't think I'll ever go back to mutable linux for my dev laptop. I feel immutability is a shield against change over time.