For VSCode, using workspaces kind of solves the problem, but it's annoying because I often find myself moving between an app and common components shared between apps and thus part of the monorepo.

With IntelliJ however, I'm stumped. Not only does indexing take time, it also seems to just not like monorepos very much. Opening just one module while an option results me having to have more than one instance of IntelliJ open which again feels like an inefficient use of resources.

Dunno... Been working with monorepos for about 4 years now, and I can't say I don't see any benefit, but I also feel like it introduced new problems I really didn't want to have to deal with.

Either way, thanks for the balanced write-up on the topic. It's not an easy one to tackle because people either love it or hate it. I myself am in the camp of trying not to hate it and very often the more vocals ones are the haters (which makes sense), but I do sometimes swear under my nose and wish it never became a thing, I'll admit to that. 😆