Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wycats
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
63 ms
·
241.
▲
by
wycats
13y ago
Agreed. If I standardize pagination, I'll be using a "since" token, not pages (this is actually something Ember Data already supports, but weakly).
242.
▲
by
wycats
13y ago
Take a look: http://www.odata.org/documentation/odata-v2-documentation/js...
243.
▲
by
wycats
13y ago
The main reason was to unify patches to attributes with patches to relationships, which do require richer semantics. It also makes it really easy to add a compound PATCH (updates to posts/1/title, posts/1/rels/author, posts/2/body, etc. all
244.
▲
by
wycats
13y ago
JSON HAL is an document format only; it does not formalize a protocol. JSON API is a solution for any "smart" client that is capable of caching documents and intelligently limiting subsequent requests. In general, I believe it will be broad
245.
▲
by
wycats
13y ago
There are several reasons I chose not to use HAL: * HAL embeds child documents recursively, while JSON API flattens the entire graph of objects at the top level. This means that if the same "people" are referenced from different kinds of ob
246.
▲
by
wycats
13y ago
Also a fair point. The original reason for using Arrays (and something that still carries some weight with me), is that people expected that Arrays be presented in a particular order returned by the server. Indeed, the semantics of a to-man
247.
▲
by
wycats
13y ago
Actually, the current Ember Data protocol uses ?id[]=12&id[]=9&id[]=4. There's no good reason for the extra verbosity; it's pretty easy to split over commas and the current format is tricky to parse for platforms that don't already
248.
▲
by
wycats
13y ago
The `PATCH` mechanism is an HTTP verb (RFC 5789: http://tools.ietf.org/html/rfc5789 ) using a standard patching mechanism (RFC 6902: http://tools.ietf.org/html/rfc6902 ). Both are RFCs that seemed like good foundations to build on.
249.
▲
by
wycats
13y ago
OP here. Indeed. And importantly, this API makes it possible to restrict the query to a list of documents that the client doesn't already have from another source. In practice, once you start using compound documents with an identity map, t
250.
▲
by
wycats
13y ago
OOP here. There are a lot of these kinds of decisions that need to be made for an API like this. In general, I went with what we're already doing if there was a toss-up. A big strength of JSON API, imho, is that it's an extraction from a re
251.
▲
by
wycats
14y ago
I've been building: - a Rails plugin - a Rails app - an Ember app - Ember itself - Several small JS libraries that I hope to use in Ember Each of these projects gets its own tmux session (I didn't really know tmux before nitrous.io, and I h
252.
▲
by
wycats
14y ago
I've been using Nitrous.io (formerly Action.io) on my ChromeBook Pixel and loving it. I've been using my Pixel full-time as a development environment for a couple of weeks now, and haven't given up in frustration yet :) The Nitrous guys hav
253.
▲
by
wycats
14y ago
January 11, 2008. User id 4[1] :D [1]: https://api.github.com/users/wycats
254.
▲
by
wycats
14y ago
Does this mean that Chrome "broke the web" by being so fast while IE6 was still in circulation?
255.
▲
by
wycats
14y ago
> Every major competitor to Ember (including its predecessor, SproutCore) has a data layer that does more than pass the buck off to jQuery SproutCore had a robust data layer, but 2013-era frameworks mostly expose HTTP directly as the ab
256.
▲
by
wycats
14y ago
Totally agree. The OP posted at 4:05 a.m., when I was very much asleep. I've been a little bit less responsive this week in general as I've been participating in TAG[1] this week. I'm very sorry that our project came across as uncaring. [1]
257.
▲
by
wycats
14y ago
I totally agree that our getting started story could be much better. In fact, it's our primary focus as we move towards 1.0. Specifically: * We're actively working on a Getting Started Guide with live examples that walks the user through bu
258.
▲
by
wycats
14y ago
Not at all. That's precisely what the petition advocates for. If you are required to use the term "license" when your software contains DRM, then you aren't allowed to use the term "buy" when your software contains DRM. Therefore, this peti
259.
▲
by
wycats
14y ago
In this case, the "state" that we're talking about is "what state are you in". In other words, the router manages high-level state ("I am looking at a post now"), and provides long-lived controllers with data reflecting that state. So even
260.
▲
by
wycats
14y ago
I was delighted to see Bastion, a game I played on my Mac, available on the Chrome Web Store using Native Client ( https://chrome.google.com/webstore/detail/bastion/oohphhdkah... )
261.
▲
by
wycats
14y ago
Right now it's mostly a "roll your own" affair. Rails provides a decent system (via the asset pipeline) for people fully inside the Rails ecosystem, but something better really needs to exist. I'd bet that it will within a year (or maybe ev
262.
▲
by
wycats
14y ago
Good work Brian! I'm glad you ported my initial Ruby implementation to JavaScript, which will make it available to a much wider group of users! Special thanks to Erik Bryn for convincing Brian to do the port in the first place ;) The next s
263.
▲
by
wycats
14y ago
No. Please read this entire document on directives, which are a front-and-center feature of Angular: http://docs.angularjs.org/guide/directive . The transclusion snippet is pretty representative of this entire document.
264.
▲
by
wycats
14y ago
O_O A quick start guide definitely does not "go against" what we believe in. At EmberCamp, we had a slide dedicated to improvements we would like to make to the documentation. The first bullet was "Getting Started". http://cl.ly/image/0i3i
265.
▲
by
wycats
14y ago
If by interesting you mean totally misleading, then sure! The Ember.js version included is unminified, and the number of files reflect several small files rather than one big file. The goal of TodoMVC is to compare code style. But sure, we'
266.
▲
by
wycats
14y ago
For what it's worth, it's not clear how Object.observe will substantially improve the performance of large collections. For example, if you insert an item at position 0 of a 10,000 item array, Object.observe will publish a change for every
267.
▲
by
wycats
14y ago
Were you consulting them on Ember development aspects? We worked with Robin and Sam as community members over the past few months as they worked on Discourse. Frankly, they're both rock stars, and managed the entire project with surprisin
268.
▲
by
wycats
14y ago
Interestingly, as an early users of the software, I got mostly the exact opposite feeling. Build it for a real community and try to make it work within that community Ember used Discourse for the past several months. We provided a ton of
269.
▲
by
wycats
14y ago
I take this legal obligation seriously and am in the process of fulfillment (see other comments on this thread).
270.
▲
by
wycats
14y ago
I had publicly started Tilde about six months before starting the Kickstarter. I said that I would use the money to take time off from work to dedicate to Tokaido. I naïvely assumed I would be able to take that time off in a large block, bu
More ›