You may get more traction asking in the communities that exist for those tools: IntelliJ and Docker
8GB for two separate IntelliJ projects sounds low. You could try importing both into one instance as separate "modules" so that there is only one IntelliJ instance/window.
Depending on how you are running the VM, the host may be choking it through the host OS and leading to OOM. Especially with a tool like docker.
Edit: I see you commented usage of windows, you may need to look into wslconfig
Hi friend, sounds like you should join us over in devops@programming.dev :)
It is important, and effective, to properly track and show to teams what effect their code changes have to the system and what "their team's process" looks like to an outsider with meaningful data.
More here https://programming.dev/post/80365
Ahh, that would make more sense, thank you - corrected
This is a great explanation, thank you.
I deal mainly with authorization and I'm not sure I've ever had the differences explained this simply (so I incorrectly lump them together)
I am still fairly new to Steam deck (~6 months).
Outside of having the dock to allow for normal USB ports for both keyboard and mouse (without converters and such), this awesome steam-deck-tricks readme/repo is majorly where I have been learning from.
The major catch is rootfs read only and strategizing how to avoid reinstalls after steam updates. I haven't quite gotten all the way there yet since I am using it more for tinkering (linux host on local network) for the time being.
I think we have ~400 microservices of varying types that deploy in many ways to many places (big proponents of using the right tools for the job rather than forcing preferred tools) and definitely in the last block. Although, as a DevOps guy my life would be a lot easier if we had a handful of monster monoliths, I understand it doesn't make sense for our scale. I can fantasize though, and this meme hits extremely close to home ๐
Tangentially, at my previous job we were in blocks 4 and 5 of transitioning away from a single monolith. Major issues arise when a "Java only shop for 20 years" start down this path with an extreme mindset of "we only use Java". Java kubernetes controllers? lmfao, no thanks (they wanted them though ๐)
I think JetBrains has fully bought into Gradle. I think Maven support has been less and less over time, which shouldn't be a surprise. Gradle supports native Kotlin build scripts (i.e.
build.gradle.kts), as well as putting a lot of work into ensuring their tools fit well within the Gradle ecosystem (exhibit A: https://github.com/JetBrains/intellij-platform-plugin-template). I think it only natural for the creator/owner/maintainer of Kotlin to go full in on the build system that supports the language!controversial take: who still uses maven? who would prefer xml files over build scripts? (ok... fine, big timers like RedHat definitely do, or at least, have never taken/don't want to take the time to upgrade lol)