HN user
Become healthier through diet and exercise. Don't worry about your weight. Gaining muscle through weight lifting will increase your weight. Cardio exercise will increase your weight due to increasing blood volume.
Just cut the sugar calories. You probably eat the appropriate amount of calories for you, just eliminate the calories you drink.
Why not both? LLMs are hilarious when they aren't trying to be funny. They are pretty bad at jokes normally, but when LLMs hallucinate more than normal it has the right amount of absurdity to be funny.
Another great feature of Tcl for writing servers it that you can reload the code while it is running and keep all the state and connections open. Code up/bootstrap your server while it is running the whole time. Sure this is a security nightmare, but it is fun to code.
Most of your steam games will run on linux with proton.
I worked the Rete algorithm into ansible-rulebook for condition matching events. https://ansible.readthedocs.io/projects/rulebook/en/stable/r... This does use Drools underneath now.
There will be a lot more competition in five years when the cost of running a company is much lower.
I have half a MUD that uses TTS and speech-to-text as the interface with LLMs generating the content and a database keeping the context. It works surprisingly well.
Meta's customers are advertisers. Their tools for advertisers are the best in the business. Facebook and Instagram users are the product.
If you had a little more software in your car it could automatically remediate the issue and you'd be on your way with no repairman involved or at least tell the repairman exactly what to fix. Maybe you could fix it with the step-by-step workflow on your console.
Oh no. I wrote a mini-language with a PEG parser and an AST. I guess I'm a compiler engineer now.
You're welcome. I hope that you find it useful.
Ansible Kernel calls ansible-playbook on a specially constructed playbook. Ansible Kernel constructs a playbook with a two tasks in it: 1. wait for the kernel and 2. include tasks from a file that does not exist yet. When you enter a #task cell we write that included file and then tell the wait task to proceed. The included file contains the #task cell contents, a wait task, and another include task. This continues until you stop the kernel, the playbook dies on an error, or you enter a #play cell. On a #play cell ansible kernel throws away the old playbook and make a new one with the new arguments. The exported playbook just contains the content on the page (without the wait/include tasks) and should work with ansible-playbook normally.
Try it on Binder here:
https://mybinder.org/v2/gh/ansible/ansible-jupyter-kernel/ma...