Recent submissions

Comment · 8 years ago
I'm not gonna bother quoting you to fisk you. Your approach towards my evidence is weak overall. I'm gonna throw more evidence at you.

Miller and Dean Tribble have been working on WeakRefs lately: https://github.com/tc39/proposal-weakrefs

Crockford's personal site no longer has the original JSON description, and neither does the Wayback Machine, but his site does still have a section on E: http://www.crockford.com/

In this talk [0], Crockford discusses the origin of JSON. He mentions working with Chip Morningstar (this guy http://habitatchronicles.com/2017/05/what-are-capabilities/) and has oblique references to his prior work. He doesn't bother to explain what he was doing during the 90s here, and at this point social interaction becomes required to learn more.

'hammering the ES peg in the E hole' is wrong. They're hammering the E peg into the ES hole. Not all of us believe in this approach; some of us think that JS is irredeemable and that we should keep iterating with languages like Pony and Monte which expand on the original E concepts.

Like I said, kicking and screaming. I don't know why you all kick and scream so much, but you do.

[0] http://www.youtube.com/watch?v=-C-JoyNuQJs

Comment · 8 years ago
I get to be part of the discussions since I hack on E-related things.

Mark Miller worked on E and then on Google's Caja (stands for 'Capability JavaScript'). He has been leading an effort to port features from Caja into ES via the 'Secure ECMAScript' initiative: https://github.com/drses

Doug Crockford worked on E and ported E's data mini-language, TermL, to JS and it became JSON. He's also done many other things in the JS community. The json.org website still links into the E archeological site from its front page: http://erights.org/data/terml/embeddings.html

The WeakMap feature of ES doesn't mention it in the spec [0], but the 'sealer/unsealer' capability pattern can be implemented on top easily, and in fact having WeakMap is equivalent to having E's brand-maker or Monte's makeBrandPair, as discussed here: https://groups.google.com/forum/#!topic/cap-talk/4hPYemjPK_Y

[0] https://www.ecma-international.org/ecma-262/6.0/#sec-weakmap...

Comment · 8 years ago
I am pleased to see that features from E continue to be smuggled into ES, like finally-style asynchronous cleanup and template literal enhancements.

Edit: Downvotes can't undo our improvements to ES. We will drag JavaScript and its users, kicking and screaming, to a capability-secure future.

Comment · 8 years ago
Let us analyze this further. Suppose that Alice browses 4chan. 4chan uses a Google image-classifying captcha. Alice is viewing user-generated content posted for free, including 4chan advertisements. When Alice chooses to post, she completes a captcha for Google and her post is sent to 4chan.

Who gets paid for 4chan's content? Alice does not profit. 4chan's users do not profit. 4chan 'profits' via advertising revenue but they actually operate at a loss.

Who is left to get paid? Google. Google gets a human-completed captcha for its machine-learning projects.

I look forward to the demise of the Web and its replacement with a content-addressed alternative where your views will be technologically obsolete.

Comment · 8 years ago
I feel like users should be compensated for giving Google their time and mental energy since this is literally making users manually tag their machine-learning corpus for free.
Comment · 8 years ago
As a resident of Oregon, I notice a curious pattern wherein shitty knockoff or generic products are more likely to carry the warnings, and the warnings don't say which ingredients caused the warnings to be issued. Doing reading on various product ingredients is interesting; in many cases, the manufacture of the product is hazardous to the workers, and so I have begun to see Prop 65 stickers as telling me that the laborers who produced the product worked in unsafe conditions.

In the specific case of coffee, it seems that this ruling was quite reasonable on the facts, up to the still-open question of whether acrylamide really should be considered carcinogenic.

Comment · 8 years ago
Why did your ear, the outer part and the inner bones and the canal and the fluids and the brain, all evolve together in a way that grants Fourier analysis for free? Coincidence?

Maybe maths could help us understand biology or other non-maths fields better!

(Extra mystery: Why did we evolve phase-invariance?)

Comment · 8 years ago
Comment · 8 years ago
I'll believe it when I see it; the authors are well-known for arbitrarily-long delays on upcoming releases as well as bare-bones git repositories with nothing inside.

Unfortunately, I expect that this reference implementation will be a pile of C++, but hopefully the protocol itself will be sufficiently-well-documented to permit implementation in other languages.

Comment · 8 years ago
You'd think so, but check out the 'smooth surprise' in Kahan's great writeup: https://people.eecs.berkeley.edu/~wkahan/Mindless.pdf

We can approximate quite a bit, but ultimately further analysis is required to show that there are no such surprises on any particular root-finding problem.

Comment · 8 years ago
No, the text is awesome. I read it over the weekend.

As an amateur mathematician, don't worry about attempts to apply mathematics to the real world; mathematics is the pattern which emerges from the real world's incidental complexity, and we have always been applying maths to real-world concepts.

Category theory actually provides ways to go from abstract domains to concrete domains. Read the text; it might loosen your view a bit.

Comment · 8 years ago
Nix is for everybody; I don't do functional programming but I still use Nix for everything. If OpenBSD is simple, or C is simple, and Void is also simple, then it sounds like I should not bother trying out Void.
Comment · 8 years ago
Why would one use Void instead of NixOS or another Nix-based distro?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton