The first was when I first realized that I could tell codex to use gdb to debug a core dump. This was about a year ago, so it made a bunch of incorrect theories, but it enabled me to go much further than I would have been able to go by myself. I eventually solved the problem.
The second was when I decided to ask it about my Linux Wi-Fi issue that I had been having for several years. The computer would infrequently have multi second pings and dropped packets, then go back to normal. I thought it was due to the weak signal, but after describing the problem to codex, it immediately disabled power management on the Wi-Fi interface (this is a desktop computer, so I don't care much for that anyway) and the problem has never come back. I had been dealing with this for years, and I had tried searching for a solution before, but codex just solved it directly.
I see these posts a lot, but this really does not match my experience. I find I run into many more bugs in kde than in gnome or other desktop environments. This bug made kde absolutely unusable for me: https://bugs.kde.org/show_bug.cgi?id=365255
(I think this bug is still present in X11, but I've moved on to Wayland.)
The other bug I run into constantly is that "exposé" sometimes makes all the windows invisible. The only fix is logging out and logging in again. I've seen this across a number of different distros. Gnome is mostly boring and just works for me.
I've been using Wayland KDE on my gaming machine recently, it somehow made my cursor movement stutter. Switching to KDE X11 or Gnome Wayland solved the issue.
I hope they address this kind of thing prior to making it a default.
> 80% of executives say they would have approached their company’s return-to-office strategy differently if they had access to workplace data to inform their decision-making.
Envoy's not exactly an unbiased source here, since they sell software to collect this data.
I am using typescript with typescript-language-server. I'll give the lazy stuff a try, but I am not sure why this would make the editor more responsive outside of the initial load.
I gave it a try the other day using copilot.lua, and it made the whole editor unusably slow. It somehow caused syntax highlighting to "lag" for tens of seconds every time I made any sort of edit.
Maybe I need to be using the official plugin, and maybe I need to disable LSP based syntax highlighting, but that makes me wonder what it's doing.
In my experience living in SF, these cars are much safer than the typical drivers in my neighborhood for pedestrians. Most human drivers around here don't even bother to stop at stop signs, and instead just slow slightly. With the cruise and Waymo cars, I feel like the risk is a bit lower when I'm on my bike or walking.
I have witnessed a Cruise car stopping in the middle of the road when faced with an oncoming emergency vehicle, so I totally buy that they aren't ready for prime time yet.
Honestly, I'd prefer if we prioritized enforcing existing traffic laws for regular vehicles.
My understanding is that it provides asynchronous replication, so you'd still lose some data if you lose a machine. This is documented here https://litestream.io/tips/#data-loss-window
>The only time you need to consider a client-server setup is: Where you have multiple physical machines accessing the same database server over a network. In this setup you have a shared database between multiple clients.
This caveat covers "most cases". If there's only a single machine, then any data stored is not durable.
Additionally, to my knowledge SQLite doesn't have a solution for durability other than asynchronous replication. Arguably, most applications can tolerate this, but I'd rather just use MySQL with semi-sync replication, and not have to think through all of the edge cases about data loss.
The first was when I first realized that I could tell codex to use gdb to debug a core dump. This was about a year ago, so it made a bunch of incorrect theories, but it enabled me to go much further than I would have been able to go by myself. I eventually solved the problem.
The second was when I decided to ask it about my Linux Wi-Fi issue that I had been having for several years. The computer would infrequently have multi second pings and dropped packets, then go back to normal. I thought it was due to the weak signal, but after describing the problem to codex, it immediately disabled power management on the Wi-Fi interface (this is a desktop computer, so I don't care much for that anyway) and the problem has never come back. I had been dealing with this for years, and I had tried searching for a solution before, but codex just solved it directly.