Here's a brief analysis of RPC vs. REST based on one person's opinion.
| # Data Structures | |
| ## Entity (object) | |
| An Entity is a URI-addressable resource that has properties and actions | |
| associated with it. It may contain sub-entities and navigational links. | |
| ### Properties | |
| - class (array[string], optional) | |
| Describes the nature of an entity's content based on the current | |
| representation. Possible values are implementation-dependent and |
| /* | |
| from @rem | |
| https://twitter.com/rem/status/729628084115247104 | |
| */ | |
| @namespace url(http://www.w3.org/1999/xhtml); | |
| @-moz-document domain("twitter.com") { | |
| div[data-component-term="user-recommendations"], | |
| div[data-component-term="trends"], | |
| .promoted-tweet, |
I say "animated gif" but in reality I think it's irresponsible to be serving "real" GIF files to people now. You should be serving gfy's, gifv's, webm, mp4s, whatever. They're a fraction of the filesize making it easier for you to deliver high fidelity, full color animation very quickly, especially on bad mobile connections. (But I suppose if you're just doing this for small audiences (like bug reporting), then LICEcap is a good solution).
- Launch quicktime player
- do Screen recording
| var sonos = require('sonos'); | |
| var Scout = require('zetta-scout'); | |
| var util = require('util'); | |
| var SonosDriver = require('./sonos_driver'); | |
| //We inherit from scout to get some Zetta functionality | |
| var SonosScout = module.exports = function() { | |
| Scout.call(this); | |
| }; | |
| util.inherits(SonosScout, Scout); |
| #!/usr/bin/env python | |
| """ | |
| This script is designed to generate a simple HTML file with _all_ of your | |
| Pinboard.in bookmarks. | |
| You should edit the `username`, `password`, `bookmark_filename`, and `tag` | |
| variables. | |
| Requirements: |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
Format: 1A Host: http://blog.acme.com
NOTE: This document is outdated. Refer to the actual API Blueprint examples.
Welcome to the ACME Blog API. This API provides access to the ACME Blog service.
| data:text/html, | |
| <style type="text/css"> | |
| #e { | |
| position:absolute; | |
| top:0; | |
| right:0; | |
| bottom:0; | |
| left:0; | |
| font-size:16px; | |
| } |
| data:text/html, <style type="text/css">#e{position:absolute;top:0;right:0;bottom:0;left:0;}</style><div id="e"></div><script src="http://d1n0x3qji82z53.cloudfront.net/src-min-noconflict/ace.js" type="text/javascript" charset="utf-8"></script><script>var e=ace.edit("e");e.setTheme("ace/theme/monokai");e.getSession().setMode("ace/mode/ruby");</script> |
