Viewing profile — serichsen

Integer division: I think the best thing to do is to produce an exact rational, like Clojure that was mentioned, and most Lisps, where it got that from.

Lisps do NOT do textual inclusion. Lisp systems are created from code, not text. I guess that the author only saw the use of `use-package' or the `:use' option of `defpackage', but…

The sport here seems to be which compiler manages to re-write the bad code best. Tail call optimization is only marginally relevant here, since the tail call is the addition, not o…

- Technical decisions from non-technical people (especially management and politics) - False commitment to up-front design decisions, even in the face of absurdities and architectu…

From my german perspective, every assumption in this article looks quite gross and barbaric. Here, everyone is insured. If you break your arm, you get it fixed. If you get cancer, …

Given the choice, I would.

The Fisher-Yates shuffle has an off-by-one.

Lisp's problem is rather that so many people play around with it, but not long enough to develop /good taste/ in it, and finally loudly complain about the language when their real …

Common Lisp has “first” and “rest” as aliases for “car” and “cdr” where it makes sense.

Valid points, but not _the_ point. There is a big difference between allowing and supporting something. OO languages _support_ hidden inputs and outputs as well as programming by m…

There seems to be a problem with ko: it alerts that retaking is forbidden even though the board has changed. Afterwards, play seems to be ended.

I am not on that mailing list, but I'd like to point out Emacs Lisp, which doesn't have modules (they would rather be called "packages" as in Common Lisp, but anyway, they just are…

I see two problems with the basic idea of JSX: - Parsing is a mess, it is not even obviously unambiguous. - HTML syntax is horrible, and all templating language attempts building o…

OK, so who manages the keys, and how? I am aware of only two general principles to do this: centralized certificate authorities (possibly chained), and decentralized assurance, a. …

It seems OK, but it would have been better if it was made by someone with more familiarity and experience with the language.

The question is about defaults. Current default of C and C++ is to cut all corners wherever it is not clearly impossible (sometimes even then). That is the insanity. Of course you …

> When those systems aren't well thought out or secure you have security issues. All evidence says that there are no well thought out and secure systems written in C or C++. If the…

Yeah! Or COBOL! PHP! INTERCAL!

> Until very recently, this situation would not have occurred. Until very recently, people didn't even have smartphones that could have been suspected to contain useful information…

COBOL will never die, either.

“I've seen things you people wouldn't believe…”

> XML is just s-exprs No. That myth has been decisively addressed by Erik Naggum about 12 years ago. His summary: > They are not identical. The aspects you are willing to ignore ar…

Huh?

Meh. This is not "ahead of the curve" but just the mainstream, maybe a little behind.

12. No! That is not a good shuffle. Search for "javascript shuffle" to find a correct Fisher-Yates implementation.