There is a common problem with Realtek ALC3306 on Linux (Kernel Bug 213159). This affects many Lenovo laptop models. For example, my fairly old Legion S7 15IMH5 laptop also does not work.

I'm not willing to pay $1000 for a fix (it's easier for me to buy a new laptop that will work with Linux), but $100 is probably okay. :)

$100 gets you a usb sound card and $90 for something else. It's not a good solution, but it's easy.

You can buy usb speakers too. Or 3.5mm speakers since the headphone jack works. Either way, way less than $100 (especially for laptop quality).

On the plus side, if the built in speakers never work, the computer won't make noise unless you've plugged in something which is a nice feature.

> Just a few months back I said I would never use uv. I was already used to venv and pip. No need for another tool I thought

Really? :)

requirements.txt is just hell and torture. If you've ever used modern project/dependency management tools like uv, Poetry, PDM, you'll never go back to pip+requirements.txt. It's crazy and a mess.

uv is super fast and a great tool, but still has roughnesses and bugs.

Pip-tools+requirements.txt helped me survive the past few years. I also never thought I needed uv, but after all the talk about it I gave it a spin and never want back. It’s just so blazing fast en convenient.

We use uv to compile requirements.txt from pyproject.toml to get the locked versions.

    # Makefile
    compile-deps:
     uv pip compile pyproject.toml -o requirements.txt
    
    compile-deps-dev:
     uv pip compile --extra=dev pyproject.toml -o requirements.dev.txt

What for? Support legacy CI/CD pipelines or something like that? uv.lock already contains locked versions of all dependencies plus a lot of other needed metadata.

> What for? Support legacy CI/CD pipelines

Yes. Azure, for instance, looks for requirements.txt if you deploy a web app to Azure App Service.

If you’re doing a code-based deployment, it works really well. Push to GitHub, it deploys.

You can of course do a container-based deployment to Azure App Service and I’d assume that will work with uv.

"legacy CI/CD pipelines"

Damn I'm getting old

Maybe. I've been programming in C++ and also in Python for almost 20 years. And I'm just happy that Python has finally started to have convenient tools for packaging and dependency management. I thought everything was cursed here, and I just hate requirements.txt. It seems they were able to overcome this curse.

pip also works with pyproject.toml. Sticking with requirements.txt is a self-imposed constraint.

It's true. msgspec has incredibly fast msgpack serialization. It's a shame so few people know about it.

JSON, too!

Funny how the author doesn't give a single link in the post. The reader has to go searching, spend time to find the things the author writes about. Well, a simple example: Awesome-Selfhosted. Is it that hard to give a link? Is it some kind of phobia or religion that doesn't allow direct links on the internet? Really? Come on, it's hypertext! Where are the hyperlinks?

The headers are hyperlinks.

Yes, the links are now in the headers. The author has updated the post.

This thing can "fix" tests, not code. It just adjusts tests to incorrect code. So you need to keep an eye on the test code as well. That sounds crazy, of course. You have to constantly keep in mind that LLM doesn't understand what it is doing.

> The user experience is similar to Notion

Honestly, it sounds like a judgment call because Notion is truly a monstrous thing. It slows down terribly and it's just plain uncomfortable. Why does "everyone" love Notion? It's horrible, how can you even use it?

Programs that do simple things should be simple and run fast. It's like a pencil that you simply use and don't think about how to use it, you don't notice it at all.

> It slows down terribly and it's just plain uncomfortable.

When was the last time you use it, and what's in your workspace? Notion did receive some improvements on performance over the years, but it still depends strong on which data you dump into your workspace.

> Why does "everyone" love Notion?

Because it's an awesome concept with a well-rounded implementation on the user side. It just sucks hard on the technical side. I mean, it's a good tool, but it has an upper ceiling of what one should do with it. But this is a general problem with all those young fancy tools. Obsidian or Logseq are not different in that regard. They all are scaling poor. They are simply not meant for this.

> Programs that do simple things should be simple and run fast.

It's not simple, it's very far from being simple.

>everyone loves notion

I don’t, I actually loathe it.

Joplin uses SQLite DB to store data, not markdown files. Moreover, you can't even change the directory where this database is stored, which is pretty funny for an open source application. Also, there are no internal linking and knowledge graphs in there. Also, there are UI/UX issues, for example annoying modal windows about updates can pop up at inopportune moments. But it should be noted that web clipper is quite usable. But it is not rocket science to make a web clipper. Obsidian is an app of a higher level of quality and usability.

Markdown is a blessing for any operation that needs to be performed across many files. Load up your favorite editor and get going.