3836293648

4 ms·

31.
by 3836293648 4mo ago
They literally are. This is not a case of extra fine tuning, this is a case of enabling or disabling smaller guard models you have to go through first before you get to Mythos.
32.
by 3836293648 4mo ago
Didn't he get the nobel for NNs? LLMs came much later
33.
by 3836293648 4mo ago
They don't throw away the weights. If it gets worse just use an older model.
34.
by 3836293648 4mo ago
No, he didn't? He predicted that third parties would donate tokens to FOSS projects, not that the labs would. One is PR that started ages ago, the other is a reasonable prediction of where the world is going.
35.
by 3836293648 4mo ago
Really? I had a terrible experience with 4.7-flash. Qwen-3.5 is still the best local model for me. (3.6 pushed VRAM usage just out of 24GB and then you're not using a consumer GPU any more)
36.
by 3836293648 5mo ago
> I've not even heard of compile times being significantly slowed by type checking. Look at Swift. But yeah, Swift is the only language I've ever heard having compile time issues because of the type checking.
37.
by 3836293648 5mo ago
Types always have to be checked. Either at compile time or at runtime. And if you're weakly typed you still check them to see if you use normal or backup behaviour. If you're statically typed you can remove the actual check from t
38.
by 3836293648 5mo ago
Because the BEAM has much more to it than a terrible dynamic type system?
39.
by 3836293648 5mo ago
No, significant whitespace today is still terrible, coming from Haskell, Python and Go (newlines that break expressions unreasonably)
40.
by 3836293648 5mo ago
You are entirely right here, you're also incredibly rude. Please don't bother replying when the only thing you're actually doing is being condescending and spreading negativity
41.
by 3836293648 5mo ago
If you're not shipping faster it's meaningless for the company . And if you are, it's bad for the employee . Is what the above comment actually said.
42.
by 3836293648 5mo ago
I hope this will never be the case. As long as we have personal vehicles they should be personally controlled. Self driving cars is such a waste of everyone's money. Cities should all have better public transport and out in the middle
43.
by 3836293648 5mo ago
It's a set of asserts that are a part of the type signature. Requires are asserts on the inputs, ensures are asserts on the outputs. Depending on your backend you either ignore them, check them all of the time, some of the time, or hav
44.
by 3836293648 5mo ago
Price to performance?
45.
by 3836293648 5mo ago
The typescript compiler is a typescript app. Or was, I guess
46.
by 3836293648 5mo ago
Then don't go interact with the social club? If you want to interact with their project, follow their rules on their terms, otherwise just grab the binaries and don't stir things up.
47.
by 3836293648 5mo ago
> X is a terrible language because of the lack of static analysis available. > (Mocking) Yes, that's why we should go back to Y with even worse static analysis. Sure
48.
by 3836293648 5mo ago
That applies to everywhere except for like the Vatican or Monaco. The US is not special
49.
by 3836293648 5mo ago
Everyone doesn't use tokio. Almost everyone on desktop/server uses tokio, with a few macos specific things wrapping grand central dispatch. But the embedded world is full of custom runtimes.
50.
by 3836293648 6mo ago
This needs to have DOS builds available. Is it performant enough for 90s hardware? I know the rust compiler itself isn't really.
51.
by 3836293648 6mo ago
Not technically. But that's not the issue. The issue is that trait resolution and imports are treated inconsistently and that is a mistake. Compare to [this]( https://play.rust-lang.org/?version=stable&mode=debug&amp
52.
by 3836293648 6mo ago
Merging autism and aspergers was not a mistake. There wasn't at the time enough science to separate them. There are separations to be made within autism, absolutely 100%, but the separations they hade made were also definitely 100% wro
53.
by 3836293648 6mo ago
Oh, yes of course. Switching to String and it works as I expected. I thought the builtins were defined in core and reexported by the prelude (they are defined in core, they're just implicitly in scope anyway). But I still think expecte
54.
by 3836293648 6mo ago
Don't they get promoted to short?
55.
by 3836293648 6mo ago
Oh, wow. I am wrong. So much of the rust community must be wrong as this is commonly mentioned when discussing breakage. This is awful. But on the other hand, it could be a bug as the trait resolver is commonly mentioned as the buggiest par
56.
by 3836293648 6mo ago
Either you used nightly, explicitly non stable, rust instead of the default stable rust; or you used dependencies that have been yanked due to security issues; or you didn't commit your lockfile and implicitly upgrades everything by ha
57.
by 3836293648 6mo ago
Strip_suffix won't break with new compiler versions. Anything explicitly imported takes precedence over the prelude, or else everything is a breaking change and would have to wait for an edition.
58.
by 3836293648 6mo ago
It's insane that this is going into an LTS. It's the kind of experiment I'd expect them to play with in a non-LTS and revert in LTSes until it's fully usable, like they did with Wayland being the default, which started i
59.
by 3836293648 6mo ago
No? It's not because it's a cache, it's because they're scared of letting you see the thinking trace. If you got the trace you could just send it back in full when it got evicted from the cache. This is how open weight m
60.
by 3836293648 6mo ago
No, I'm claiming your source is outdated. It has become an old people thing now

More ›