You should try using a larger model like llama-35b or even GPT-3 for the feedback. That way you might be able to condense knowledge from these really big models into a smaller model
As stated multiple times in the article, making taxes easier for the average person does not stop people with complicated taxes from getting help.
My taxes are simple; my family’s taxes are simple; most of my friends taxes are simple. We don’t need Inutit making our taxes more complicated than they need to be. I’d rather have free simple filing be done with my government. I don’t need Intuit getting between me and my government. And if I ever have really complicated taxes, I’m sure TurboTax will still exist.
Every time I see AMD in the news I hope to hear that they’ve invested in a RISC-V cpu. I would love a real desktop or professional class RISC-V chip made by an American company.
This article is most likely in response to “DataDog asked OpenTelemetry contributor to kill pull request” [1]. Though it fails to make a real apology or explain their actions.
I've recently been looking really hard at NixOS as a possible next-step. (I use Manjaro and am particularly interested in ways to keep my Laptop and Desktop in sync)
I've heard that the documentation can be pretty lackluster at times. Are there any other rough edges I should know about?
I'd say it's really about the documentation, including "unofficial" documentation like bug reports and SO questions. Part of why Ubuntu is so popular is because there's enough of a community that whatever issue you hit, someone's probably already hit it before and asked about it on SO, where it has a highly upvoted answer that fixes the issue and explains it. That's also why NixOS seemed like a better choice than Guix to me.
One thing I ran into was setting up a Python project using poetry2nix. Mostly works great, but then you sometimes get inscrutable error messages. I had to copy this into a shell.nix file for reasons that aren't entirely clear to me (and I had to hunt it down from https://github.com/NixOS/nixpkgs myself instead of finding docs or a bug report):
One non-documentation issue I've hit is that even when using the stable channel, you live much closer to the bleeding edge than a distro like Ubuntu. I updated my system to the latest packages, and then my wifi wouldn't work after waking up from sleep. Turned out to be a kernel regression that was fixed a few days later in a patch update. Everything was fine again, but it's not something you'd run into with a more conservative distro. Similar issue with the latest Gnome breaking extensions for a while before they got updated.
> Are there any other rough edges I should know about?
I think the easiest to encounter is that programs downloaded from the internet might not 'just work' for various reasons. (e.g. because they're linked against libraries in more typical locations, or because the code hardcodes paths like /bin/bash or /bin/rm which NixOS doesn't provide by default).
So, when programs like minikube like to provide a nice UX by downloading helper executables, it won't 'just work'.
Solutions vary from "someone already packaged this, it's not a problem" to requiring deep understanding of what you're trying to do.
It's not trivial to package/run stuff that isn't prepackaged (unusual given that NixPkgs is enormous).
But not too hard either, I authored several official packages within a few days of migrating to Nix. It's only difficult if the build process is a bit uncommon or ugly.
The hardest part about NixOS is figuring out what to learn, and in what order.
For development, not all languages have the same “support”, tooling. This is sometimes inherent in the given language’s dependency management or popularity.
Same with Safari on MacOS. They're WAV files so it's not a format issue. I can see that the network request fails in the inspector but that's the extent of the debugging work I'm willing to put in this morning!
Rust forces you to do a lot of thing correct. But when learning the basics of programming, "correctness" is one of the least concerns. At that phase, it should be about getting an idea into a somewhat working state ASAP. Rust, while I love it, isn't great for that.
