Here are two other related links :
http://www.ghacks.net/2013/03/14/the-ultimate-google-reader-...
http://reviews.cnet.com/8301-19512_7-57574201-233/google-rea...
HN user
Here are two other related links :
http://www.ghacks.net/2013/03/14/the-ultimate-google-reader-...
http://reviews.cnet.com/8301-19512_7-57574201-233/google-rea...
Downloads is a valid missing (or rather removed) feature, but as others have pointed out, this feature at core is not very different from rebase.
Bangalore - Fullstack software engineers @promptcloud
It should be titled " Amazon, Apple and the beauty of high volumes"
This looks good. For cpu and memory checks I find htop to be more lightweight and functionality wise is pretty good too. It doesn't show disk stats though, for which something like atop should be used.
http://blog.oscarbonilla.com/2009/05/visualizing-bayes-theor...
gives pretty intuitive visual explanation of Bayes theorem .
It depends upon the hardware you have. But if you have a decent machine say EC2 small instances or something like http://www.hetzner.de/en/hosting/produkte_vserver/vq19 it should not be an issue. We use similar setup for promptcloud and that machine has numerous other things running too, there is no noticeable load.
>I'm a bit stumped on toggling comments, though. Any ideas?
" comentify/uncommentify a line or a visual block"
function! Komment()
if getline(".") =~ '^[ \t]*#'
let hls=@/
s/^\([ \t]*\)#\(.*\)$/\1\2
let @/=hls
else
let hls=@/
s/^\([ \t]*\)\(.*\)$/\1#\2
let @/=hls
endif
endfunction
:vnoremap // :call Komment()<CR>
:nnoremap // :call Komment()<CR>
If you want to use c style comment :
function! Komment()
if getline(".") =~ '^[ \t]*\/\*'
let hls=@/
s/^\(\s*\)\/\*\(.*\)\*\/\(\s*\)$/\1\2\3/
let @/=hls
else
let hls=@/
s/[ \t]*$//
s/^\(\s*\)\(.*\)\(\s*\)$/\1\/\* \2 \*\//
let @/=hls
endif
endfunction
:vnoremap <silent> // :call Komment()<CR>
:nnoremap <silent> // :call Komment()<CR>
edited formattingDarcs is good for personal use, but I moved away primarily because of the exponential merge problem. I think darcs2 takes care of it in most of the cases but NOT always. That is a big question mark for production repository. Darcs is easy to get started with though - to anybody interested I recommend this link - http://blog.interlinked.org/tutorials/darcs.html .
On the other hand if you want to move from darcs to git , use the following - https://github.com/purcell/darcs-to-git
Also SQS should accept utf-8 in message body rather than a restricted set of characters.
Following is a great resource for Concurrent programming without locks and software transaction memory : http://www.cl.cam.ac.uk/research/srg/netos/lock-free/