Areading314

> Java 27: “We’re finished, we’re tired.”

Seems about right

The central point, that working with agents is some tried and true variation of existing processes, is incorrect.

Managing agents has some similarities with EM and program management but a whole lot of other dimensions like token use, avoiding drift, successful concurrency at scale, variations in prompting, testing, evaluation, etc., not to mention that the agents are hyperintelligent coders with zero common sense and a penchant for extremely literal interpretation and ultra-verbosity.

New programming languages? Doesn't seem needed anymore

Is there a list of useful science/inventions that this project has led to?

I think explicit management of the event loop and the associated potential for grievous bugs has a lot to do with it.

Construction costs have been outpacing headline inflation by a huge amount. This has accrued to costs of repairs easily exceeding 20-30% over a few years ago.

I applaud the aim to make lean and fast websites, but the lack of timer and drag+drop on this game makes it unusable, so I think this actually makes the reverse point -- one should not put non-functional requirements ahead of the function of a product. In other words, this was not a good compromise.

* Bloomberg terminal

* Vim ;)

K8s is an abbreviation of kubernetes K3s is an abbreviation of k8s

Ah, that makes more sense -- it might be a good idea to integrate with the upstream library as a submodule rather than lifting the actual .cpp/.h files into the bindings repo. That way people know the upstream C++ code is from a much more active project.

Despite my snarky comments, thank you for contributing to the python ecosystem, this does seem like a cool project for high performance URL parsing!