bberrry

5.6 Sol is extremely good, definitely Fable level from my experience. With 5.6 Sol being half the price and noticeably faster I think Anthropic will find the coming months unpleasant.

If you want your company's code to be used in training, then yes.

My favorite stack, Kotlin with Spring Boot. A real delight to work with

They are definitely cheating, they have crafted prompts[1] that explain the game rules rather than have the model explore and learn.

1. https://github.com/symbolica-ai/ARC-AGI-3-Agents/blob/symbol...

The old stuff still being accessible is the only way I find the stuff I'm looking for

Do share examples and evidence, by all means.

75 minutes to diagnose what's failing is not.

Tidal is using a revenue share model, just like Spotify. A higher per-steam payout just means users on Tidal are listening to less music than Spotify users.

So is Netflix. Silly take

Those of you surprised to see Java so prominent, where have you been all your careers? 10 people startups with nodejs backends? You must have been entirely shielded from enterprise software companies.

Have you had any significant issues with scams? In my home country we have a huge problem of scammers calling and tricking elderly people to transfer their savings with a similar instant payment app.

Finally I can recommend virtual threads without significant caveats.

Mine had iteration count 1. I was livid when I found out. Fucking amateurs taking on the responsibility to safeguard everyone's passwords

What evidence is there of preservatives having detrimental effects on humans (in the doses we actually receive)?

Kotlin does improve on the primitives/boxed situation. For example in Kotlin there is just "Int", not both "int" and "Integer". The language will use stack-allocated primitives wherever possible and boxed objects when necessary (in Collection generics or when you've explicitly opted into nullability). The distinction is abstracted away from you as a programmer. Sounds like the consistency you want.

This is the biggest issue with investing in Kotlin IMHO. The stewards of the language have a conflict of interest in democratizing the tools.

try statements being expressions is also especially lovely

Can't blame Kotlin for that. And it's a very minor sin frankly.. set-and-forget.

Depends on what you're writing I guess (as always). I write backend services and if there is an exception thrown, generally the whole request is forfeit. So a top-level exception handler is all that's needed.. no checked exceptions ruining my lambdas or streams like in Java.

Personally I love the esthetic and hope they never change it.

You can't spend 20 minutes charging on the occasional 5 hour trip?

Funny, their technique is to completely ignore the nature of the task and ask for the smallest possible number you will accept.

I'm so incredibly thankful that there are people like Pavel and Chris putting effort into articles like this. You are truly the best of us

It can't handle YouTube ads unfortunately.

I would hope it's not the authentication team's systems that are logging payloads with passwords.. they should definitely know better. Presumably it happened some infrastructure component owned by another team.

I don't understand these benchmarks at all. How could it possibly take virtual threads 40-50 seconds to reach maximum throughput when getting a number of tasks submitted at once?

I don't think that's correct. ThreadLocals should behave just like on regular OS threads, the difference is that you can suddenly create millions of them.

You used to be able to depend on OS threads getting reused because you were pooling them. You can do the same with virtual threads if you wish and you will get the same behavior. The difference is we ought to spawn new threads per task now.

Side note, you have to specifically use InheritableThreadLocal to get the inheritance behavior you speak of.

If you are already in a reactive framework, why would you change to virtual threads? Those frameworks pool threads and have their own event loop so I would say they are not suitable for virtual thread migration.

> Hiring on merit will be a permanent policy at Scale.

Isn't this what everyone tries to do?

You seem to have missed that meritocracy has recently become a bad word and undesirable in some political circles.

You mean _invents_ details.