Great photo. Actually, is this a photo?
Great photo. Actually, is this a photo?
8½ is a pretty surreal. Considered one of the most influential films of all time. One of the earliest examples of post-modernism in film.
Every scene in Ex Machina is basically a dialogue covering different arguments in the philosophy of AI. Plus a surreal dance scene.
I was blown away by mother! when I first saw it. But looking back on it, the allegory wasn’t exactly subtle.
Once Upon a Time in Hollywood is a meta-modern masterpiece.
Tropic Thunder, as a meta commentary on comedy, is actually really good. Aside from the great comedy itself.
Maybe.
Linux won because it worked. Hurd was stuck in research and development hell. They never were able to catch up.
However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.
Quite the opposite.
GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.
Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.
Linux won because it was simple, not elaborate.
You talk about “non-absolutist,” but this thread got started because the parent comment said “literally never.”
I am literally making the point that the absolutist take is bad, and that there are good reasons to call unwrap in prod code.
smdh
Fair. But unwrap versus expect isn’t really the point. Sure one has a better error message printed to your backtrace. But IMO that’s not what I’m looking for when I’m looking at a backtrace. I don’t mind plain unwraps or assertions without messages.
From my experience, when people say “don’t unwrap in production code” they really mean “don’t call panic! in production code.” And that’s a bad take.
Annotating unreachable branches with a panic is the right thing to do; mucking up your interfaces to propagate errors that can’t actually happen is the wrong thing to do.
Unwrap should literally never appear in production code
Unwrap comes up all the time in the standard library.
For example, if you know you’re popping from a non-empty vector, unwrap is totally the right too for the job. There are tons of circumstances where you know at higher levels that edge cases defended against at lower levels with Option
cannot occur.
deleted by creator
They can’t even be punished. robots.txt
is just a convention, not a regulation. It’s totally not enforceable.
The only legal framework we have is copyright law. Those who oppose this behavior will have to demonstrate copyright violation, and that may be difficult to do since the law hasn’t caught up.
This comment is copyrighted by me and licensed to the public under the terms of the CC-BY-NC-SA 4.0. If you intend to use this comment for commercial purposes, you must secure a commercial license from me, which will cost you a lot of money. If you violate the terms of the CC-BY-NC-SA 4.0 without securing an appropriate license, I will send my army of lawyers that I totally definitely have to defend my copyright against you in court.
orlp invented PDQSort and Glidesort. He collaborated with Voultapher on Driftsort.
Driftsort is like a successor to Glidesort.
Glidesort had some issues that prevented it from being merged into std, and which are addressed in Driftsort. IIRC it had something to do with codegen bloat.
What’s wrong with AC if it’s powered by renewable electricity?
Zsh
No plugin manager. Zsh has a builtin plugin system (autoload
) and ships with most things you want (like Git integration).
My config: http://github.com/cbarrick/dotfiles
Exactly.
My take is that the issue isn’t with tmpfiles.d, but rather the decision to use it for creating home directories.
Someone told me that Goldeneye actually supported dual stick controls if you plugged in two controllers. And Perfect Dark is the same engine.
I need to try that out on real hardware…
113M shares times $31/share is $3.5B.
That’s wild. No way the company is worth that, much less his share.
With a headline like that, I thought he died…
Huh. This got me curious.
Yes, I did just type a bare URL. Every mature markdown parser I’ve used turns this into a link, and appropriately handles trailing punctuation.
So I went to the spec, and it’s explicitly called out that this is not an autolink. Autolinks must be explicitly surrounded with angle brackets <>
.
So yeah \shrug.
https://spec.commonmark.org/0.31.2/#autolinks
Edit to be clear: This means that both of our markdown parsers are wrong relative to the commonmark spec. But I’ll argue that if a parser is going to attempt to autolink this, then handling trailing punctuation is better than not.
Yes, thanks for the spelling correction.