Pertinent info on this change is in the Unreal dev docs here: https://dev.epicgames.com/docs/services/en-US/GameServices/A...
1,761 karma · joined August 12, 2015
Pertinent info on this change is in the Unreal dev docs here: https://dev.epicgames.com/docs/services/en-US/GameServices/A...
You could take this a step further; once you have determined that a set of chunks have been modified significantly, you could apply that set of changes to the same coordinates of any map generated from that seed, meaning you can combine changes from multiple worlds into one (with the same seed).
You could take this a step further by "decaying" the bases in some way (remove torches, remove some large percent of the items in chests, add vines, weather rock, move blocks from the ceiling to the floor, etc)
Are you asserting that this is the case in reality, or that we should strive for a society and economic system in which this would be true?
"This waste is also related a tension: intransigence versus capricious trashing. Responding to change quickly is a core tenet of agile development and often thought of as the opposite of refusing to change. However, responding to change is more like a middle ground between intransigence (unreasonably refusing to change) and thrashing (changing features too often, especially arbitrarily alternating between equally good alternatives)."
Is giving a false name to the CC companies not illegal in some way? At the very least I'm certain it is a breach of contract.
Another extremely common pain is trying to "delete" a local commit.
The worst part is the "easier" solutions are actually just footguns in disguise, as soon as they accidentally click the wrong thing and end up with a detached HEAD, a few commits ahead and behind the REMOTE, and halfway through a botched merge, you have to figure out how to bail them out of that using a GUI you've never actually used. Knowing all this, you either teach them git (high short term pain, high chance of them just giving up immediately) or you tell them to download the first result for "windows foss git gui" and pray that history won't repeat itself.
To expand on this, it may be the case that less is more here. Making the description be very short (a paragraph or so - no more than 200 words total) and being emphatic that the founders need to be available to respond to comments will result in greater engagement I'm sure.
If in the course of discussion, the same question keeps popping up, adding a FAQ or some addendum edits to the body should work to fix that.
None of those things are mutually exclusive with vertical scaling?
Having two identical servers for redundancy is doesn't mean you are scaling horizontally (assuming each can handle the load individually, nothing better than discovering that that assumption was incorrect in an outage).
Still pretty expensive if you wanted to do every single Valid CC #, though.
> Fof non-commercial or development usage only