![](https://programming.dev/pictrs/image/a491cc5f-fa6b-402c-af4c-7f6ae4c276da.webp)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
It’s entirely disingenuous because who the hell is throwing JSON into YAML without converting it? Oh wow, I changed the file extension and it still works. I’m so glad we changed to YAML!
Professional developer and amateur gardener located near Atlanta, GA in the USA.
It’s entirely disingenuous because who the hell is throwing JSON into YAML without converting it? Oh wow, I changed the file extension and it still works. I’m so glad we changed to YAML!
Unless you’re dealing with some insanely flexible schema, you should be able to know what kind of number (int, double, and so on) a field should contain when deserializing a number field in JSON. Using a string does not provide any benefits here unless there’s some big in your deserialzation process.
Should be like 0o777
to mimic hex 0xFF
Do you actually use them?
These people already cling to fringe beliefs because they feel marginalized by society. Bullying them on national television is not going to make them any more likely to change their beliefs. It’s only going to make them double and triple down.
The generic name I’m complaining about is “conventional commits”, not “fix” and “feat”
Everyone complaining about timezones is truly missing the forests for the trees.
Go play EVE Online. The servers used to have (still, do I think, but shorter) daily downtime that was scheduled using UTC and it led to everyone using UTC since the game server itself used that time.
Proleptic Gregorian Calendar enjoyers
Yesssss, so true. Anytime people say they want history to be “clean” I insist they explain what they mean because more often than not they’re going to suggest something that makes the history way less useful.
Any standard that wastes valuable space in the first line of the commit is a hard sell. I don’t see the point in including fix/feat/feat! just for the sake of “easy” semantic versioning because generally you know if the next release is going to be major or minor and patches are generally only only after specific bugs. Scanning the commits like this also puts way too much trust in people writing good commit messages which nobody ever seems to do.
Also, I fucking hate standards that use generic names like this. It’s like they’re declaring themselves the correct choice. Like “git flow”.
And then my team squashes those commits 😩
Think of this like saying using a scythe to mow your lawn is antiquated. If your lawn is tiny then it doesn’t really matter. But we’re talking about massive “enterprise scale” lawns lol. You’re gonna want something you can drive.
Don’t forget ear files. Oh, and don’t forget the abomination that is the executable war file when you’re using Spring Boot but your company hasn’t fully embraced it yet.
Can you use sftp instead? Pwease? 🥺
Hell yes, Luvon. Temurin is the GOAT.
Wowwww that’s truly fucked up.
Adoptium and OpenJDK are different builds. OpenJDK has no concept of LTS which is why they only provide the latest build. Adoptium has LTS versions and you can download past ones.
That’s why you shouldn’t use OpenJDK. You should use Adoptium (formerly known as AdoptOpenJDK). OpenJDK also doesn’t provide builds of anything but the latest version even though the source is still receiving bug fixes for previous versions. OpenJDK has no concept of LTS.
For the love of all things pure, holy, and just, please do not use YAML in your APIs…