maninalift

Is anyone aware of any line-breaking algorithm which penalises for rivers or typesetting algorithm which adjusts spacing to compensate for it.

I'm interested that rivers are such a concern of manual typesetting but I have never heard mention of it in typesetting algorithms.

dumb question: "more ht2000 lines of code" - is that a typo of "more than...", is "ht2000" something I don't know and can't google, or are are these hacks in some way related to an antique motherboard?

ghost what?

yes, that's exactly what stepstep said

The description notes the replacement of many uses of "tasks" with native OS threads. Tasks may map to threads or may be managed as green threads.

Threads unlike tasks must be detached if they are too be allowed to outlive their parent.

yaaaaaaaaaaaaaaaaaarg awesome!

even if software is formally verified, and even assuming the specification is both totally accurate and complete, there is plenty of room for issues at software deployment in a multi-component system such as this

This appears not to actually solve the hard problems of cryptography. It simply generates a random key, them XORs your message with it.

The key and the message are independently just random data and don't reveal anything about the content of the original message (except it's length).

It is a pretty rare case where we cannot transmit messages securely but we are confident that we can transmit two messages and not have them both intercepted.

If on the other hand you can securely transmit keys that are as big as your data, you could of course just transmit the data itself.

As such this is a starting point in understanding cryptography rather than a practical application.

I think, please tell me if I am missing something