653 karma · joined June 6, 2012
https://daliwali.neocities.org
Looks like axiom is coupled to RDBMS, while fortune tries to abstract away the data store (there are mongodb & postgres adapters) by providing a contract for reading/writing data. virtus looks very similar to the implementation of record type in fortune, has some extra features such as type coercion and lacks some features such as foreign keys.
if you're interested in query implementation have a look at how the postgres adapter maps the adapter contract to sql: https://github.com/fortunejs/fortune-postgres/blob/master/li...
What troubles me is that this tool seems completely unrelated to Facebook's business so why must they assert ownership of their employee's side project? On the other hand, it could be the author's intent to give up their rights to Facebook, which seems dumb, there's nothing the author could gain from that other than the Facebook brand in front.
Some media types do consider their applicability over multiple protocols, for example: http://amundsen.com/blog/archives/1151
The good:
- It opens a path for standardized tooling among API clients. Rather than having a whole mess of JSON-over-HTTP clients with a hard-coded understanding of the particular API, one could theoretically use a hypertext client to interact with any API using this standard.
- It establishes a baseline of what an API server must implement.
The bad:
- It tries to control not just the media type, but the protocol (HTTP) and server implementation. This is problematic because it dictates how your server must implement its routes, and is tightly coupled with HTTP.
- It tries to be very prescriptive, but it cannot cover all edge cases without being exhaustive. This comes at a heavy burden for implementers to get every part of the specification correct. Despite this, some extremely basic features are missing, such as providing an index document so that a client can enter the API knowing only a single entry point (as it stands now, clients must have a priori knowledge of what resources exist on the server).
The ugly:
- Since so many parts of the base specification are optional MAYs, and there is no prescribed mechanism for feature detection, there is no way to figure out if a server supports a particular feature of this spec without trying to do something and failing.
- The spec has made many breaking changes on the road to 1.0 (as other commenters have mentioned, and there is still room for breaking changes).
At this point, I think that this project gained traction due to the clout of the original authors (Yehuda Katz and Steve Klabnik) and the promise of no-more-bikeshedding, though I would argue that the bikeshedding has just shifted from particular APIs to the spec. Disclosure: I authored and maintained some libraries that implement this spec, and authored another media type for hypertext APIs.
Object.keys(window).filter(x =>
window[x] instanceof Function &&
!/native code/.test(window[x].toString()))
120 user-defined global functions, and that is not counting all global variables... yikes!(edit: if you're using Chrome, `Object.keys(window).length` gives you 260)
Case in point: I could force myself to improve upon a real-time bidding algorithm, resulting in more winning bids and targeted advertisements to appear on a largely captive and passive audience. Perhaps aspects of the bidding system could be improved to use less CPU cycles, memory, saving cost on the infrastructure to run it. I could get into the finer details of the time-complexity of every operation.
But why should I be expending my effort, a part of my lifetime, on helping to sell something people don't need? To the benefit of big corporate brands while they pay me a pittance of their enormous profits? A major problem with this "screw motivation" philosophy is that it encourages more mindless work in favor of the status quo. The quintessential codemonkey churning out code as if that is its purpose to follow orders from above. http://en.wikipedia.org/wiki/Little_Eichmanns
Another misconception the author has is that someone has to be in the right emotional state to be motivated to do something, to which I reply emphatically FUCK NO. Things don't just get done out of an emotional urge to do things. I am not always feeling enthusiastic about my side projects but I am highly motivated to do them even if it involves dry reading of technical specs. With lots of discipline and little motivation I could plod through the boring parts and forget about what I was trying to do (and this is what I feel most schools optimize for).
Pedigree and pedantics have taken precedence over hacking and creative problem solving, particularly in the Silicon Valley where a Stanfordcal degree and Googfacetwit work experience is expected.
I remarked how non-RESTful this API is, which may have been the motivation for the title of this submission [2].
Yep, this is someone who tech nerds can honestly relate with. Easily accessible. Uh huh.
http://www.damemagazine.com/2014/05/23/amazon-killing-my-sex...
Stop labelling every API that operates over HTTP as a REST API, this one clearly isn't.
>Some folks probably should feel tied down by their reputation/ego.
I'm pretty sure that implies that you don't want the "bigots" in your worldview to be able to express themselves anonymously.
Also, Fortune should work out the box with Ember Data and my JSON API adapter: https://github.com/daliwali/ember-json-api . Not to say that you should ditch Angular, but it will probably need quite a bit of modifications to its data layer to get it working with the JSON API spec.
I will be working on a full, non-trivial example of what an Ember.js + Fortune.js application can be in the coming week(s). There is a current implementation that's in production at my company, but its unfortunately closed-source.
In the future, I might actually cut out Express from this framework, but still accept Connect middleware. The reason for that is because I don't want the user to be concerned about routing or having to manually set routes, so a thinner router might be in order.