I've been waiting for indexing improvemence for over 10 years, not holding my breath.
You installed an npm package and it seems to depend on all the things? Let's start indexing on node_modules and give you no chance to even uninstall the **er. You used the CLI to work around our tooling? Hey let's start indexing immediately after this one finishes so it's a great idea for a coffee break, just never pull directly after coming back so you may actually do some work until we bog down all the cpu cores.
Don't get me wrong, I love all the JB IDEs, but indexing has been a deal-breaker for many.
I wish it bogged down all cores.. I work on relatively small Java projects (maybe 10 KLOC, 20 or so items in the pom.xml (although these obviously have transitive dependencies)). IntelliJ 2018 would re-index everything in a few minutes using all 20 vcores. I specifically spent about $8k on an iMac Pro back in the day to make this faster.
IntelliJ 2022, on the other hand, uses only 4 cores, and takes about 10 minutes. That's a stupid default (if I buy a powerful computer I want to use it..).
There is a setting to override it, but in my case it just doesn't work. CPU goes to approx 400% and just stays there. I filed a bug report, no movement.
Edit: I should say 12-thread, not 12-core, just to be clear on the performance level we're expecting here. It's a 6c/12t i7.
I haven't worked with Java in ~2 years so I'm not sure how bad it is now. I might start a NiFi index job just for fun...
But for some reason, whenever I reopen a project, it needs to reindex it. Even when I open the same project every day, not having changed anything in between. I understand from a friend it doesn't do that with Java projects.
Sometimes it does. I have no idea what causes it.
I think their developers have no idea how it works either and just gave up some time after the useless shared indices came out.
That's both on my 16-inch M1 Max and my M2 Air with Go in Goland.
JetBrains is good for stuff I rarely do in the editor, like certain types of debugging, but otherwise feels too heavy, expensive, and hard to configure across installs. Finding a particular config option is always a hunt.
My dad was a vim user since the 90s and he ended up switching to IntelliJ a few years ago as well. It’s just significantly less hassle and has way more intelligent intellisense/autocomplete.
I used to meticulously maintain a vim config for the 8 or so languages I switch between, but eventually realised that for me the good part of vim is modal editing, and that IdeaVIM gives me that without having to fuss with it. My vimrc is now empty and it’s relegated to commit messages and fixing merge conflicts…
Do you know you can search for an option in the settings menu? Actually, you can search just about everywhere.
You can also set your IDE to store your config in a git repo so that it's the same everywhere you use it.
You should be debugging alongside development to gain deep understanding and reduce errors. No amount of "test" coverage can replace that.
I'm always skeptical about people who don't use IDEs and I'm almost always right about them. And it's not the good kind of being right.
Can it:
- assign (scenario, subsystem, level, description) to breakpoints and watches, so they can be turned on/off or selected in groups for debugging without removal?
- commit these scenarios of bps and watches into a repository?
- edit/read them in a textual form to patch or share over an IM?
- store traces of previous sessions and diff them to find out what changed?
Does anything even remotely similar exist? Most debuggers are just test-pause-and-inspect tools with “integration” in the form of eval on mouse hover. Their ux and dx sucks and the only reason I could find to use them were slow build times and too low-level runtimes, which are no more today.
Pretty sure most people avoid debuggers not because they are too hard to learn (they aren’t), but because they are too dumb to be useful, given that you can ‘if (cond) log.level(…)’ and restart instantly.
In Jetbrain's tools they definitely can. I can
* create a bunch of breakpoints
* give them descriptions
* only have them break on execution under certain conditions (conditions stated via the programming language being debugged, so `my_struct.some_func() == 5`)
* disable and enable breakpoints with a click of a button
* have a breakpoint only become active when another breakpoint got hit (and therefore only cause the debugging logic to execute in certain code paths
* Have a breakpoint not stop execution when it gets hit, which is useful because I can then
* Log when a breakpoint gets hit, including it's stack trace (so I can see exactly the flow that got me to that breakpoint)
* Evaluate some variable when a breakpoint is hit and log that evaluation.
All of this with an extremely simple UI that can be manipulated without any recompiles and while the application is running. I've gotten tons of value of debugging complex scenarios in both C# and Rust via this constructs.
So while I'm not going to convince you that debuggers are worthwhile, to call them "too dumb to be useful" is pretty naive.
The problem that debuggers solve is simply not a big problem anymore, in my experience. Definitely not worth the setup hassle when actively working on multiple platforms.
As a fellow debugger lover, having to basically use log statements instead of being able to reach in and debug was a rude awakening. Some people probably don’t know that debugging can be easy with the right combination of IDE and language. Or the billion software layers mean that the debugger fails to attach for some reason which can’t be figured out.
Debugging and using IDEs are entirely orthogonal. DTrace and lldb are far more valuable to me than a graphical step debugger, which I effectively never use. As it happens I use JetBrains IDEs full time.
One option is to use their sync service with your Jetbrain account, but you can also use git[1]
It definitely makes it easier to move machines when your settings and plugins are kept in sync with it.
[1] https://www.jetbrains.com/help/idea/sharing-your-ide-setting...
Apologies if you have accessibility needs and that’s the reason, but otherwise what is so unique about your editing requirements that requires such extreme customisation? I just use tools as they come. I try not to change anything. Less entropy in my life.
(Emacs, of course, has best in class discoverability via M-x and C-h, which allow you to find and introspect basically everything that's available to you, but then Emacs is an OS, not an editor)
We are not fine with it. It really sucks. It's just out of our hands.
To this day I hate the gmail interface. It used to be so much better back in the day.
Actually I did use the web client one time recently and I literally couldn't find an email I knew I'd just received; my inbox is kept at 0 unread; so in theory it should have been impossible NOT to see it, right? After the initial confusion then annoyance came the realisation and I just went and found my phone to read it on.
> Nah I'm fine with it, because I never go to the website and just use mail
> clients; I can tolerate you its existence, out of sight out of mind and all that.
And that contributes nothing to this thread because we are discussing the Jetbrains UI and the Gmail UI was an analogy. Unless you would like to argue that we can ignore Jetbrains UI changes like Gmail UI changes because we can use VIM as an interface to the code, so the Jetbrains UI is out of sight out of mind and all that.I'm neither fine with Gmail, nor with major changes to Jetbrains IDE which I've been using every day for years now, and totally agree with all of the points in the article (and by extension this thread).
> I'm afraid my British humour (sarcasm) may have been lost here.
That's fine. Apparently you're no Eric Idle, but I'm no Einstein here either.It was more pleasant to look at and provided more useful functionality on the UI.
The modern trend of wasting space and erasing colors is really bad.
The only new feature I like is the "tab" categories (but only on desktop). Though they really botched it because now I'm confused about the difference between categories and labels so I don't use labels anymore. IMO they should have used the existing labels system for that.
It was also pretty easy to find and read your email, which it currently is not.
I wish there was a better balance between both UIs. The "better looking" one wastes too much resources (CPU, memory, screen space).
It's not about resource cost for me, I use high end hardware and fast connections (coupled with ad and script blockers, both in-browser and at network level, which are probably adding to the frustration) and not only does it load and run like complete crap, I literally couldn't find an email I knew was there in my "inbox" last time I opened it.
I only use Gmail/Workspace for family/personal stuff so I just use mobile apps 99% of the time now, but if I had to use it more regularly I'd be quite annoyed.
Not that Office 365 which I use for work is any better in a web browser.
The "basic HTML" version is probably not exactly as any previous version but it's a good approximation. I think it makes much better use of color and space, and the buttons have text labels instead of using an arcane symbol language I have to relearn every time I have the misfortune to use it.
I actually really like it. I've been looking at IntelliJ for 8 years, the refresh is really very welcome XD. I also haven't noticed any lost functionality.
https://mail.google.com/mail/u/0/h/
Still points to the "basic HTML" version, which is at least faster than the standard one. (I use it, and I'll keep using it, until I can, I guess.) https://support.google.com/mail/answer/15049
Found that while searching for the same problem
I did make an attempt to be the million line vimrc, t480, arch Linux guy (from reading HN) for a month or two but I found it was taking up so much time it was basically a hobby. I would rather just have something that works out the box (Mac + jetbrains) and be able to spend work and hobby time coding interesting stuff.
The fancy vim configuration just becomes more and more frustrating the more languages that you use and you start to run into weird things like when you start a new line in markdown the cursor doesn’t start at the same bullet indentation level so now you need to debug which plugin is messing that up.
Or if your Linux laptop doesn’t actually go to sleep (and goes flat) and PyCharm needs to index _again_ on start!
It’s an uncomfortable feeling to see something new, and sometimes it genuinely is a step backwards, but I feel most of the time it’s progress and you get over it after a month.
I kid, I kid.
But not really.
I wonder how many percent of users are sticking with the old UI.
Even now when I look at Gmail 2004 I find it superior to the current UI.
It might look a lot prettier now, but it's much harder to actually do things from zero knowledge, I do fear we've regressed.
”New packaging, same great taste” the professional liars proclaim; as the box got emptier, the false bottom bigger, the air more voluminous, the filler lower quality. No, no. Worse things are in fact good for you. The party proclaimed it, so you are required to believe it. Or else.
Even more controversial is both the cause and the remedy, for which the overwhelming number of people, especially on a site like this, have absolutely no interest in facing; so I will refrain from expanding on that. It’s irrelevant anyways, because the consequences are as inevitable as they were clearly predicted and suppressed.
The abusive relationship that the western world in particular is currently in, remains largely furiously defended, like any other abusive relationship the abused have not yet faced reality about.
That results in continued comments one can also see in these threads, proclaiming essentially how “no, no, degraded features and lower information density against my will is actually a good thing”, which is no different than “I would not get beaten if I just made smarter decisions”.
The problem is precisely what you say: UI """designers""" don't make evidence-based decisons and don't do research or look for user feedback, they simply go with whatever they subjectively think best.
Don\t get me started on GNOME-iffication of apps.
Or stop the damm thing to run indexing, or avoid doing 10 finger combos, showing code problems without running inspections, doing Java compilation on save without using Eclipse's own compiler,...
> doing Java compilation on save without using Eclipse's own compiler If you are saving files with Intellij. Configure Intellij to save when focus is lost. I haven't pressed Ctrl-S in 15 years in Intellij. Regarding the automatic compiling whenever you save, like in Eclipse. I am really happy it doesn't do this. Because it means I can work slow compiling projects at all. I can work with refactoring features while my code is in the middle of larger refactoring and it doesn't compile. And so on. But if you prefer Eclipse's workflow, why not use Eclipse?
Incrementally compiling on save, is hardly noticeable versus continuous indexing.
Eclipse has incremental compile. Only parts you changed are compiling and it is not slow at all.
> I can work with refactoring features while my code is in the middle of larger refactoring and it doesn't compile.
That works in Eclipse perfectly well - except that code completion and suggestions are much better then the ones you get in Idea.
Especially in cases when much more important tasks are at hand, as you rightfully note.
It’s a completely different tool window layout mechanism with far fewer tool windows that can be open at the same time. I rely on having my source control, embedded terminal, problems window, commit window + more all simultaneously visible. It’s key to my workflow to have a number of key windows open and their new layout throws this all away.
So far its the most disruptive and user hostile “UI refresh” I’ve ever seen and will see me moving back to Visual Studio if they persist with it.
Sadly it’s not actually just a UI refresh but a UI downgrade because they’ve actually removed key functionality, not just tweaked some visual styling.
It’s a completely different tool window layout mechanism with far fewer tool windows that can be open at the same time. I rely on having my source control, embedded terminal, problems window, commit window + more all simultaneously visible. It’s key to my workflow to have a number of key windows open and their new layout throws this all away.
So far its the most disruptive and user hostile “UI refresh” I’ve ever seen and will see me moving back to Visual Studio if they persist with it.
They dont, not compared to eclipse and java. They are more lightway and look nicer, but it does much less for you. (The default call hierarchy is just atrocious for example, you can see only problems from small part of project etc)
I'm not fine with it. It's still an accessibility DF for me, and I use HTML mode, despite it being semi-broken.
I just wish they would invest more money into things that are actually a problem currently like how slow indexing is and how disruptive it is when you do a clean re-install and it indexes all your dependencies again.
I have tried spacemacs which gives a lot of functionality out the box with less configuration needed than DIY vim or emacs but it still just doesn’t compare to the ease of use of Jetbrains IDEs across languages (I use Java, Python, Ruby and Typescript every week).