9bananas

aber "DU", da geht noch was!

all of the words you listed that use a soft g are loanwords from other languages (pretty sure they're all french) soooo......yeah. no wonder those have different pronunciation.

when you look at anglo-saxon words the difference becomes clear:

• gift
• graveyard
• ground
• gay

all hard g's.

mixing up languages is the common denominator here.

the G in GIF stands for graphical, neither english nor french in origin, hence the confusion about pronunciation.

alternatively; English is a terrible mess, and the only "correct" pronunciation is reached through general consensus. if the majority pronounces something a certain way, that's how it should be pronounced.

Orconomics (Dark Profit Saga, Trilogy) for the exact same reason!

excellent fun to read, incredibly funny!

this is not true.

it entirely depends on the specific application.

there is no OS-level, standardized, dynamic allocation of RAM (definitely not on windows, i assume it's the same for OSX).

this is because most programming languages handle RAM allocation within the individual program, so the OS can't allocate RAM however it wants.

the OS could put processes to "sleep", but that's basically just the previously mentioned swap memory and leads to HD degradation and poor performance/hiccups, which is why it's not used much...

so, no.

RAM is usually NOT dynamically allocated by the OS.

it CAN be dynamically allocated by individual programs, IF they are written in a way that supports dynamic allocation of RAM, which some languages do well, others not so much...

it's certainly not universally true.

also, what you describe when saying:

Any modern OS will allocate RAM as necessary. If another application needs, it will allocate some to it.

...is literally swap. that's exactly what the previous user said.

and swap is not the same as "allocating RAM when a program needs it", instead it's the OS going "oh shit! I'm out of RAM and need more NOW, or I'm going to crash! better be safe and steal some memory from disk!"

what happens is:

the OS runs out of RAM and needs more, so it marks a portion of the next best HD as swap-RAM and starts using that instead.

HDs are not built for this use case, so whichever processes use the swap space become slooooooow and responsiveness suffers greatly.

on top of that, memory of any kind is built for a certain amount of read/write operations. this is also considered the "lifespan" of a memory component.

RAM is built for a LOT of (very fast) R/W operations.

hard drives are NOT built for that.

RAM has at least an order of magnitude more R/W ops going on than a hard drive, so when a computer uses swap excessively, instead of as very last resort as intended, it leads to a vastly shortened lifespan of the disk.

for an example of a VERY stupid, VERY poor implementation of this behavior, look up the apple M1's rapid SSD degradation.

short summary:

apple only put 8GB of RAM into the first gen M1's, which made the OS use swap memory almost continuously, which wore out the hard drive MUCH faster than expected.

...and since the HD is soldered onto the Mainboard, that completely bricks the device in about half a year/year, depending on usage.

TL;DR: you're categorically and objectively wrong about this. sorry :/

hope you found this explanation helpful tho!

and your source measured the effects of one single area that cathartic theory is supposed to apply to, not all of them.

your source does in no way support the claim that the observed effects apply to anything other than aggressive behavior.

i understand that the theory supposedly applies to other areas as well, but as you so helpfully pointed out: the theory doesn't seem to hold up.

so either A: the theory is wrong, and so the association between aggression and sexuality needs to be called into question also;

or B: the theory isn't wrong after all.

you are now claiming that the theory is wrong, but at the same time, the theory is totally correct! (when it's convenient to you, that is)

so which is it now? is the theory correct? then your source must be ~~wrong~~ irrelevant.

or is the theory wrong? then the claim of a link between sexuality and aggression is also without support, until you provide a source for that claim.

you can't have it both ways, but you're sure trying to.

you made the claim that the cathartic hypothesis is poorly supported by evidence, which you source supports, but is not relevant to the topic at hand.

your other claim is that sexual release follows the same patterns as aggression. that's a pretty big claim! i'd like to see a source that supports that claim.

otherwise you've just provided a source that provides sound evidence, but is also entirely off-topic...

your source is exclusively about aggressive behavior...

it uses the term "arousal", which is not referring to sexual arousal, but rather a state of heightened agitation.

provide an actual source in support of your claim, or stop spreading misinformation.

the information age is easy: the silicon age!

not sure about the space age...maybe titanium age? that's about the time we figured out how to machine titanium on large scales, and for highly specialized, extreme applications (talking about the SR-71 here, mostly). could also call it the alloy age, since a number of important alloys were discovered around that time

not necessarily, but it can be a good idea to have a distributed, tamper proof ledger of transactions.

that way anyone can provide proof for basically anything to do with the service: payment, drive, location, etc.

it might also have advantages from a security perspective for riders and drivers.

there are advantages, they're not entirely necessary, but they may well be the best option for a distributed network (i.e.: no central server infrastructure, at least not beyond some simple software repository for downloads/updates)

+1 for everything: literally saves my sanity

so you're basically saying it talked itself squarely into uncanny valley?

i honestly didn't consider that would be an issue for LLMs, but in hindsight...yeah, that's gonna be a problem...

there's probably already a tamperMonkey script out there, check greasyFork or something