wolttam

    curl > some_file
    bash some_file

(Also, how in the world would a server be able to tell where you’re piping the response?)

Edit: thanks for the replies, that makes perfect sense

There's always going to be some nerds out there that want to make and release a model as open, and share their knowledge along the way. I'm not too concerned.

The fear you're sharing has been shared since day 1 of open-weight models and it has yet to come to fruition.

Further, regardless of what any of these labs license their model as, the end user who has downloaded the weights can still use them for virtually any purpose (synthetic data, classification, etc) as much as they want and there is no way to reasonably enforce a license on those outputs.

So even if you can't run a service using this model's weights (without a license), the weights still do provide utility for training new models with any other license.

*Edit, responding to the replies: Constraints give rise to ingenuity. Who knows how we'll be training models in the future. Hopefully in a distributed fashion, maybe with some kind of consensus-driven training dataset selection. Crowd funding, etc. There's too many people that want this, and the knowledge on how to do it is out there (many times by now)

> "A REAL, ultra-photorealistic, high-end 35mm cinematic first-person perspective..."

Real nice prompting there, Google. It also still looks like a video game rendering.

The financials depend on revenue that isn’t materializing because:

- the utility of the models is not that great (see almost every company outside of tech and even many within tech reporting “no measurable increased revenue or productivity as a result of adopting the technology”.

- China has been undercutting them hard with open-weight models that are “good enough” for 95%+ of use-cases, leaving only the hardest problems for OpenAI and Anthropic’s models, which it turns out isn’t where there is a ton of money to made (curing various forms of cancer is valuable but not “let’s dump trillions on these companies” valuable - and once their models can solve it, it probably won’t be long before others do too).

People want these models on their own hardware. People will (eventually) want these models running on robots that can do real work for them, and they won’t want those things tethered to an insecure and privacy eviscerating cloud subscription.

The money to be made is in selling hardware, as it should be.

Anthropic’s S1 still shows them not even breaking even on revenue/expenses during what was probably their biggest year of adoption, right before people started going “oh, I can do this with an open model”

I’m not saying anything new here. What are we missing?

It is namespaced under the pylance project. I also don't see any announcement here, just a markdown file.

Perhaps the post title could use a tweak

If the model is predicting syntactically incorrect tokens in code you probably have bigger issues

There is no “earning potential” to be gained in a world where you simply ask machine to do X and it does it for you.

We might not quite be there but we’re trucking towards that point at full speed.

Xiaomi-Robotics-1

Because Opus 5 is the best at their benchmark.

It's a bit fascinating to me how all of these labs have rolled their own (it sounds like) completely unique RL environments.

I wonder how much the industry will centralize around a few key patterns, and if we'll start to see some RL framework projects gain traction and be used by the bigger labs

P.S. weights by November 4th

It really is the determinism aspect for me. Okay, it’s programming if you sample at temperature 0 with a fixed seed on a fully deterministic inference stack and you have made your prompts the artifact that you iterate on (repo full of natural language that “builds” into the running software it describes with the use of the LLM sampling at temperature 0)

The fact that Grok refused is hilarious.

> Podman, by default, uses crun as the container runtime

Not anymore, they switched to runc (but it can use any OCI compliant runtime)