Yeah I guess you’re right. Probably just seen the Source Code Pro one so many times that I stopped being annoyed with it.
Should try exposing myself to the Jetbrains Mono font until I get used to that instead, then I won’t have to fiddle with that part of the IDE settings.
I use SauceCode Pro (variant of SourceCode Pro with nerdfonts stuff). I’ve given up on changing it because everytime I do I find stuff that’s “non-standard” in the fonts I test and it bugs the hell out of me. signs are the absolute worst offenders, which is weird because they have a very uniform look everywhere that’s not a specialized “programming” monospace font.
Yes, but at the end there should be a single all lowercase "i love gradle"
Gradle is fantastic, but there is this mantra you have to chant while tinkering with it:
I hate Gradle, I hate Gradle, I hate Gradle, I hate Gradle, I hate Gradle
But once you get it to do whatever you want it's way more powerful than Maven, since it's actual code. Also you will never get me to voluntarily define my project structure in XML.
the biggest selling point for me is that I’ll have a mounted folder or two, a shell script for creating the container, and then if I want to move the service to a new computer I just move these files/folders and run the script. it’s awesome. the initial setup is also a lot easier because all dependencies and stuff are bundled with the app.
in short, it’s basically the exe-file of the server world
that’s true I guess, but for the most part shit’s stuck inside the container anyway so how much does it really matter?
you kinda can, reading a Dockerfile is pretty much like reading a very basic shell script for the most part. regardless, I do trust most creators of images I use. most of the images I have running are either created by the people who made the app, or official docker images. if I trust them enough to run their apps, why wouldn’t I trust their images?
that’s sort of the point, isn’t it? stuff is isolated