smizell

10 ms·

31.
by smizell 11y ago
I've been working on library that creates a queryable structure for trees like this. I prefer writing normal JS than to having some query language for it. var obj = minim.toElement({ a: 1, b: [ { c: 1,
32.
by smizell 11y ago
Or you could actually use XPath :) https://www-01.ibm.com/support/knowledgecenter/SS9H2Y_7.1.0/...
33.
by smizell 11y ago
It always feels like we keep reinventing Lisp. You could do something like: ['contains?', ['list', 1, 2, 3], 1] Instead of: { $contain: { foo: 1 } }, { foo: [ 1, 2, 3 ] }
34.
by smizell 11y ago
We're also working on a data format that allows for this use of arrays. https://github.com/refractproject/refract-spec/blob/master/r... We use it very similarly to how you would with Lisp, where the
35.
by smizell 11y ago
I wrote a very similar tool one time: https://github.com/smizell/geneva It is Lisp in JSON. I did it for fun, but thought it would a cool way to send instructions across the wire from the server to the client and back.
36.
by smizell 11y ago
I work at Apiary and we have a format called MSON for writing data structures in Markdown. https://github.com/apiaryio/mson/
37.
by smizell 11y ago
Got curious about how the spec is built. Source said: > Built with spec-md http://leebyron.com/spec-md/
38.
Decoupling the Mind of the API Designer(blog.apiary.io)
8 points by smizell 11y ago|0 comments
39.
by smizell 11y ago
Ah, very interesting! Thanks for the link.
40.
by smizell 11y ago
I actually created a hybrid of JSON and Lisp called Geneva [1]. It was a fun weekend experiment. I totally relate to how the author feels [1] https://github.com/smizell/geneva
41.
by smizell 12y ago
I thought the same of Orthodoxy. Chesterton just has a way with words and thoughts.
42.
by smizell 12y ago
Hiccup gives you HTML in Lisp https://github.com/weavejester/hiccup
43.
by smizell 12y ago
Definitely! :) Was just pointing out that this search engine was making discovery possible _because_ of hypermedia. Nicely done!
44.
by smizell 12y ago
I think a key here is hypermedia. APIs can only be machine-discoverable if there are hypermedia links pointing to them (which is how this helps). If there are no links, then some human must hardcode it. This also is a reason for including h
45.
Geneva: Lisp-Flavored JSON(github.com)
3 points by smizell 12y ago|0 comments
46.
JaneML: JSON-based HTML5 Superset(github.com)
3 points by smizell 12y ago|0 comments
47.
by smizell 12y ago
Cool, I'll keep an eye out. Any reason to use React+Mori over Om other than more familiarity with JavaScript??
48.
by smizell 12y ago
Do you have any code samples online of this combination? I'd be interested to see how these are used together, because they seem like a great fit.
49.
by smizell 12y ago
I live and work in the Midwest, and this is the situation I see a lot. We actually saw a local company move to a nearby city (two hours away) in order to find more talent, though they bumped up the salary to get that talent. I believe if th
50.
by smizell 12y ago
I think Blossom [1] switched to it. They had some articles on their blog about the switch [2]. [1] https://www.blossom.io/ [2] http://www.ramen.io/post/46936028144/we-are-switching-to-dar...
51.
Verbose Hypermedia Format(verbose.readthedocs.org)
1 points by smizell 12y ago|0 comments
52.
by smizell 12y ago
(author here) It definitely does! But the point was to play with hypermedia (REST), not really solve FizzBuzz.
53.
Solving FizzBuzz with Hypermedia(smizell.com)
12 points by smizell 12y ago|2 comments
54.
Converting Between Hypermedia Types(smizell.com)
2 points by smizell 13y ago|0 comments
55.
RESTful Static Site(smizell.com)
1 points by smizell 13y ago|0 comments
56.
by smizell 13y ago
This is also how Apache works with content negotiation, either with a type map or MultiView. https://httpd.apache.org/docs/current/content-negotiation.ht...
57.
by smizell 13y ago
Regarding content negotiation, the idea is to put all of the media types in the Accept header that the client can understand (instead of saying I want such and such representation). You then request a URI and the server decides which repres
58.
by smizell 13y ago
The big benefit the author is describing comes from content negotiation and hypermedia types. The idea behind content negotiation is that a client and a server should decide and agree upon the media type that will be used in the communicati
59.
by smizell 13y ago
What you're describing has already been done by SOAP+WSDL. Even the term "endpoint" is from the SOAP world, not the REST world. The IDE (usually) does all the heavy lifting of generating and consuming of these endpoints and t
60.
by smizell 13y ago
Doesn't true REST (not the RPC kind) address these same things when implemented? Content types and hypermedia to allow clients to know how to access the data and follow links to linked data? If we all built our APIs with a registered c

More ›