espdev

I don't understand how Codex can blunder so badly. I imagine that even if they would be using vibe-coding, surely they must have some good engineers. So why is there such severe bugs?

I'd say this is also partly a problem of working under intense pressure and the demand to work faster and faster - even faster now with "AI". All these companies are competing with each other very aggressively and are driving their employees like horses in order to win the "AI" race.

The sound only does not work from the laptop speakers; wired headphones work perfectly. Sometimes you want your laptop speakers to produce sound. So an external sound card does not solve the problem.

It's funny, but for as long as I can remember Linux (20+ years), there have always been some problems with sound.

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

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.

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.

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.

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

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

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?

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.

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.