mertyildiran

Well if the fundamental constants or hidden variables of the universe are shifting because of his comment then it can change the outcome.

Terrance, Reinmann and Hebert walks into a bar...

Funny that it says "written with human assistance" instead of saying "written with AI assistance". So we're assistants to the machines that we have created.

Kubeshark (formerly Mizu) is an observability and monitoring tool that captures all the network traffic inside a Kubernetes cluster, including ingress, egress and across containers and pods.

Kubeshark can even capture and display the encrypted (TLS) traffic using various Linux kernel technologies. It supports a wide variety of application layer protocols and RPCs like gRPC, GraphQL, etc.

Kubeshark is open-source and free to use. It has a large userbase.

We recently renamed the project from "Mizu" to "Kubeshark". Please give Kubeshark a shout-out. It's a carefully crafted tool by a handful of Kubernetes enthusiasts for Kubernetes enthusiasts!

First of all, thank you for your comprehensive review. I learned a lot of things from this review. For example; I didn't know the existence of the Library of Babel.

Yes, I agree with you on the fact that in the current state of LDCA, there is no meaningful evolution. I tried create a supervisor script[1] to achieve such evolution based on comparing stdout. But comparing stdout does not give me a stochastic picture of error/loss. So instead in the following days or months, I'll try to create a system that checks the values in the registers at the end of the program execution. It will pick the best offspring to go with and eliminate other offsprings.

Yes, I'm basically trying to create Artificial Life with this project. Any contributions to this project are welcomed. Feel free to open PRs and issues on GitHub to discuss and contribute.

[1] https://github.com/mertyildiran/ldca/blob/master/simulate.py

Yes, you are correct. The very intuitive approach we took on decision making is the key point of the language.

I came up with this idea of designing a language with no "if" after dealing with various untestable codebases for years. They were literally untestable because of the technical debt caused by the extensive amount of "if" usage in the function bodies, especially the guard clauses makes it 1 "if" minimum for almost every functions. So at the end I have exhausted because of the if(s) and decided to create a language that forces you to have minimum technical debt.

Thanks a lot for finding the way Chaos language handles the decision making, interesting.

There are a lot of alternative keywords, especially for type safety and function definition related keywords, with the purpose of attracting programmers from other programming languages and making them feel at home. At least that was the intention.

The language at an early development stage. So "How immutable should variables be?" is open to discussion. You might want to open an issue and propose this in the issues section: https://github.com/chaos-lang/chaos/issues