No gods, no masters.
It’s the API’s job to validate it either way. As it does that job, it may as well parse the string as an integer.
I’m not a solipsist.
That’s true, the Amazonians do need air raid sirens due to the chemical air attacks from entrepreneurial colonialists.
polyculture intensifies
I fucking hate timezones. Whatever it is, I’d rather read the current clock as 4 a.m. even if it’s noon than have timezones.
The sound would make for a great emergency alarm system in case of natural disasters or air raids.
I invite all cheese lovers to try Adipocere.
Yeah but how is the Kremlin going to control us with their gas & oil if we have nuclear?
France is EU’s first importer of ‘Russian nuclear products’: study – Euractiv
New report shows Russia raking in revenue from state nuclear company | Fox Business
Russia faces threat of sanctions on nuclear power industry as Germany backs uranium ban – POLITICO
Bratislava to reject EU’s latest sanctions package if it includes ban on Russia nuclear fuel
Russia’s Rosatom Helps Putin Skirt Sanctions
Russia’s nuclear project in Hungary: France’s growing role | OSW Centre for Eastern Studies
https://www.greenpeace.de/publikationen/20220517-greenpeace-report-russland-taxonomie.pdf
Squashing
The
s
“squash” command is where we see the true utility of rebase. Squash allows you to specify which commits you want to merge into the previous commits. This is what enables a “clean history.” During rebase playback, Git will execute the specified rebase command for each commit. In the case of squash commits, Git will open your configured text editor and prompt to combine the specified commit messages. This entire process can be visualized as follows:
Note that the commits modified with a rebase command have a different ID than either of the original commits. Commits marked with pick will have a new ID if the previous commits have been rewritten.
https://www.atlassian.com/git/tutorials/rewriting-history
You can also amend for a softer approach, which works better if you don’t push to remote after every commit.
The
git commit --amend
command is a convenient way to modify the most recent commit. It lets you combine staged changes with the previous commit instead of creating an entirely new commit. It can also be used to simply edit the previous commit message without changing its snapshot. But, amending does not just alter the most recent commit, it replaces it entirely, meaning the amended commit will be a new entity with its own ref. To Git, it will look like a brand new commit, which is visualized with an asterisk (*) in the diagram below.
You can keep amending commits and creating more chunky and meaningful ones in an incremental way. Think of it as converting baby steps into an adult step.
This is the kind of stuff the timber mafia needs to know so that they can efficiently pack trees and send them to IKEA.
Remember kids: publishing negative results is hard.
If you read the article there, you’ll notice that it’s more complicated.
I’ve also read a bunch of papers on it and it’s not as simple as access. People have desires (often influenced by advertising and culture) and a certain segment of the planetary population believes that cooking is beneath them, so that it’s someone else (very shitty) job to feed them while the hustle and grind to win the Dream.
Isn’t this about the racism?
see: mpox
I was referring to this concept: https://sentientmedia.org/food-desert/
You’re referring to outliers.
If you care about animals, you don’t move to a “desert” where you don’t have a supply of non-animal-based food. That’s the cost of trying to give a shit. You don’t get to be an opportunistic predator, you don’t practice it only when it’s convenient with your business/career plan.
For most people this isn’t even an issue, but carnists love to glom onto the exceptions as if most humans are living on a space station surrounded by asteroid cattle.
I was also like that when I was a child. Along with “did you bring anything?”