Live data from Hacker News

Hello, Tensorflow

oreilly.com

41–44 of 44 posts

Re: Hello, Tensorflow

#41
post #14

TensorFlow is admirably easier to install than some other frameworks I thought most frameworks are fairly easy to install in python, usually with a single call to pip. NLTK takes one "pip install nltk" and then "python", "import nltk", "nltk.download()" to download all the corpuses and miscellaneous data. Installing tensorflow seems complicated compared to that. # Ubuntu/Linux 64-bit, CPU only: $ sudo pip install --u…

Deeplearning frameworks aren't your normal machine learning frameworks. The real problem is CUDA, which isn't allowed to be distributed separately.

By comparison, here's what you need to install (manually!) for Torch on OSX:

  Homebrew
  Xcode
  cmake
  wget
  readline
  QT
  ffmpeg
  gnuplot
  opencv
  CUDA (and there's a whole other thread trying to get that to work..)
http://e-lab.github.io/html/wiki-torch7-installation.html

Re: Hello, Tensorflow

#42
post #19

Wow! I was going to post this but here it is already! I wrote (with a lot of help) the article there. I also jotted down some notes on the process of writing it with O'Reilly in case anybody's interested in that side of things: http://planspace.org/20160619-writing_with_oreilly/

Just a CSS critique: could you add "monospace" to the end of your list of monospaced fonts? I have perfectly good monospaced fonts on this computer, but none of them are Consolas, Menlo, Monaco, or Lucida Console, so I end up with a default proportional serif font.

O'Reilly tells me that this issue has been resolved as of last Friday. Does it look better for you now?

Re: Hello, Tensorflow

#43
post #19

Earlier quoted context omitted.

Just a CSS critique: could you add "monospace" to the end of your list of monospaced fonts? I have perfectly good monospaced fonts on this computer, but none of them are Consolas, Menlo, Monaco, or Lucida Console, so I end up with a default proportional serif font.

This might seem like an innocent change but it really is another HTML/CSS browser hell hole. If I remember correctly it was Jeff Atwood or jzy who taught me this lesson at a time when Stackoverflow was just out of Beta: If the keyword monospace is somewhere in your font stack some browsers use 13px as default font size instead of the usual 16px. The workaround used to be to use both , serif and monospace, in your fon…

O'Reilly tells me that this issue has been resolved as of last Friday. Does it seem better now?
Post reply on HN