- Jun 24, 2017
- 1,092
- 1,318
Yes, but the story is only the sex portion of her side and then the story from Literotica.com is over...so probably one final update to goqazxsw80 Regarding your review - just FYI, 0.9 doesn't necessarily mean "near complete" - version .....
Oh I didn't know this was from an existing story. Nevermind thenY
Yes, but the story is only the sex portion of her side and then the story from Literotica.com is over...so probably one final update to go
Don't care.....SHE'S HOT!So if the mc doesn't condone the cheating/ntr the girl does it anyway.... why get married if you can't be honest/faithful? why is mc stupid? He can't figure out she's cheating? the guy even tells him "man you're wife is something else" bang splat brain matter everywhere as well as his buddies.... smh... or alternatively mc: "oh so she's a cheating whore? Why did I bother even showing up I'll be filing for divorce and finding someone worthwhile... also moving to the wrong neighborhood, but they are all going on vacation? I don't know many broke people who can afford a vacation? Seems like the characters are being punk'd and Ashton Kutcher should be jumping in at any moment going "man I can't believe you fell for that"
Yeah, the girl with the nazi tats etc really put me off along with everything else you mentioned. Don't really want nazis in my sex game.Of course BBC,s.
Like horses.
N-word this , n-word that.
A girl with Third Reich jewelry.
Prejudice everywhere.
Not my nazi cup-a-tea.
I hate to nit pick, but that would only make sense if it was 0.09 rolling over to 0.10. 0.9 is 0.90, (the last zero obviously drops off with how decimals work). So going from 0.90 to 0.10 doesn't make sense, that's going backwards. That's like a kid counting "eighteen, nineteen, tenteen, eleventeen, twelveteen, thirteenteen...." etc.. Get my point? Mind you, I'm not arguing "The fact that it's 0.9 must mean it's almost done", just saying that if it isn't & is going to roll over 0.10, (Tenteen hur hur hur), then the dev is just bad at math. That's all.qazxsw80 Regarding your review - just FYI, 0.9 doesn't necessarily mean "near complete" - version numbering isn't a decimal system (some devs do use it that way, but not most). It can go from 0.9 to 0.10
Mate I literally addressed this in the post you quoted (in fact it was the entire point of said post): version numbering is not a decimal system. Some amateur devs use it as such, and there's nothing wrong with that as there's really no "official" standard, but it's not common practice.I hate to nit pick, but that would only make sense if it was 0.09 rolling over to 0.10. 0.9 is 0.90, (the last zero obviously drops off with how decimals work).
I'm aware. It still doesn't make sense & is still bad math though. I mean even if it was common practice for many dev's to number their releases as "0.1, waaaa, o hi there, potato, bluuuuue, my mouth tastes like teeth," etc... Still doesn't change the fact that it's dumb & illogical. Lot's of brain dead people on tik tok did the tide pod challenge too. Just means that's lots of people being stupid. Sorry but it is what it is.Mate I literally addressed this in the post you quoted (in fact it was the entire point of said post): version numbering is not a decimal system. Some amateur devs use it as such, and there's nothing wrong with that as there's really no "official" standard, but it's not common practice.
yes it looks like that, it's possible, we'll see ;-)I'm aware. It still doesn't make sense & is still bad math though. I mean even if it was common practice for many dev's to number their releases as "0.1, waaaa, o hi there, potato, bluuuuue, my mouth tastes like teeth," etc... Still doesn't change the fact that it's dumb & illogical. Lot's of brain dead people on tik tok did the tide pod challenge too. Just means that's lots of people being stupid. Sorry but it is what it is.
Also, numbering scheme aside, it still doesn't change the fact that this game is almost done. It's a bunch of lazy, mismatched renders slapped on someone else's incomplete story. After Angelica's POV for the last scene completes, the game creator no longer has any story material left because the author never finished it. Since they not only didn't bother creating their own story, but also didn't even bother editing their story to fit the renders or vice versa, odds are they are just going to abandon it.
It isn't "bad math" because it isn't fucking math. I don't know what is so hard to understand about this. A project doesn't just automatically reach a major release just because there's been nine minor updates prior (or a minor update just because there have been nine patches), that would be idiotic.I'm aware. It still doesn't make sense & is still bad math though. I mean even if it was common practice for many dev's to number their releases as "0.1, waaaa, o hi there, potato, bluuuuue, my mouth tastes like teeth," etc... Still doesn't change the fact that it's dumb & illogical. Lot's of brain dead people on tik tok did the tide pod challenge too. Just means that's lots of people being stupid. Sorry but it is what it is.
With all due respect, it seems clear that the tiniest bit of research was exactly what you did, as what you have done is demonstrate you know just enough to think you know what you're talking about, but not enough to realize that you really don't.It isn't "bad math" because it isn't fucking math. I don't know what is so hard to understand about this. A project doesn't just automatically reach a major release just because there's been nine minor updates prior (or a minor update just because there have been nine patches), that would be idiotic.
Do you know what the current version of Chrome is? 90.0.4430.93.
Apache? 2.4.47.
SQL Server? 5.0.4123.1.
Final version of macOS X? 10.15.
Firefox?You don't have permission to view the spoiler content. Log in or register now.
Maybe actually do theYou must be registered to see the linksbefore trying to act as if you know better than an entire industry.
Very true, but as someone who's done quite a bit of this kind of work, both contract & working for companies, one rule of thumb that always remains prevalent, (at least with the competent ones), is to structure all aspects of the work so that it's as efficient & streamlined as possible. Why turn a task into a 4 or 5 step process when it can be done in 1 or 2 steps? They also like to automate as much as they can to minimize steps. Less time, work & effort for the same result which saves time & money. Pretty universal concept. So if they structure their catalogue numbering sequence as x.x.x, that's 3 single character octets. Now if they have to roll over to a 2 character octet, that adds more work from them because they then have to modify the cataloguing sequence from 1 to 2 before they can catalogue it. This extra work adds nothing to the product & is basically internal time & money spent to rework internal systems to accommodate their cataloguing needs. That's wasted time, money & effort. So typically they will design their cataloguing method to accommodate for this possibility, so that they don't have to re-work it later. So for example, using your example of a 2.9.0 build rolling over to 2.10.0, while some people might do this, you don't see this often with competent programmers because that would require them investing extra time & effort to accommodate that cataloguing change that doesn't yield them extra benefit & for those few companies that do make that error, their is typically an observable trend of mismanagement & bad decision making more globally with them. Overall, it's substantially more likely that they would roll over from 2.9.0 to 2.9.1 because it meets the needs for cataloguing & allows them to use their already existing framework, which fits with what we typically see.This is not my words, i just grab them from somewhere but i always believe it like this.
"The revision tracks every change that people commit to the source code. This might be a number (like r630) or a hash (like da39a3ee5e6b4b0d3255bfef95601890afd80709).
The build tracks every time that there has been an official build of the software. This might be a number (like build 284) or a date (like 20190311, always YYYYMMDD unless you are crazy). Not all revisions get turned into builds, but each build corresponds to a specific revision.
The version is used mostly for official releases. It might look like X.Y.Z. As a rule, compare left to right. So 2.4.63 comes before 2.5.0, and that comes before 3.0.0. You might have 2.9.0 and then 2.10.0, because 10 > 9. These aren't decimal numbers, they’re separate numbers that have a dot between them. They can mean almost anything, you can make up whatever you want. Another example is xbox went to version Xbox, Xbox360, Xbox360s, Xbox360e, and back to Xbox One. Usually, you make a bunch of different builds before making one of the builds into a new version.
One of the main things you have to deal with is that you could release a version that has a bug in it—say, v1.3.0—and then you fix the bug, and release v1.3.1. Maybe you’ve already made a bunch of changes that are supposed to go in v1.4, but you’re careful not to include those changes in v1.3.1. So you make what is called a release branch."
The conclusion is the version numbering don't mean anything, so they can do whatever they want with it.