Actually no, sat down and wrote it out. Did some AI proofreading but applied the suggestions by hand. Would be interested to hear what parts were painful.

I tried using Orion mobile for months but I just kept running into so many UI bugs that I had to switch away from it :(. I love Kagi, but Orion just feels unpolished right now

I still use it because I like how easy it is to use extensions on iOS but definitely agree that there are a lot of UI bugs. Listing the most prominent ones just in case the dev is around:

- At times, the search bar text disappears and the "refresh page" icon is left aligned (instead of right aligned).

- When a link has an associated app that can open it, Orion opens a modal that asks whether you'd like to open it in-app or continue on the browser. However, sometimes it immediately opens the app and shows the modal once you navigate back.

- When using a custom search engine, you can no longer use the search bar to edit your query and it just shows the url.

Same for me. It was just so full of glitches - UI not responding, refusing to scroll, menu being inaccessible, pages somehow producing looping pop-up dialogs about not being able to render right and blocking the rest of the app...

Interesting, I get occasional glitches, mainly around placement of the text bar, but they are visual and don’t affect behavior. I’ve been living on the browser on iOS for about a year now and I enjoy it.

I did eventually have to abandon the desktop one about a year ago though due to bugs. It seems like it’s better now though.

I have quite the opposite view here. I have switched from Firefox to Orion on my iPhone a year ago (potentially more?) and had a great experience.

Sure they are sometimes some buggy UI controls (like the focus not working), but for the most part, the experience has been smooth.

Did you try to report the bugs when you had some? Maybe this could help everyone else using the browser.

> Did you try to report the bugs when you had some? Maybe this could help everyone else using the browser.

I rarely bother submitting bugs on closed source software. Submitting bug reports takes a lot of time (to do well) and I feel that it often leads to nothing.

In my case, all the bugs I ran into were things that developers should also run into through normal use of the app (freezes, weird search bar bugs, scrolling stuck, etc)

I have been running Orion mobile on my iPhone for 3 or 4 years. Occasionally scrolling up or down would get stuck, but I haven't experienced that in a long time. I tend to do simple things though. Read HN, NYT, reddit, webtoons, and that is about it. The native ad-free experience is top.

that was my experience as well. in my case, i kept running into issues with using chrome plugins.

ditto, it’s just not stable or usable at all for me.

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

Not a great summary of the article. It just barely touches on reverse repo lending which is the core of the linked article.

This sounds like the output of a LLM. No actual reasoning or thought.

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.

[1]: https://news.ycombinator.com/item?id=34540419

> It's got some rough edges

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):

    astunparse = super.astunparse.overridePythonAttrs
            (old: { buildInputs = old.buildInputs ++ [ self.wheel ]; });

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.

On my phone (iOS) I can’t seem to get any of the samples to play.

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!