I'll second the enjoyable parts of Neovim shared above, and add a few more of my own: - vi uses most of the same default keybindings, which is available across most distros (in busybox). Meaning I can use the same keybindings in a docker container, appliance server, etc. - With the conform[1] plugin, I can add any CLI code/text formatters that might not be available as a vscode extension. As long as it takes a file/stdin and outputs a file/stdout.

[1] https://github.com/stevearc/conform.nvim

over 50% less the price, I see the JetKVM at $90 USD, but PiKVMs range from $230+.

I found PiKVM useful as I already had the hardware laying around, so setting one up didn't cost me anything, and its a pretty good experience. If I were to buy new though, not sure I'd find it worth the cost for my use case.

This was great and a really unique idea. In thinking about sharing it with people who don't have a dev background, changing some of the situational descriptions could be helpful: "vendor kickoff", "standup", etc

Another reply had some good insight: https://news.ycombinator.com/item?id=45368092

Great read. At my last job, everything was quite monolithic when I joined, and I led the crusade to move to more segmented, module-driven development. There was definitely a period where I eventually swung too far in that direction and only realized it after a dependency issue led to an escalation.

Hopefully someone can learn from this before they spin a complex web that becomes a huge effort to untangle.

Dropping ICMP traffic isn't super uncommon to try to mitigate low-complexity DoS attacks, I also cannot ping irs.gov.

I can get to www.irs.gov in my browser though.

It's also a great way to introduce hard to debug network issues since PMTUD also relies on ICMP, and is basically mandatory for ipv6.

Its a custom license apparently, but its public domain for the US.

https://github.com/IRS-Public/direct-file/blob/main/LICENSE

Was required to be open-sourced from the SHARE IT act. One of the most common-sense bills in a long time.

https://www.congress.gov/bill/118th-congress/house-bill/9566

I don't think the second half of your comment is accurate.

Works created by the federal government have always been in the public domain, i.e. ineligible for copyright protection. The SHARE IT Act has nothing to do with that. (Of course, government works may be protected or restricted in other ways, such as classification.)

The SHARE IT Act doesn't say anything about releasing software publicly, nor does it say anything about open source licensing. It applies to software that is created by the federal government itself or by contractors It requires the source code to be made available to the government and stored in an appropriate source code repository, such that it can potentially be shared between agencies.

Might be worth opening an issue, the project states it aims to aggressively cache dependencies: https://docs.astral.sh/uv/concepts/cache

Maybe that functionality isnt implemented the same way for uvx.

You could try this equivalent command that is under "uv run" to see if it behaves differently: https://docs.astral.sh/uv/concepts/tools/#relationship-to-uv...

I haven't been able to find any kind of rhyme or rhythm to it, so I don't know how to explain when it happens or how to better debug it for a bug report.

based on their company about page, looks like Leta has existed since 2023

https://mullvad.net/en/about

Its a variant of the orchestration software. I'm not sure this is as enticing as other permissive licensed projects like OpenTofu/Ansible (push) or OpenVox (pull) based on available documentation/market share.

Of note, this is not affiliated with Chef itself [1], but looks like Chef has blessed it [2]

[1] https://cinc.sh/disclaimers/ [2] https://cinc.sh/blog/cinc_client_is_live/