deno

92 ms·

901.
by deno 15y ago
You can automate GUIs using accessibility controls and/or desktop message bus. If an app is modular, as it should be, it does not matter one bit how many UIs it exposes. Also all CLIs are not the same — try automating ncurses application.
902.
by deno 15y ago
It's preferable to return correctly annotated (with elements from aforementioned namespaces) XML, rather than ‘plain XML.’ My point was, that this vocabulary already exists and there's no reason to invent new (incompatible) one. If you thin
903.
by deno 15y ago
Well, yes, if the content is inter-connected this is more tricky. Xml:id assumes unique identifiers within scope, and with multiple documents that would require a global scope, something that is not standardized and problematic (it'd requir
904.
by deno 15y ago
Well, I only care for public Web APIs. Though if you're not writing your documents by hand, I don't see how the syntax matters (it's just library then, anyway). And if you are writing your documents by hand, there are better solutions tha
905.
by deno 15y ago
YAML specifies standard way of including multiple documents in a single stream/file. With XML (assuming XSD-compatible parser), you can always extend the NS and have several documents in a single container (thus single stream/file), but I d
906.
by deno 15y ago
You will reinvent XML with uglier syntax, all while hurting yourself and Open Web. I've managed to somehow get into that argument before, so maybe there's something worth reading there: [1], [2]. [1] http://news.ycombinator.com/item?id=262
907.
by deno 15y ago
No mention of IANA's link relations[1], OpenSearch[2] and Atom[3] which seems to cover almost anything and beyond what ‘HAL’ specifies. For JSON, JSONSchema specifies standard way of including hyperlinks in a document, but of course no one,
908.
by deno 15y ago
Website is available in English. You should have no problem communicating in English with their customer support, as well. Also, it's KVM based, in case anyone is wondering.
909.
by deno 15y ago
You can navigate using keyboard (j/k).
910.
by deno 15y ago
> Lots of people "log out" by letting their session expire; this would merely get them back in the game faster. I'd expect, that someone that is going to employ auto-login URLs, is not going to be shy in using ‘forever’ login cookies an
911.
by deno 15y ago
The only situation you're targeting, then, is when a user intentionally logged out (in non-privacy mode) in the past (because otherwise they wouldn't have the half-cookie). Is it really desirable to log in them automatically in such cases?
912.
by deno 15y ago
map() returns an iterator in Py3k. > python3.2 -m timeit "( x**3 for x in range(10000))" 100000 loops, best of 3: 2.67 usec per loop > python3.2 -m timeit "[ x**3 for x in range(10000)]" 100 loops,
913.
by deno 15y ago
My experience opening .mdb file on Linux: 0. Make sure Kexi is installed. 1. Click on it. It's numbered from 0, because Microsoft Access isn't a standard part of Windows either.
914.
by deno 15y ago
This is like XML Myths 101. > xml seems too bloated To cite Wikipedia¹, “The XML encoding may therefore be shorter than the equivalent JSON encoding.” Please provide a fragment of XML document that is significantly more verbose than its
915.
by deno 15y ago
The best of both worlds is to have a fake system—that is booted automatically, without any password etc. and with installed spyware—alongside your actual OS, encrypted and hidden. You could even just keep data on your disk and have /boot on
916.
by deno 15y ago
That's not entirely Apples–Apples. XML was, in fact, designed with all those things in mind. Here is the 2nd design goal and its rationale, from 1996 draft specification[1]: > 2. XML shall support a wide variety of applications. > N
917.
by deno 15y ago
You can just as well use XML. The XSD list data-type makes for great building block for structured arrays. For example: Schema: <xs:element name="series"> <xs:simpleType> <xs:list itemType="xs:double
918.
by deno 15y ago
Well that's the point, isn't it? XML unifies various independent ecosystems. At the very least, if defines such essential things like data and time representation formats, whereas JSON doesn't even attempt to do that. But then XML goes furt
919.
by deno 15y ago
> If you just need a light-weight API that is only ever going to be REST orientated, then use JSON. I disagree with that assertion. There is nothing open Web can possibly gain by adopting JSON for its APIs. In a heterogeneous ecosystem,
920.
by deno 15y ago
It might be, but you're dismissing streaming the torrent directly. If your client can use moving window to select parts—instead of just doing it randomly—you could start watching your show without waiting for 100%. This does not require sup
921.
by deno 15y ago
Hover on it with your mouse.
922.
by deno 16y ago
My friends and I did that in 2005 with Google Reader. But fair enough, the project looks nice. I'd only suggest to implement caching better: 1) Make /get_user_feed.php return only list of stories. E.g. [ http://.../story1 , http://.../stor
923.
by deno 16y ago
So, content creators convert their RSS feeds to Twitter feeds and Readstream then converts them back again? Seems pointless. Why not just use the full feed in the first place (if that's what you want, instead of the <140 chars synopsis)
924.
by deno 16y ago
> I often think that, via REST APIs and content negotiations, API can become browseable and self-descriptive but I've yet to see any example of such a thing. It should be trivial with AtomPub/GData/OData APIs. REST itself is not specifi
925.
by deno 16y ago
Those are not restrictions to REST, since REST doesn't make any specific claims about how to use things like filtering, sorting etc. Google created GData2 as an extension to AtomPub format, which only specifies a common envelope for resourc
926.
by deno 16y ago
But that's just because of a general ignorance of how HTTP protocol works. If someone were to be explained, how it should work from the beginning, I'm sure they'd have no problem with grasping the subject. Actually some Google engineers do
927.
by deno 16y ago
Okay, first this was of course nit-picking, as I just hoped to get across the point, that REST is not just pretty URLs. > Except those are of course guidelines Well, obviously. > Instead of a list of methods, you get a list of metho
928.
by deno 16y ago
HTTP makes some simple guarantees in its spec regarding to the methods used. For example, GET must never have side effects. POST, PUT, DELETE always have side effects. This simple guarantees enable software like HTTP proxies to work properl
929.
by deno 16y ago
REST is as simple as it gets. You could make that argument if someone were to advocate using REST outside of HTTP. But HTTP is inherently REST, so you should have a good reason to not use REST rather than the other way around.
930.
by deno 16y ago
This can be done on top of REST API with your server acting as a client to your own API. Actually, that way it'll probably be possible to implement it much safer. And what's the use case anyway? Are you going to perform those requests from

More ›