Personal anecdote: I had a subscription to the Philly Inquirer. They made it very easy to sign up online, but there was no way to cancel online. The website only said "call the sales team to cancel".
I changed my home address to California, and shortly after, a new "Cancel Subscription" button appeared on the PI website, which worked great.
I think in this case you just need to change your mailing address with them. There is a California law (and from other comments it looks like 4 other states) that requires them to allow easy cancelations to CA residents. And since it is probably too much work for them to prove you are a CA resident, they just have the logic check if your address is in CA to enable the online cancelation (since they have online signup)
Fellow Branestawm enthusiast here. That is the first time anyone has ever mentioned Professor Branestawm on HN, as far as I can tell! It's triggering deep memories.
As another comment said, you can write client side code in F# which gets transpiled to JS, just like Typescript or CoffeeScript. This approach allows you to use JSX components directly from your F# code. It's very cool. Other FP languages have something similar.
OCaml took the '|>' pipe symbol from F#. And F# was the language that made the '|>' pipe symbol popular in mainstream programming (as opposed to the unix '|' pipe symbol), afaik. According to Don Syme, it was used in F# in 2003 (see "Early History of F#", section 9.1, [1] which references [2]).
Here's his full comment:
/quote
Despite being heavily associated with F#, the use of the pipeline symbol in ML dialects actually originates from Tobias Nipkow, in May 1994 (with obvious semiotic inspiration from UNIX pipes) [archives 1994; Syme 2011].
... I promised to dig into my old mail folders to uncover the true story behind |> in Isabelle/ML, which also turned out popular in F#...
In the attachment you find the original mail thread of the three of us [ Larry Paulson; Tobias Nipkow; Marius Wenzel], coming up with this now indispensable piece of ML art in April/May 1994. The mail exchange starts as a response of Larry to my changes.
...Tobias ...came up with the actual name |> in the end...
/endquote
Haskell has had "$" or "backwards pipe" for ages, but that is just another way of doing function application and it does not feel the same as (and is not used the same way as) the unix-style piping paradigm.
Peter Norvig does his own research: "When faced with a controversy like this, the great thing is that you can do your own research. If you suspect Oreskes or Peiser (or both) might be biased, you can look at the data yourself."
I'm skeptical of "doing your own research" on scientific topics. Most of us lack the background to even read primary sources.
In this case, the background required isn't really about climatology, but just to judge whether a conclusion points in one direction or another. That is something that we can probably participate in, even without any climatological background.
But that also limits the breadth of our conclusion. We can infer that the papers all point in the same direction, but we can't rule out the possibility that contradictory papers have been systematically excluded.
It seems to me "common sense" that a conspiracy that universal and pervasive is effectively impossible, especially given that the motives suggested for it are absurd. But "common sense" isn't an argument, and many people "do their own research" and conclude that such a conspiracy is not only likely but certain.
Exactly. I have a mild accent, but my dad still has a thick brogue. Would a car understand him? Not if it's using the same algorithm as YT's captioning.
Agreed about the TLA docs, but it is worth persisting, as TLA is very useful in some situations. These slides cover the basic syntax enough to get started.
The original title is "Write your own Excel in 100 lines of F#." I don't know why the F# part was removed either. HN guidelines say "please use the original title, unless it is misleading or linkbait; don't editorialize.". Having read the article, I don't think the "in 100 lines of F#" part is misleading, nor is it Buzzfeed-style clickbait.
"in 100 lines", especially when not strictly accurate, is a nerdier version of "9 zany reasons ..." and the like. HN's title star chamber is also generally down on magic numbers in titles.
reply