> OpenAI is sitting on a $100+ billion ad network, incoming.
How can you make this sort of claim with a straight face, knowing that a chinese model downloaded for free from ollama works as well if not better than OpenAI's models, without costing you a cent.
> Luna is about suppressing inexpensive Chinese model competition.
I think so too. To me the so-called Chinese local models are a clear move to prevent US companies to establish a foothold and build a moat around their business. US companies are clearly invested in a strategy to make themselves relevant with claims of major impressive achievements with the so called frontier models, and how these and only these are unblocking whole ranges of applications. At the same time, they are heavily invested in pushing AI on all absurd types of mundane tasks, such as transcribing meetings and... talking to your own kids?
In the meantime it's rather obvious that, in spite of all the propaganda, frontier models are required only in ultra niche applications, whereas the ability to run any model at all already provides most of the value. In fact, US companies have been renownee by dumbing down older generation models in what seems to be a desperate attempt to make newer models look better and influence their uptake rate.
So there is no better way to take the wind out of the US AI companies' sail than pulling a two-punch attack consisting of not inly releasing capable models that refute the "only US frontier will do the job" thesis but also releasing them for free to commodities them and eliminate the business impact of dumbing down models.
> It sounds like you’re still writing code by hand and reading and reviewing code.
This is such a naive, baseless opinion.
Nowadays any AI coding assistant service supports or can be used with sub-agent orchestration frameworks.
If you are in the business of software factories, you can use the cheapest models and even local models to handle some if not all tasks in the orchestration chain.
Adding tests or executing tests (unit, integration, UI, you name it) doesn't require a cutting edge frontier model. Neither does refactoring. Neither does identifying call stacks. Neither does planning a changeset.
You have your specialized subagents, you put together a small orchestrator subagent that handles feedback loops and handoffs,and you throw it at tasks.
For the past couple of months, most of the code I write is not code per se, it's subtask orchestrators. And unlike the old "only Opus is passable" days, the cheapest models do get the job done.
> suppose you rebase a typo at the beginning of a feature branch without change ids a reviewer sees n new unrelated commits while with change ids it is possible to clearly identify which commits where changed/added/removed since the previous review iteration.
A rebase can introduce change to a commit in cases such as handling conflicts or squashing.
Also, a commit already retains it's commit message after rebasing.
> It absolutely is different. You just said the Mac Mini is upgradable but the Pi is still soldered on.
I'm sorry, you seem to be confused. Soldering is not the problem. Locking up the hardware to have hardware provisioned tier limits to block you from upgrading your own hardware is silly.
And do note, raspberry pi doesn't prevent you from switching RAM chips. The board will continue to work just the same with high capacity variants. But for some reason raspberry pi hardcodes a max memory size that prevents you from using the hardware upgrade you paid for in full.
The memory that they are placing in it has to be cheap enough to be worth their while. Which in this climate is highly probably faulty memory, or memory that runs at a different speed/spec to the one advertised to come with the RPi. That is fraud.
It's unfortunate, but given that there are so many ways you could end up with a poor quality knock-off (i.e. Amazon, sorry, 'third party marketplaces') it's probably something that skews the tradeoff quite significantly.
I guess there are more individuals who will be upset when they can't run something on their equipment as it was advertised to them than will be upset that they can't re-solder the RAM.
There are probably even fewer individuals who'll do due diligence in their own supply chain. Whilst those that suffer are technically suffering from some kind of crime / civil wrong - the chance of them getting a remedy for this is going to be non-existent.
Given the how overpriced the high RAM models sold by the RPi foundation are, I think they just can use good RAM and still make a nice profit. Like you know RPi foundation could, if they were not greedy.
This is classic gaslighting technique corporations use to extract more profit. Modifications or upgrades made by small business = fraud, OEM selling different SKUs = legitimate business.
If a small business is modifying the product and not telling the eventual customer they've done so how is that not fraud? I don't want to buy a Raspberry Pi with a memory chip from who knows who which might have not passed QA modified by people who may or may not do a decent job at soldering it to the board.
> The memory that they are placing in it has to be cheap enough to be worth their while.
You're framing this as if no reputable vendor is willing or able to source cheaper parts.
If they can get a better deal in more RAM, why can't they upgrade the boards? As a consumer, doesn't that benefit you as well?
> Which in this climate is highly probably faulty memory, (...)
That's specious reasoning and blatant fear-mongering. Consumer protection laws require vendors to support their products. If RAM is faulty, whether it was hand soldered by Eben Upton himself or hacked from a Soviet fridge, vendors are compelled to support customers. This means vendors ultimately have an interest in minimizing faulty equipment, because it hurts their bottom line.
So why can't people have the right to upgrade their hardware? I thought we already went through this battle in the 1980s.
I certainly don’t say this with the implication that I would do what RPi did if I was in their shoes or that I agree with it, but the answer to your question is “you probably can upgrade it yourself but you just haven’t figured out how to.”
Just like the idea that you “can’t” rip a Blu-ray Disc was only a matter of time and energy to thwart.
I also don’t think this device is one that has ever been sold with the expectation that it would be upgraded. It is (or was) a cheap single board computer.
Like it’s kind of funny to me how this is becoming a controversy among people who probably didn’t even think raspberry pi memory could be replaced in any semblance of an economically sensible way as of yesterday.
A unit that rpi themselves sold with 8g is different than a unit that someone else modified. The reworked unit is not sold with the disclosure that it has been hacked and no longer covered by any warranty, and the memory installed is of totally unknown provenance and quality, timing specs, failed qa, etc. Even the simple process of heating everything up to desolder & resolder temps is not free, it degrades everything, the pcb itself, the epoxy holding the traces and pads down, and all the components, and means higher chance of some failure happening sooner than it would have. But it's sold as a real rpi unit for real rpi price or a little less to beat real ones.
That is the fraud they speak of.
You should be free to do this to your unit if you like of course, and rpi has infinite other possible ways they could have chosen to address the problem and didn't have to do it this way. I'm only saying there is actually a problem.
> I can’t remember anyone earning the level of hostile treatment he did and getting kicked out.
You don't seem to be following it very closely, as apparently you failed to come across the history of abuse and hostile behavior of bcachefs's maintainer.
> There's always one of two of you rabble going "You dared defy the kernel community!
No. It's very simple. 1) do QA and follow the release cycle, 2) act like a person when interacting with other developers.
If you fail to do both, you should not be surprised that people go through great lengths to not have to deal with you and all your nonsense.
The fact that after all this time you still feel compelled to gaslight everyone with this victim mentality shows that you still have a long way to go to, and a lot of soul searching to do.
The kernel doesn't have any kind of coherent testing strategy. That was a big part of the problem, because that means the subsystems that do test their code, like bcachefs, get stuck picking up the slack for the subsystems that don't.
I was spending a lot of my time just doing QA for the rest of the kernel.
You seem to just be painfully misinformed - or you're outright trolling.
> If you can answer that question then the clankers can help you write a deterministic program for that same interaction and you only spend the tokens once.
The MCP is the deterministic program.
You need to take a step back and look at the problem you're discussing. What's exactly this MCP thing? It's a protocol to allow agents and coding assistants to access tools, services, and data sources, through a standardized interface.
It's the interface for your deterministic program. That's it.
It's easier if you started a while back shunning all human labor (including your own) in favor of fully deterministic systems. Reality is deterministic so your company or project logically can be run off a single compiled binary with formal verification of correctness for every possible scenario.
How can you make this sort of claim with a straight face, knowing that a chinese model downloaded for free from ollama works as well if not better than OpenAI's models, without costing you a cent.
reply