Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wycats
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
24 ms
·
211.
▲
by
wycats
13y ago
In general, I've come to believe that it's very easy to look at decisions as "severe cases of NIH" by looking at available tools and assuming that something must fit the bill. Especially in the young ecosystem that is
212.
▲
by
wycats
13y ago
Why?
213.
▲
Announcing Firebase Bindings for EmberJS
(firebase.com)
31 points
by
wycats
13y ago
|
3 comments
214.
▲
by
wycats
13y ago
It looks like the Ember one has three {{action}}s: 1) <button {{action "removeTodo"}} class="destroy"> (a button) 2) <button id="clear-completed" {{action "clearCompleted"}} {{bind-attr class
215.
▲
by
wycats
13y ago
Today's reasonably-built JavaScript-based applications are built using HTML as templates. They don't use a <div> as a button, they use a <button> as a button. They don't invent navigation using JavaScript, they us
216.
▲
by
wycats
13y ago
I was asked to choose a name that didn't potentially confuse the project as officially endorsed by the Rails project and DHH.
217.
▲
by
wycats
13y ago
It's not clear to me how to compile directly to it without breaking CoffeeScript code that already uses for/of. Is the idea to break compatibility with existing CoffeeScript code? See my longer question about this upthread.
218.
▲
by
wycats
13y ago
Generators will be an ES6 feature, and therefore libraries written using generators and yield will run on both the server and in browsers. For many use-cases, this is a good enough reason to use them.
219.
▲
by
wycats
13y ago
There are going to be some bigger issues if you start targeting ES6, like the inconsistency between for/of in ES6 vs. CoffeeScript, differences in destructuring, semantic inconsistencies in classes, etc. I'd be very interested to
220.
▲
by
wycats
13y ago
Does this mean that the mere presence of the word `yield` turns a function into a generator? Is there any way to build a yield-less generator (say, a noop generator for an API that requires a generator)?
221.
▲
by
wycats
13y ago
Also Jefferson: "A strict observance of the written law is doubtless one of the high duties of a good citizen, but it is not the highest. The laws of necessity, of self-preservation, of saving our country when in danger, are of higher
222.
▲
by
wycats
13y ago
There is no secret law. FISA, the law which authorizes surveillance, is a public law approved by Congress. Courts make secret decisions all the time, especially when surveillance is involved. When a local police department gets a wiretap on
223.
▲
by
wycats
13y ago
Article 1, Section 6: "They shall in all Cases, except Treason, Felony and Breach of the Peace, be privileged from Arrest during their Attendance at the Session of their respective Houses, and in going to and returning from the same; a
224.
▲
by
wycats
13y ago
Rational, reasonable response. Kudos! Thought experiment: imagine if half of these foiled plots had occurred. In other words, imagine if every 6 months or so we had a terrorist attack that killed a dozen people (and sometimes more). Do you
225.
▲
by
wycats
13y ago
That's like saying that if there are any reports of measles, the entire vaccination regime is a failure. I agree that we need to know more about the efforts to understand if they're working. I disagree that the small number of ter
226.
▲
by
wycats
13y ago
The problem with this sort of analysis is that there are EXTENSIVE efforts to reduce the amount of terrorism. You might not like it, but the efforts are not trivial. You're looking at the number of terrorism incidents AFTER efforts to
227.
▲
by
wycats
13y ago
The word "infinitesimal" appears in this document.
228.
▲
by
wycats
13y ago
There's already a library named react.js: http://www.reactjs.com/
229.
▲
by
wycats
13y ago
I used URL Templates (RFC 6570 - http://tools.ietf.org/html/rfc6570 ) so that the request to the server is not ad-hoc, but instead fully described by the resource body.
230.
▲
by
wycats
13y ago
URLs are opaque, and can often serve as very useful IDs, but, alone, they imply a one-at-a-time model of fetching documents, and this spec is trying to provide a way to easily request only the documents a client needs in a compound document
231.
▲
by
wycats
13y ago
It can only be used for GET requests, has problems in web browsers, and still requires the overhead of individual requests on the server side to construct and return many responses. In theory , things like pipelining allow you to never hav
232.
▲
by
wycats
13y ago
I don't think "served from Rails" and "consumed by Ember.js" is quite right. It was designed to work with existing servers that have facilities for easily generating JSON (Rails, Django, various Node frameworks), and smart clients that want
233.
▲
by
wycats
13y ago
Indeed. In my experience, looser requirements in this kind of thing just leads to tears on the part of client and server implementations. I'll happily reduce some of the MUST s to SHOULD s or MAY s if it makes sense for the communication
234.
▲
by
wycats
13y ago
> I'm not sure about the name Good feedback. Many people have said this, and I'm thinking about an alternative. > Or phrased differently, why would I ever not want to use the "URL Template Shorthands" approach mentioned later? You c
235.
▲
by
wycats
13y ago
Thanks for the feedback :) Standardized paging seems to come up a lot, so it seems like a good thing to add once the core spec stabilizes. Optional sideloading also has come up a few times, and seems easy to add as a MAY in the spec. I ne
236.
▲
by
wycats
13y ago
> The proper layer for caching is HTTP, do we really want to end up with duplicated overlapping functionality between the layers? HTTP caching doesn't work well with compound documents that represent a graph of objects. The kind of cach
237.
▲
by
wycats
13y ago
How would you combine multiple authors into a single request? With IDs + a template, you can form a single request for all of the "people" you don't have yet. If you use URLs as IDs, which is one of the primary goals here.
238.
▲
by
wycats
13y ago
> What's the reason for the top level rel? It seems like it's just there to stop the urls from being repeated and to save space, but isn't that what gzip is for? It also makes it possible to cache things locally indexed on their IDs, an
239.
▲
by
wycats
13y ago
The references to Ember are in the introduction only and provide some historical context for the project. I believe that it's important for standards to come out of real experience, and that the context of that real experience will help oth
240.
▲
by
wycats
13y ago
And [this][1] looks similar to JSON API to you? [1]: http://www.odata.org/documentation/odata-v2-documentation/js...
More ›