Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tensorflow sucks

nicodjimenez.github.io

Post reply on HN
Print view View original

91–100 of 133 posts

Re: Tensorflow sucks

#91

Post by stared »

sangnoir wrote: post #67

I'm probably being overly cynical, but this is (indistinguishable from) a "growth-hack" submarine article by the author to promote their tool. There is hardly any substantiation to support the assertions. Tucked right at the end: > If you want a beautiful monitoring solution for your machine learning project that includes advanced model comparison features, check out Losswise. I developed it to allow machine learning…

I don't think so. Even even if - then ineffective, as a link to their tool is covered behind pages of text.

> There is hardly any substantiation to support the assertions.

How about side-by-side TensorFlow and PyTorch comparison?

...though, for experiment tracking (and experiment running) I recommend https://neptune.ml/.

Re: Tensorflow sucks

#92

Post by matasuge »

KirinDave wrote: post #82

Usually I'm on the hook for being open minded about programming languages in this forum, but I'm putting my foot down. I really hope at some point this entire universe gets liberated from Python at some point. Even R would be more palatable. Both these examples are awful , error prone, obfuscated, and beholden to Python's difficulties with large sums of data.

go back to your cave and write some assembly you elitist neanderthal

Re: Tensorflow sucks

#93

Post by harry8 »

foobarchu wrote: post #65
libeclipse wrote: post #42

Earlier quoted context omitted.

Lmao not sure why this was down-voted. Utterly destroyed your quotation, and gave me a giggle.

It didn't "utterly destroy" the quotation. It's pretty easy to argue the virtues of cannibalism, it's just that for modern day society they do not trump the downsides. For example, cannibalism has successfully prevented death by starvation (e.g. the Donner Party), and it reduces the need for disposing of the dead. It's an application of reduce-reuse-recycle. Some species of other animals practice it as part of their…

You don't seem able to argue the other side here...

I refuse to name the thing that's impossible to argue for for reasons of good taste, but you know what it is. I hope not from any experience.

Re: Tensorflow sucks

#94

Post by rkangel »

yongjik wrote: post #54
CompleteSkeptic wrote: post #9

An appropriate quote: "If you can't intelligently argue for both sides of an issue, you don't understand the issue well enough to argue for either." There are many people for whom the declarative paradigm is a huge plus. I would say there are at least 2 major approaches in running fast neural networks: 1. Figure out the common big components and make fast versions of those. 2. Figure out the common small components a…

After being exposed to several declarative tools during my career, I must say they age poorly: make, autoconf, Tensorflow, and so on. They may start out being elegant, but every successful library is eventually (ab)used for something the original authors didn't envision, and with declarative syntax it descends into madness of "So if I change A to B here does it apply before or after C becomes D?" At least Tensorflow…

I believe that make's declarative is not the cause of it's problems at all - it's poor syntax and lack of support for programming abstractions is what makes it clunky to use.

Something like rake, which operates on the same fundamental principles (i.e. declarative dependency description) but using ruby syntax has aged better.

Re: Tensorflow sucks

#96

Post by antonvs »

harry8 wrote: post #93
foobarchu wrote: post #65

Earlier quoted context omitted.

It didn't "utterly destroy" the quotation. It's pretty easy to argue the virtues of cannibalism, it's just that for modern day society they do not trump the downsides. For example, cannibalism has successfully prevented death by starvation (e.g. the Donner Party), and it reduces the need for disposing of the dead. It's an application of reduce-reuse-recycle. Some species of other animals practice it as part of their…

You don't seem able to argue the other side here... I refuse to name the thing that's impossible to argue for for reasons of good taste, but you know what it is. I hope not from any experience.

Using emacs?

Re: Tensorflow sucks

#97

Post by jacquesm »

TheMagicHorsey wrote: post #85
ninjakeyboard wrote: post #70

I'm not a comp-sci grad and I worked at Google for a bit after a startup I was at was acquired. I didn't proceed far after that 2 years due to the need to commute and/or relocate but I had a clear path into full time work without much else. Although I was granted a bit of a pass, I believe anyone can work at Google given they are 1) slightly above average and have learned every base that they run into in reasonable d…

One should also ask the question: would you want to work at Google today. This is not the Google of 2002 ... or even the Google of 2010. 2017 Google is like 1999 Microsoft. Lots of brilliant people working on heavily resourced projects ... but also significant bureaucracy and many political animals in what was formerly a pristine engineering "garden of eden". You can see a lot of Google projects struggling now, and m…

> Nobody ever got fired at Google for spending all day brilliantly arguing on Google's internal newsgroups

There was a pretty high profile example of this not all that long ago.

Re: Tensorflow sucks

#98

Post by DanBC »

jacquesm wrote: post #97
TheMagicHorsey wrote: post #85

Earlier quoted context omitted.

One should also ask the question: would you want to work at Google today. This is not the Google of 2002 ... or even the Google of 2010. 2017 Google is like 1999 Microsoft. Lots of brilliant people working on heavily resourced projects ... but also significant bureaucracy and many political animals in what was formerly a pristine engineering "garden of eden". You can see a lot of Google projects struggling now, and m…

> Nobody ever got fired at Google for spending all day brilliantly arguing on Google's internal newsgroups There was a pretty high profile example of this not all that long ago.

That was decidedly not "brilliant" arguing.

Re: Tensorflow sucks

#99

Post by dx034 »

jacquesm wrote: post #97
TheMagicHorsey wrote: post #85

Earlier quoted context omitted.

One should also ask the question: would you want to work at Google today. This is not the Google of 2002 ... or even the Google of 2010. 2017 Google is like 1999 Microsoft. Lots of brilliant people working on heavily resourced projects ... but also significant bureaucracy and many political animals in what was formerly a pristine engineering "garden of eden". You can see a lot of Google projects struggling now, and m…

> Nobody ever got fired at Google for spending all day brilliantly arguing on Google's internal newsgroups There was a pretty high profile example of this not all that long ago.

For spending all day in internal newsgroups or for posting one article that went viral?

Re: Tensorflow sucks

#100

Post by syllogism »

serveboy wrote: post #95

Quick shout out for DyNet! The API is so simple and intuitive even a two year old (a prodigious one) can use it.

DyNet is also vastly faster than Tensorflow for realistic NLP models, especially on CPU.

http://dynet.readthedocs.io/en/latest/index.html

If you're doing the sort of work that would be published at ACL or EMNLP, DyNet is a really good choice.

Post reply on HN