xiaq

49 ms·

481.
by xiaq 12y ago
To mod: please do not remove the "pipebackend" from the title since it is the reason I'm sharing this... Perhaps I should have written it as [PipeBackend].
482.
by xiaq 12y ago
Thought of submitting this when another PowerDNS submit came up. The pipe backend is a very interesting one since it allows you to hack up a custom DNS resolution mechanism very easily. For instance I built a simple backend that synthesizes
483.
[PowerDNS] Backends in detail: PipeBackend(doc.powerdns.com)
2 points by xiaq 12y ago|2 comments
484.
by xiaq 12y ago
Well, it's always safer to use widely used solutions in production. That way you encounter fewer bugs, and it's much easier to find a workaround in case you do encounter one.
485.
by xiaq 12y ago
Most of the team? I only know that Rob Pike and Russ Cox are Google employers. And I have the impression that they are working mostly on Golang and some distributed infrastructures. Did they employ any other inferno developers?
486.
by xiaq 12y ago
Answering the second question: you won't want to use it in production, but if you have ever been intrigued by one of those Unix philosophy preaches, you should definitely take a look at it. It takes the tool philosophy (build simple to
487.
by xiaq 12y ago
plan 9 is the earlier effort of re-engineering Unix and runs on hardware. It was meant to replace Unix, but it never did. With inferno they went the VM route (the dis VM) and built it so that it runs on myriad platforms, from Unix and Activ
488.
by xiaq 12y ago
"fun" is even funnier than "func"! ML etymology sounds pretty plausible (I didn't know ML uses fn) since I can see there is a strong influence of ML on Rust.
489.
by xiaq 12y ago
fn is my favorite keyword for function definition. "function" is too long. "def" doesn't say anything about functions (unless you read it as DEfine Function). "func" sounds too funny. "defun" alw
490.
by xiaq 12y ago
Replying to myself: A little googling reveals that it actually is exploitable [1][2][3]. 1. http://stackoverflow.com/questions/2913618/how-is-integer-ov... 2. http://rogunix.com/docs/Reversing
491.
by xiaq 12y ago
It has always made me wonder why there is no direct way for checking for overflow in most languages, since most CPUs do have an overflow flag. Dedicating an operator or keyword is probably too much, but at least it can be a routine in std
492.
by xiaq 12y ago
Interestingly, they seem to only stop pre-installing Google Play recently and they claimed that it's due to Chinese policies [1]. According to my knowledge it should be more of Google policies... In the same link [1] they also provided
493.
by xiaq 12y ago
> 3) Speaking of ecosystems, does this thing have Google Play (I looked on their site, but couldn't get a clear answer - no Google app logos though...)? If not, it's really going to struggle in Western markets. It doesn't.
494.
by xiaq 12y ago
On a related note, parsing Chinese could be much harder since the first step, identifying word boundaries [1], is already hard enough... 1. https://en.wikipedia.org/wiki/Text_segmentation
495.
by xiaq 12y ago
see the "copyright infringement" section near the bottom of http://www-cs-faculty.stanford.edu/~uno/abcde.html
496.
by xiaq 12y ago
> * Lifetimes completely confuse me, as it seems like they would be handled by garbage collection? Interesting misconception :) Lifetime is used to avoid garbage collection. By expressing the lifetime of a variable preciously in the co
497.
by xiaq 13y ago
As a recent comment suggests it's a "kanban board".
498.
by xiaq 13y ago
A bit off-topic, but I like how pocoo.org uses different fonts for different projects: Flask: Georgia for text, Garamond for titles Werkzeug: Lucida Grande for text, Ubuntu for titles And now click: Ubuntu Mono for text, Open Sans for title
499.
by xiaq 13y ago
He/she is complaining about the webpage being too wide.
500.
Error vs. Exception(haskell.org)
2 points by xiaq 13y ago|0 comments
501.
by xiaq 13y ago
For anyone wondering, uzbl stands for “usable”.
502.
by xiaq 13y ago
for anyone wondering, uzbl stands for “usable”.
503.
by xiaq 13y ago
Interesting, but if I were the author I would definitely avoid the name "gitsh" since some googling reveals there have been prior arts under exactly the same name: https://github.com/caglar/gitsh https:&#x2F
504.
by xiaq 13y ago
Yeah, after reading this I can imagine myself translating "we have a cloud" to "WE GOT SERVERS LOL" and the like...
505.
by xiaq 13y ago
> Last year, we created a new team at Mozilla to explore one specific area of the Web that’s grown with the explosion of mobile devices — the cloud (sometimes called Internet servers). Hey Mozilla, you are too honest about the cloud thin
506.
by xiaq 13y ago
Chinese here. Wow it's actually hilarious to read how some western people see the PLA exactly the way we see DPRK army. I have no military experience, but with access to Chinese sources, I feel justified to point out some obvious error
507.
by xiaq 13y ago
> The problem with Perl, IMO, is that there are too many clever ideas and it takes way too much to fit all of them together (and they never give up and ditch some of the less clever ones like Python people routinely do), which is why Per
508.
by xiaq 13y ago
Yeah, you can actually find many many clever little ideas in Perl 5 and 6. I even find reading the Perl 6 synopsis ( http://perlcabal.org/syn/ ) entertaining. The problem with Perl, IMO, is that there are too many clever
509.
by xiaq 13y ago
> Perhaps the open source community is currently working on something like PowerShell's PSDrives, but adoption by the teams producing large apps would be critical to its success. plan 9 ( http://plan9.bell-labs.com/pl
510.
by xiaq 13y ago
And psh: http://gnp.github.io/psh/

More ›