Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jbclements
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
jbclements
10y ago
As someone with a definite and well-established viewpoint on CS education, I sort of expected to hate this paper... but I didn't. I thought it made some excellent points, and I very much liked the idea that people not trained as progra
32.
▲
by
jbclements
11y ago
I'm really astonished to find only a handful of references to DuckDuckGo in this discussion. I've been using it exclusively for about 2 years now, and had no problems at all. Perhaps I just don't know what I'm missing ..
33.
▲
by
jbclements
11y ago
I have a lot of bones to pick with Mathematica, but calling it "clunky" seems like a stretch; my experience suggests that mathematica is the exact opposite of clunky; it has so much silky chrome that I feel like it's complete
34.
▲
United wants to know if you work as a plumbing insulator?
(jalopnik.com)
3 points
by
jbclements
11y ago
|
1 comments
35.
▲
by
jbclements
11y ago
I'll tell you what I want: I want Google to help identify non-DKIM-compliant forwarders. As the operator of (yes, I know) a vanity e-mail domain with DKIM, SPF, and DMARC records, I have no problem sending mail to gmail directly; in fa
36.
▲
by
jbclements
11y ago
I'm not so sure about that; I use a self-signed cert for port 25 TLS, and I just sent from google to my domain, and didn't see a warning.
37.
▲
by
jbclements
11y ago
I host with linode, and have had generally good results sending mail to gmail. They're definitely not the worst. Granted, I have had SPF enabled for about 10 years.
38.
▲
by
jbclements
11y ago
I geniunely do feel bad for magazines that are trying to figure out how to survive in a world of ad-blockers. I suspect that many hard-working journalists will lose their jobs as magazines like Wired go out of business. I personally subscri
39.
▲
by
jbclements
11y ago
I'm very sad to see this announcement. I've been a big fan of persona since I first learned about it three years ago, and for a few months I tilted at windmills by writing to services I used, and asking them why they didn't s
40.
▲
by
jbclements
11y ago
Sorry to see this post sink without a trace; I think this is a really big deal, and I'm excited to see a shared industry/academia ecosystem growing around Rust. Now if only the macro system were a little more hygienic ....
41.
▲
by
jbclements
11y ago
Main-line lefty here: I'm immensely frustrating to me to read articles that point out that there's no solid research on guns & gun violence when--to the best of my knowledge--congress has been blocking funding for this researc
42.
▲
by
jbclements
11y ago
That's not a fair comparison. I can't believe I'm going to defend Apple here, but Apple's "walled garden" is an environment that they designed, that people can choose to use or not. We can tell people that ther
43.
▲
by
jbclements
11y ago
After 10 seconds of inspection: no, not a good idea, don't think this solves a nice problem. Speaking as a PL & s-exp guy, I don't really have a problem writing (bullets (item "pick up milk") (item "drop off d
44.
▲
by
jbclements
12y ago
try it out! I found this style of password (horse-battery-staple) to be much longer and less memorable. The proof, of course, is in the pudding. The next step (for me) is to conduct a reasonable experiment to discover whether or not these p
45.
▲
by
jbclements
12y ago
Yes, absolutely. 100% invertible.
46.
▲
by
jbclements
12y ago
cool... can you guarantee that every password is generated with equal probability?
47.
▲
by
jbclements
12y ago
Variable-order markov models do sound interesting; this tool isn't using them, though....
48.
▲
by
jbclements
12y ago
I tried it, and ... eliminating the double-quotes looks like a win. Average password lengths in the order-2 model don't increase measurably; it rounds to 20.0 chars for both models. I've now deployed this. Um ... I mean... what qu
49.
▲
by
jbclements
12y ago
Um... certificate pinning? Fortunately, my last caveat covers a bunch of these. Also, I think you(I) forgot: * You are in fact hallucinating at this very moment.
50.
▲
by
jbclements
12y ago
Things will definitely get a bit longer if you make the source more uniform. I sympathize with you on the quotation marks, though; I think it might be nice to toss just those. Lemme try that.
51.
▲
by
jbclements
12y ago
I took a look at whole words. Things got a lot longer. Like, twice as long. Here, let me generate some. These are 56-bits each: '(#" that looked up to Darnay: you not?\" \"Very willingly,\" pointing" #"
52.
▲
by
jbclements
12y ago
Seriously. Has someone already done this? Next gen peer review, anyone?
53.
▲
by
jbclements
12y ago
you might be interested in http://try-racket.org . Quick online tutorial. Haven't worked through it myself, but spent 30 seconds with it to make sure I wasn't embarrassingly wrong.
54.
▲
by
jbclements
12y ago
I'm assuming that there's no memory safety guarantee for Swift code that interacts with Objective C code. Can anyone shed any light on this?
55.
▲
by
jbclements
12y ago
From a PL standpoint: 1) APL clearly made good use of an extensive symbol set. Now that many languages support unicode, this is totally do-able. 2) APL is in love with overloading. It's not totally my cup of tea, but you could definite
56.
▲
by
jbclements
12y ago
This is absolutely the best news I've had all day. I've been a fierce advocate of proper tail calling since 1999, and I'm incredibly happy to see it gaining traction outside of niche functional languages like Racket. Many, ma
57.
▲
by
jbclements
13y ago
Looks like no one's mentioned Benjamin Pierce's authoritative book on this, "Types and Programming Languages" (TAPL). I would certainly put it way, way above the Dragon Book. Bob Harper can certainly defend his opinions