If that ever gets fixed then I'd look at replacing Sublime (which is still my go-to for quick editing) and then see if it can handle more advanced coding (which one the rotating list of various vscode forks handle today)
So, it's been one year since I use Zed daily, and I didn't encounter this issue, or any other issue for instance, everything is smooth and I never encountered a failure or a crash.
I work on large (everything is relative, though) monorepos, that would probably qualify for this limit, and I remember already did the kind of "workaround" discussed in this issue years ago on this device. I think it's hard to blame the software when the default file limit is so low depending on the languages you work with.
Anyway, if you would encounter this problem, you would have already encountered it with other tools, or else this is fine.
Have you tried BBEdit recently? It's incredibly configurable, AI features are entirely opt-in, and it supports LSPs now. It's my go-to for basically all text editing these days.
Honestly when I saw Okta in the headline, I had assumed the article was going to say they were breached again.
This one is amusing, and as another comment mentioned below, large companies are awful at accepting patches on github. Most use one-way sync tools to push from their internal repositories to github.
Cool, I just had claude code write me something similiar this week to go through my immediate directories and get me this type of information on each one of this (since all of my git repos are under a single dir)
fun fact: check-projects is initially a nodejs script I wrote specifically for my projects few years ago;
My first usage to test out claude code was to generalize this script: cople hours later it was entirely rewritten with Go and and CI on github actions you see now here.
I think if your old company plan is with Vanguard and your new company plan is not as good as Vanguard, you leave it in the old company plan as a 401k.
Sometimes, sure - but sometimes, passing around a fat wrapper around a DB cursor is worse, and the code would be better off paginating and materializing each page of data in memory. As usual, it depends.
which is really funny, since the Microsoft mice (only a few are left) and keyboards (discontinued) are by far some of my favorite peripherals.
On the apple mouse side, I got a white corded mouse with the tiny eraser looking mousewheel back in around 2003 or so, it's still in use today with a M4 mac mini. Works like a champ, Keyboard from that era is also still in use and used daily in our family.
I daily drive the Microsoft Touch Mouse, have for 10+ years. It is by far my favorite piece of hardware. I've never seen another one used in the wild, which might explain why they discontinued it.
If that ever gets fixed then I'd look at replacing Sublime (which is still my go-to for quick editing) and then see if it can handle more advanced coding (which one the rotating list of various vscode forks handle today)