marcusdigitz

I posted a few days ago, but I believe I posted too late for any real traction to be gained.

I work with Typescript a lot. I often reach for complex typing whenever I can improve the DX of everyone around me.

About a year ago, I stumbled accross a show-stopping IntelliJ bug (both webstorm and ultimate) that spikes CPU as high as 1000+%.

The sad part is that this bug has been reported and known for at least 2 years with very little progress being made.

I am reaching out here in the hopes that someone on the Jetbrains team will see this and hopefully, it gets fixed.

I don't want to switch editors, but if this isn't fixed, I fear I'll have no choice

Thank you for taking the time to read this

It's very frustrating since I consider myself a power user. Switching would be hard at this point but I'm at that crossroads now

That's wild, its these types of experiences that pull people out of productive development cycles. I hate fighting with the IDE

IntelliJ has had some type of CPU bug while trying to parse mildly complex Typescript types for about a year now. Its an IDE & machine stopper. I've personally seen spikes up to 800+%. The Jetbrains team has been less than responsive on this issue and it seems like there is no urgency to fix it.

This bug is actively making my development experience miserable.

This repo is to serve as a way for anyone else to verify the bug and hopefully, for the Jetbrains team to fix it.

I want to stress that I DON'T WANT TO SWITCH EDITORS. But I'm at my wits end and this needs fixed

In your "Sentiment" graph, dont you think `negative` should be red?