rshm

i would look into Ubiquiti as well for network.

Game pairing in Go for example is usually a random pool (bingo; pick your number from a bowl), after that it is straightforward knockout.

It is not a 1-1 comparison but one distant example would be plain text html/css vs frontpage and dreamweaver. Over the time i have seen for a serious work done using plain texts instead of studio based design (may be specific to HTML?).

For any TODO or small notes i fall back to half sized index cards 3"x2.5".

For brainstorm use yellow legal pads with pilot V5 and tear them off once done.

One thing i do with all fountain pens are to resurface the nibs using dremel or grinding on any fine surface. Basically a hit and trial to get fine calligraphy like quality, writing after that is more consistent and in control.

http://aturon.github.io/

One area google translate could look at is the name identification from the context and using roman instead of literal translation.

This game is a mirror go upto move 72. Black player is https://en.wikipedia.org/wiki/Chou_Chun-hsun

Either on the first video or some news, i think i heard the ability to drive where the lanes are not clearly defined. Things such as snow would absolutely requires such reconstruction.

I was driven by courisity, no pressure of completion and had all the time in the world. The book was thick with complete programs with outputs instead of snippets. Book also had list of all core packages, class and their members. It helped to grasp the core libs before hand.

I would suggest a comphrensive book. I have not checked any Osborne reference series since then, but check if there are similar ones for python.

If the metadata (such as last modified) size of your index is small enough to upload to aws, you can also reduce your re-crawl efforts when they have a fresh release.

The linked post mentions dir_index default and tune2fs -l lists the dir_index under Filesystem features only.

Not knowing this default behavior, i was considering enabling dir_index explicitly to aid chocking rsync.

EDIT: I ran the reproduction code with 200K instead of 100K just to be sure. There was no problem creating file as well as copying all the files to a different folder. The disk was formatted about 3 months ago and mounted with default options "ext4 noatime,barrier=0 0 0" . On original as well as copied folder `ls | wc -l` still gives 200000.

Closest thing might be Xilinx Zynq or Stratix 10. Both are comparable PSoC, comes with ARM core but with high density FPGA instead of small CPLD.

The MX series from article adds DRAM in larger size and with larger bandwidth than what is available currently.

My understanding of PLD/CPLD vs FPGA is that the CPLD is based of EEPROM for logic cells which are programmed before deployment (With exceptions), and they are operational as soon they are powered up. They are generally small in terms of number of logic cells they offer.

FPGA in other hands are based on RAM. They are programmed / booted at the power on (Internal/External Flash). They become operational once the program/design is transferred from flash to RAM based logic cells. They offer large number of logic cells thus allows the implementation of complex designs.

Facebook Paper - PDF http://arxiv.org/pdf/1511.06410v2.pdf

Pachi Original Paper - PDF http://pasky.or.cz/go/pachi-tr.pdf

VULTR 2 GB INSTANCE dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync

    1024+0 records in
    1024+0 records out
    1073741824 bytes (1.1 GB) copied, 8.11451 s, 132 MB/s
    
    
    hdparm -tT /dev/vda
    
    /dev/vda:
    Timing cached reads:   25106 MB in  2.00 seconds = 12568.51 MB/sec
    Timing buffered disk reads: 496 MB in  3.02 seconds = 164.16 MB/sec

    hdparm -tT /dev/vda
    
    Timing cached reads:   8926 MB in  2.00 seconds = 4468.52 MB/sec
    Timing buffered disk reads: 542 MB in  3.00 seconds = 180.43 MB/sec


    dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync 
    1024+0 records in
    1024+0 records out
    1073741824 bytes (1.1 GB) copied, 32.0005 s, 33.6 MB/s