It would be quite useful for the sort of software development I do, where I want to run my IDE, applications under development, plus various databases -- all in Kubernetes, Docker compose, etcetera, and ideally with realistic heap sizes.
It's also handy for running integration tests that use TestContainers in parallel so I can run a huge test suite very quickly with, for example, 10 copies of the application and database under test at the same time.
I often have to do backporting work meaning I want multiple large projects open in my IDE at the same time. I like to enable all of the indexing features which enables lots programmer assistance functionality, but it uses lots of RAM.
It would be a entirely a luxury but not wasted, enabling multiple of these kinds of workflows to happen at the same time.
The question is whether you would just become hopelessly CPU-bound before being able to make use of it. I suspect yes, in which case, something more modest likely makes sense.
I'll just speak for myself.
It would be quite useful for the sort of software development I do, where I want to run my IDE, applications under development, plus various databases -- all in Kubernetes, Docker compose, etcetera, and ideally with realistic heap sizes.
It's also handy for running integration tests that use TestContainers in parallel so I can run a huge test suite very quickly with, for example, 10 copies of the application and database under test at the same time.
I often have to do backporting work meaning I want multiple large projects open in my IDE at the same time. I like to enable all of the indexing features which enables lots programmer assistance functionality, but it uses lots of RAM.
It would be a entirely a luxury but not wasted, enabling multiple of these kinds of workflows to happen at the same time.
The question is whether you would just become hopelessly CPU-bound before being able to make use of it. I suspect yes, in which case, something more modest likely makes sense.