708145_

Lombok was never relevant, and using Jackson’s or other frameworks’ undesirable runtime sorcery does not make Lombok any more sound.

Adding a pile of annotations throughout your codebase, often five stacked on top of one another, which generate behavior that is not locally visible, was never a sane trade-off for saving a little boilerplate.

After the 6 month Mythos scare campaign it hard to take him serious.

All of the version 5s have been truly disappointing.

- Fable, nerfed or whatever, too expensive and not fully included in subscriptions.

- Opus, neurotic (excessive) slop machine.

- Sonnet, way too token hungry, cost much more than 4 series.

Their almost daily outages does improve the experience. Anthropic really have messed up this year.

No shit.

Is Taalas' approach scalable to larger models?

Fully agree, responsible parents should not allow their kids (including teenagers) to use Shorts or TikTok. It is a shame that YouTube does not support blocking that crap. It is obvious "Don't be evil" is not Google's motto anymore.

_squash merge_ to main ofc.

I see no need to ever rebase manually, just merge on your branch and always fast-forward squash merge (only sane default) with GitHub/GitLab/whatever.

Most people reading Wired probably don't know what an API is.

How about possibly also failing for being too US centered, basically being an "internet portal" but mainly for the US. Sure Yahoo where _huge_ 2000, but it was never the main goto portal in Scandinavia where I grew up using internet from the mid 90s.

Here Altavista was the defacto standard for search until Google replaced. For the portal aspect of Yahoo, there were local alternatives with more relevant material.

I don't see that Yahoo ever succeeded globally.

Of course it possible to limit the number of virtual threads. A web server can have a limit on number of virtual threads too, and queue incoming request before dispatching to to workers (virtual threads).

As other have said, this can be achieved with a semaphore and the bulkhead pattern. You can also limit the number of number of connections.

I would expect any "production ready" web server using virtual threads having some sort of limiting. That must be the case right?

It is a fine balance, and everyone that doesn't "drive the same speed" as me, frustrates me.

It is definitely not procedural.

"This seems rather … procedural. Even though we get all the nice guarantees of working with side effectful functions in Haskell, the code itself reads like any other procedural language would. With Haskell, we get the best of both worlds."

Working with the IO monad is much more complex, especially if you want to use other monadic types inside that code.