> I think the basic intellij config is set at max 2 gigs of RAM
yes, that is the conservative JDK defaults iirc; its likely unrelated to intellij specifically. I only mentioned the system specs because the other commenter was like 'i buy nice machines and give the editor tons of RAM'. but thats the cost of them using java. I don't want to tune my editor to ensure its responsive and can get its job done.
> Windows issue, and has nothing to do with intellij
except I exclusively run linux. ;)
> what language was that project written in?
early days for a flutter app. most of the issues most certainly due to the plugins themselves.
it was primarily gradle tasks running without prompting and fucking up my build.
I didn't configure anything. the experience was so bad I just bailed out, switched to my standard stack vscode and the command line stuff and never looked back.
Wait, all of this complaint is for a niche language in "early days" and you didn't even bother to try giving it more RAM? For a guy who just had to suggest I was a shill, that's a lot of information you left out of your initial judgement.
> yes, that is the conservative JDK defaults iirc; its likely unrelated to intellij specifically
No, it is explicitly set by intellij through its vmoptions file. The JDK by default uses as much as half of all available RAM (that is for maximum usage. It doesn’t start there)
yes, that is the conservative JDK defaults iirc; its likely unrelated to intellij specifically. I only mentioned the system specs because the other commenter was like 'i buy nice machines and give the editor tons of RAM'. but thats the cost of them using java. I don't want to tune my editor to ensure its responsive and can get its job done.
> Windows issue, and has nothing to do with intellij
except I exclusively run linux. ;)
> what language was that project written in?
early days for a flutter app. most of the issues most certainly due to the plugins themselves.
it was primarily gradle tasks running without prompting and fucking up my build.
I didn't configure anything. the experience was so bad I just bailed out, switched to my standard stack vscode and the command line stuff and never looked back.