Hacker News new | past | comments | ask | show | jobs | submit | jstclair's comments login

This is the place to look for the standards Oslo sets for road safety and cycling infrastructure.


He did what? The pre-existing know-how to build reusable rockets? Are you confusing SpaceX and Tesla?


Ever since Elon became the world's richest man people like this have showed up. I don't know if they have been misinformed or if they just want to say negative things about billionaires. But the early history of SpaceX is very well documented in the book liftoff if anyone wants to know the truth.


No mentions of promises? Any reason to rev the spec without promises?


IIRC the main reason indexeddb does not use promises is because promises are required to reject/resolve asynchronously [1]. Indexeddb requires that you manipulate the object stores in a synchronous way from it's event handlers, so it can terminate the transaction after running the event handlers synchronously. It can't do this with promises that will run their resolve handler at best in the next microtask.

It's been a while since I looked into this, but I remember this being my conclusion.

1: https://promisesaplus.com/#point-34


That's actually not true in Chrome https://bugs.chromium.org/p/chromium/issues/detail?id=457409 although it's not clear if that is a bug in Chrome or in other browsers. It would be nice to have more clarity on that, or an explicit promise API like https://github.com/inexorabletash/indexeddb-promises because until then it's really shitty to use - you have to constantly worry about cross-browser compatibility.


I understand the transactional requirements but AFAIK most IDB operations are already async. Open for example:

https://developer.mozilla.org/en-US/docs/Web/API/IDBFactory/...

"The method returns an IDBOpenDBRequest object immediately, and performs the open operation asynchronously."


Here's the discussion on promises: https://github.com/inexorabletash/indexeddb-promises

The 2.0 spec is just a bunch of minor changes. Promises will be a big change - although I would argue it's way more important than all this other stuff combined.


Not all operations are asynchronous.


Sounds like you're describing Microsoft Research's CHESS (2007), and a host of related projects (Google's ThreadWeaver for Java).

See http://research.microsoft.com/en-us/projects/chess/ and https://code.google.com/archive/p/thread-weaver/wikis/UsersG...


I made blogpost about thread weaver some time ago. Not very useful http://www.mapdb.org/news/thread_weaver/


Admins, how did this dupe https://news.ycombinator.com/item?id=10764870 (11 hours ago)?


(I'm not an admin. You probably want to email HN because they won't see the question otherwise.)

In the past HN had a fairly strict dupe-detection filter.

That meant that a lot of good stories that didn't get attention on the first posting didn't get reposted.

Currently the dupe-detection is much weaker than it used to be. A story that didn't get much attention on the first post can be reposted easily now.

HN tried an experiment where they'd email people and ask them to repost submissions, and give those reposts a small bump. That was a lot of work, so they only do that for "Show HNs". Now they do something like an auto-repost which resets the timestamp.

This means that sometimes you'll post something, and it won't get much attention, and a few hours later someone else will post the same thing and it'll get upvotes.

This isn't going to stay like it is. They're working on a better system.

https://news.ycombinator.com/item?id=10754760

>> We've recently started doing things to make the original submitter get the front-page slot more often

https://news.ycombinator.com/item?id=10753401

>> Invited reposts are mostly deprecated now in favor of re-ups [1], but when it looks like the submitter might also be the author (as e.g. with Show HNs), we still send them. It's nice for an author to know that their post may still get discussed, and it's good for HN when an author jumps into the thread.

https://news.ycombinator.com/item?id=10705926

(A meta post, with links to previous discussion).


Thanks for that! I knew they'd loosened de-duce up a bit, but this was ~10 hours.


Interesting, maybe dupe shouldn't be a hard boolean but something more analogic.

A dupe submit could be like a major upvote, weighed by proximity. 0h-24h : +100, 1d-12d : +50, _ : +1


could they make it so that the discussion in the dupe could be merged with the latest post as it is now people add links to previous posts.


I guess they decided it didn't get a fair run and removed it from the dupe checker? That happens sometimes...


An interesting companion would be J.L.Austin's "A Plea for Excuses", where he contrasts "by mistake" and "by accident".

(Google books link, but the PDF is available widely)

https://books.google.no/books?id=CPKHKvge3Z4C&lpg=PA379&ots=...


If you're not familiar with the author, Dan Davies, he's been a contributor at Crooked Timber (http://crookedtimber.org). A great intro would be his choose-your-own-adventure intro to the Greek financial crisis from 2012 (http://crookedtimber.org/2012/02/16/so-what-would-your-plan-...).

Paul Krugman called this post from 2004 one of the great blog posts of our era: https://dsquareddigest.wordpress.com/2004/05/27/108573518762...


I've been working on a virtual table (not for React, but KnockoutJS) that's designed around needed to virtual scroll over a large number of columns (as well as rows). Really in-progress code at the moment, but getting there...

[Knockout-Virtual-Grid](https://github.com/jstclair/knockout-virtual-grid)

[Live Demo](http://jsbin.com/roheqo/1/)

You can edit that on JsBin and easily increase the columns to 5-10,000. You may want to look at [editableCell](https://github.com/gnab/editableCell) for some of the keyboard shortcuts.


That's really nice work John - thanks!


Yea that is very nice!


So you've just sterilized the Einsteins...

The whole premise is that "like produces like", which of course is nonsense. Dumb people have brilliant kids, ugly people produce beautiful children, and so on and so forth.


1. The Einsteins were a fairly intelligent family - so it's a bad example: http://en.wikipedia.org/wiki/Einstein_family

2. You are wrong vis-a-vis heritability of intelligence. It is largely determined by genes: http://en.wikipedia.org/wiki/Heritability_of_IQ

3. However - you are right in one respect. There is usually a 'pull to the mean'. That means that children of exceptional people tend to be closer to the average, thus they are not as gifted as the exceptional parent.


Would an individual have been chosen for sterilization if:

1) He was born with a markedly pointy head, which caused much consternation to his parents and relatives.

2) Was developmentally backward. Notably, he failed to acquire language skills for a significant period during his early childhood.

3) He was educationally subnormal, showing signs of what would now be diagnosed as ADHD,and drugged into a stupor.

4) Was bone lazy. I believe that 'schweinehunde' was the informal term used at the time for this condition.

5) Was disobedient and rebellious, or one of those 'malcontents' that perennially threaten to upset the applecart of society (the term 'hooligan' enjoyed a brief vogue for describing this condition).

6) Was Jewish. The eugenics movement designated Jews for mass sterilization, along with Blacks, Poles and the 'bloody Irish' (but then again, these were the same dolts who thought that sterilizing homosexuals would somehow serve to 'keep the race pure').

Albert Einstein was a prime candidate for this preemptive culling.


I think your comment is a good example of why talking about intelligence is hard.

Note that nobody here advocated forced sterilizations (or killing off ugly babies).

All we said is that it's pretty much settled that intelligence is inheritable.

PS I will contend one point - and that is whether Jews were marked for mass sterilization. That is false.

Jews were marked by Nazis for extermination. However - people who advocated eugenics in other countries (like US or the UK) had no issues with Jews (http://en.wikipedia.org/wiki/Eugenics_in_the_United_States).

If anything, Jews (or more precisely Ashkenazi) are a poster child for eugenics - since really that's what they went through in the middle ages, which is used to explain their enormous achievement (see http://www.economist.com/node/4032638)


Awesome! Gonna spend a weekend on this.

And an easy way to share my personal all-time favorite title sequence, Delicatessen:

http://www.artofthetitle.com/title/delicatessen/


I have to link to North by Northwest. Just incredible when you consider it was done in 1959.

http://www.artofthetitle.com/title/north-by-northwest/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: