_a_a_a_

I've never owned a games console so I don't know, but I thought they could be used to play DVD films. It makes perfect sense as part of their function. ISTM anyway.

Fresh cardboard can be a prize bitch too. Even worse perhaps.

(source: was picker in a 3M warehouse)

I said this is where it would help (AFAICS), not that it was the best solution.

At a guess, a single thread which benefits from as much cache as it can get.

Seems very complex therefore very expensive (and possibly slow where it matters, at L2). Or it might just work.

> As for what I mean by narrative, much of the appeal of D&D seems to lie in crafting the story and adventure, being a part of the plot

That's what I was after. I know some people play in a much more involved way but when I played so many years ago I love the plot and setting, but really worked the mechanics. It may have been you got a DM or group that was just not suited to you.

> with its slow pace and focus on narrative

am curious, could you elaborate a touch on these? TIA

> I hit a case where I actually test nothing and have no results. Did I pass?

equally, can you reasonably say you failed?

Okay, I'll respond because you made an interesting point, but you've also pissed me off. Let's follow this through: for a start, just because it's an intuitive doesn't mean it's wrong. However, you made me think that may be we can force at compile time that all() must take a non-empty list of Booleans where we can be sure that the problem domain should never have empty lists. I think with modern typing we can do this with dependent types (but I'm not an expert on this, but you have raised an interesting possibility, thanks).

However there are domain cases where empty lists still make sense, so you're still going to have to account for them in a rational way, and that means logically consistent, and I guarantee we will be back to what you don't like. But that's ok.

Now where you've pissed me off is this bit

> n this case, one possible solution is to not have the concept of "falsy" and "truthy"

and

> forcing 'all' to take a mapping closure

Perhaps you could un-piss me off by explaining what the bloody hell those two are supposed to mean – pretend I'm a language designer that interested in your idea (which actually I am) – what are you asking me to implement?

It's a consequence of enforcing logical consistency. You can't get around that (but if you want to suggest other behaviour and justify it, I'd be interested).

That was not an example of low risk, responsible drug use - "There is more stupidity in the universe than hydrogen"

This kind of stupid behaviour does not improve the image of drug use.

Word. I borrowed a circa 2005 – 2010 server and the fan roared on start-up. I would not want that on full-time for reasons of noise, power and wear.

Can't remember but have read you can bootstrap a forth interpreter from an amazingly low number of bytes. Maybe more of theoretical interest than practical but still.