HN user

dharmab

7,780 karma

I have retired this account because it reached lucky 7777.

Posts7
Comments2,443
View on HN

On Arch, I think you could install a second "backup" copy of Arch Linux on a recovery partition that your motherboard firmware can boot into directly, and then use the `arch-chroot` program to recover your main OS. I'm sure something similar exists for other distros?

Please link to where I said not to use copyleft licenses. Check the usernames carefully.

Note that I don't agree that GPL and MIT are equivalent, or that GPL becomes a non-copyleft open source license if not enforceable. IANAL but it might revert to the regular copyright law for wherever you publish software, not an open source license.

$800 was set out of desperation. CBP was overwhelmed and underfunded, so the executive increased the de minimis to significantly higher than any other country ti relive their workload. The proper solution would have been for Congress to increase funding to maintain a reasonable de minimis (many countries use around $50-200), but that wasn't happening.

No, the argument for de minimis is that the cost to collect taxes on a $20 parcel is less than the collected tax.

Granted, the US' $800 de minimis, which was created because of a lack of funding to deal with the volume of shipping, was probably a bad decision in retrospect. But removing it entirely is another extreme.

There are good legal reasons to avoid the GPL; there are open legal questions about whether the GPL and its variants are enforceable.

I make an open source, MIT licensed piece of software. I don't accept unsolicited contributions, but I document that people are free to fork the code and provide instructions on how to develop, test and build on your machine.

Am I "fake open source"?

Note that tariff categories can be pretty tricky. For example, a board game might be imported as a toy (125%) or as a table or parlor game (20%). Both categories are valid choices, and it simply depends on which the importer specified on the paperwork.

Is your comment pro-SLURM or anti-SLURM?

I took a serious look at SLURM for my problem space and among my conclusions were:

- Hiring people who know Kubernetes is going to be far cheaper

- Kubernetes is gonna be way more compatible with popular o11y tooling

- SLURM's accounting is great if your billing model includes multiple government departments and universities each with their own grants and strict budgets, but is far more complex than needed by the typical tech company

- Writing a custom scheduler that outperforms kube-scheduler is far easier than dealing with SLURM in general

Our team switched from Docker Compose (without Kubernetes) to Tilt for a distributed systems development environment. (Think platform engineering work on a system that scales from zero to several hundred thousand instances). Our time to go from code change to testable, running code on our laptops went from about a minute to a couple of seconds, using some Tiltfile recipes to do automatic incremental recompilation on our host laptops as we edit source files, and live-reload the new artifacts into running Kubernetes containers. The reload happens so fast that we configured our environment to compile+deploy+run on save, and the new code is already running by the time you reach for the "run tests" button.

I think if you told our team to go back to Docker Compose they'd revolt on the spot haha

It explains it in clear terms:

"""

Zed's language support is built on two main technologies:

    Tree-sitter: This handles syntax highlighting and structure-based features like the outline panel.
    Language Server Protocol (LSP): This provides semantic features such as code completion and diagnostics.
These components work together to provide Zed's language capabilities.

"""

Note this is _not_ how VSC's C++ Intellisense works. The VSC C++ plugin uses proprietary features of MSVC, it doesn't use LSP.