![](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?
Didn’t he have a stutter when younger?
every accusation is a confession.
This is all I could think of when Trump said Democrats would use every avenue both legal and illegal to overturn election results.
More like there being chemicals that actually fucked up frogs’ genitals but we only ever heard about it through the lens of Alex Jones and “turning the freaking frogs gay [sic]” https://youtu.be/i5uSbp0YDhc
They say they already use it to manage GitHub issues so it’s definitely more than “point 0” right now.
That’s always struck me as odd, but I’m also very much an outsider looking in. A “gecko electron” does sound intriguing though.
The generic name I’m complaining about is “conventional commits”, not “fix” and “feat”
I see ads pretty much everyday in Windows. They’re not as attention grabbing as traditional ads and I think this is part of why some people don’t see them.
Just because it might be legal to violate copyrights in other countries doesn’t make the code considered open source though lol.
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 😩
You’re being obtuse. I get the point you’re trying to make – you’ve been heard. I’m just saying those aren’t the terms you should be using to make it. Open source has a very distinct definition and it has to do with the licenses covering the code. It has nothing to do with whether different countries have differing laws. Code cannot be open source in one country and not open source in another because the definition has nothing to do with countries. In fact, that would specifically not be open source because it gives rights to some and not others.
If someone infringes on a copyright that doesn’t mean the work isn’t copyrighted. You can’t just say things that are source available are open source. Even if someone is infringing on the rights holders they’re still only source available.
Open source doesn’t mean source available. You simply aren’t using the term correctly.
For the love of all things pure, holy, and just, please do not use YAML in your APIs…