3 ms·

I don't see how JetBrains can fix (or even be expected to fix) this problem long term. It's a macOS/Java problem that can only be truly fixed by Apple and Orac

I don't see how JetBrains can fix (or even be expected to fix) this problem long term. It's a macOS/Java problem that can only be truly fixed by Apple and Oracle.

jakewins 3y ago
It makes a lot of sense for them to try though - the obvious reaction here is to switch to VSCode, devs using JetBrains can’t wait for Oracle to fix this. I imagine JB are churning a lot of users because of this
- mdaniel 3y ago
  merely as anectdata, I'm on 14.4 (m2) and none of the JetBrains products are doing anything weird for me. But nor am I getting any of the whatever other bad outcomes the blogosphere is whining about 14.4 so there's obviously some nuance to the errors also, lol, "the obvious reaction here is to switch to VSCode" doesn't even deserve a response