moljac024

How would you prove they trained on your data specifically?

It's likely much closer to that price if you don't calculate with subsidized token pricing.

But when do you get that type error?

This is the important bit.

You get it after the app is deployed, the query is ran and a result is expected.

When do I get a type error from my language if it's statically typed? That's right, before I even deploy.

Can you explain how COT is essential to distillation and why obfuscating it helps defend against distillation?

Or point me in the right direction in terms of what to read.

I'm getting a little tired of the "X is all you need" formulation

If the performance and accuracy was there, don't you think there would be a market other than memes?

I would argue models have been plateauing for quite some time now.

This is why I believe capitalism cannot survive AGI

I would like to add that for what it's worth, I wouldn't mind slower compilation times if it means we get the type system as described. If it really does end up having a significant impact on performance, would you be open to making compile-time type-checking optional instead of scrapping the whole thing?

what are the alternatives?

What's the difference?

Quite simple: you don't. Time and space complexity is an implementation detail, if you care about those things then declarative programming is out.

Funny thing, I'm working on a game right now, using react and pixi.js and I implemented something very similar to what you're describing here! It's been fun so far

Can you share a link to the reddit discussion? I tried searching but I couldn't find the post.

WSL has horrible horrible IO performance. It's really not going anywhere until they fix it, and the fix won't be easy