maninalift · HackerTrans

maninalift

no profile record

Submissions

Node Inspector

github.com

2 pointsby maninalift13 years ago0 comments

comments

11 years agodiscuss

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.

11 years agodiscuss

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?

11 years agodiscuss

ghost what?

12 years agodiscuss

yes, that's exactly what stepstep said

12 years agodiscuss

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.

12 years agodiscuss

yaaaaaaaaaaaaaaaaaarg awesome!

12 years agodiscuss

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

12 years agodiscuss

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

maninalift
12 years agodiscuss

Readers may be interested to cf. https://en.wikipedia.org/wiki/Corecursion

maninalift
12 years agodiscuss

A nice demonstration of lambda calculus using Church Encoding in Ruby, without saying that that's what he's doing.

I guess at the end of the video, he will probably reveal what the thing he's been doing is called.

maninalift
12 years agodiscuss

Voted down? It's just a quick, weak joke, I don't see the harm.

maninalift
12 years agodiscuss

unmatched </semisarcasm> at (3,123)

maninalift
12 years agodiscuss

I heartily recommend this short accessible article to anyone interested in loeb:

https://github.com/quchen/articles/blob/master/loeb-moeb.md

maninalift
12 years agodiscuss

I usually skip the start-up advice posts on HN but this was worth reading for the first point along "focus on the problem not the solution". Good advice for hackers as well as entrepreneurs.

maninalift
12 years agodiscuss

Put enough ground coffee into a cup that a spoon shushed into it goes "thunk" like a spade into sand and stands up.

Pour over hot water to just cover, stir until saturated, fill cup, allow to settle, drink.

No need for filters or devices. All the flavour stays in the cup.

maninalift
12 years agodiscuss

Ew, now you can have an awkward weak implementation of some FP ideas in Go too.

Yeah, I'm a bitch.

maninalift
12 years agodiscuss

Am I shallow that it made me feel good getting all the answers right even though I knew most of the people who tried it would?

maninalift
12 years agodiscuss

I just read the first one 8718462, and I actually think it might be worse than the "photographs on a white background" patent linked to in article.

maninalift
12 years agodiscuss

"positioned in a longitudinal axis intersecting" = "pointing at"

obfuscation is the name of the game

You wouldn't get away with horrendous babble like this in essay in any subject at any level of education.

maninalift
12 years agodiscuss

Surely the key point is that most of us read indentation first, it doesn't matter whether you are witting C with semicolons and curlies or ruby with no semicolons and "end"s or lisp with parens, what the programmer really reads first is the indentation. Those other things are sometimes checked afterwards.

Therefore there are two reasonable courses of action to prevent this kind of problem:

* use automatic code indentation * use a whitespace significant language
The second is absolutely the better choice. You may disagree but you are wrong. This is not a matter of taste, it is a matter of programming language syntax actually reflecting what the programmer reads.