I don’t really care for enterprise support. Incus hits a sweet spot no other solution does.

Migrated from Proxmox and manage all my VMs. Heavily use coding assistants to automatically set things up through the IncusOS CLI, translate Docker-Compose images to Incus, write bash scripts to automate launching new containers to use `--dangerously-skip-permissions` without fear of repercussions, etc.

What I love the most about it is that it's possible to manage IncusOS with declarative files, so you always have visibility into networking setups, resource configuration, etc.

Highly recommend checking IncusOS out if you have similar use cases!

Syntax example: `watchexec -r -e py uv run pytest -xvvs file.py`

[1]: https://github.com/watchexec/watchexec

He seems to have a good intuition, but he gives weak and often cherry-picked reasonings, to the point that many of his takes are completely unreliable.

For a channel called Predictive History, he made too many weirdly precise explanations and predictions that turned out to be wrong. Then, he'd look over the old failed ones to find new ones.

That being said, I'd say his macro level analysis is directionally correct, as well as his read on the incentives of each party involved. Watch his lectures, but be skeptical and double check everything he says, because he does indeed make factual mistakes... some of them are caught in the comments by other viewers, some are not obvious.

It doesn't have built-in notifications and there's no panel to see all the open sessions, but I wonder how hard that would be to add.

I've used zmx since I ran into it a few weeks ago. Uses libghostty as well. It's great because it allows me to replace tmux completely in all my ssh sessions, and can keep one session per assistant.

[0]: https://github.com/neurosnap/zmx

What would you say has changed over the past few months? I just felt like Kagi wasn't prioritizing Orion development enough, being busy with their main Kagi subscription and all.

Comments URL: https://news.ycombinator.com/item?id=46331373

Points: 8

# Comments: 0

For me, after trying the Lazy neovim plugin distro and being a long-time vim user, Helix fills a unique need:

- It's beautiful (lots of attention to detail) - It's fast (meaning: at no point did I think Helix is slower than it should) - It's hugely ergonomic (each default keystroke resonates with me and the modal selection is a boon for my brain and productivity) - It requires almost no configuration out-of-the-box

I can't be bothered to use neovim and configure it, and vim doesn't cut it. I need something in the middle between nvim and VS Code, and that's Helix for me. This might have been different had I been a vimscript wizard, which I'm not.

I don't need Helix to be more modular or UNIXy, I simply need it to keep on the direction they've taken. There's a thriving ecosystem of tools around it, and I can use it with Claude Code (by simply refreshing the buffer when there's a new edit). What else can I ask for?

Helix is a great editor, one of the very best I've ever used. As a result, I started chipping in monthly money to keep the project going.

In terms of future improvements, the only one I'm missing the most is the ability to render images or math formulas from the editor, which I hope can at some point be done through a plugin using Kitty's terminal protocol or sixel. This is especially handy when working on Markdown files for notes or blog posts.

Long live Helix.

Where are the safe levels limits to interpret test results? This would be a small addition that would make any of the results interpretable. I had to open the PlasticList website to get the baseline safe thresholds for each chemical and to do some rough approximations.