2
points
apples2apples
Joined 314 karma
- 1 point
- 460 points
- apples2apples parentCareful Anaconda will change the license on you and then sue...
- Wow, they really threatened a hospital!
- I'm sorry but deep learning is only a very small part of why Python is preferred by data scientists. The fact that Python was the the preferred language is why the enormous corporations wrote bindings to them. Both of these frameworks exist in the Julia ecosystem.
- 1 point
- 40 points
- I would need some sort of contact details to shoot you a message, or perhaps I'm not kewl enough to know how to do that in hacker news... This thread leads me to believe that it can't be done, but that was nearly 3000 days ago https://www.hackerneue.com/item?id=1028763
- Anything labeled Watson get out the checkbook!!! My guess is that this thing will do less than Amazon Lex and cost $$$$.
Reading the buzz on the page, I don't see any difference between this and the chat api Watson released last year. The one they wanted like $60K for my startup to use for 50 conversations a day....A DAY!!!
Watson == overhyped, devalued brand
- 107 points
- 2 points
- "There has been very little open source that has made its way into broad use within the HPC commercial community where great emphasis is placed on serviceability and security. There is a better track record in data analytics recently with map/reduce as a notable example. ... It should be noted that the most significant consumption of open source software is China and it is also the case that the Chinese are rare contributors to open source as well. Investments in open source or other policy actions to stimulate creation are likely to produce a disproportionate benefit accruing to the Chinese."
- 2 points
- Currently in a project situation with no budget and blue sky dreams. I can't say how much I love this article enough.
I think one of the unspoken insights here is: give your projects a budget.
I've been with two startups now that didn't do this and see them either think there is no budget or there is infinite budget. Ultimately both CEOs would say "Just come ask me" which means that you now have to pester the busiest person at the company to get a budget. It is effectively giving the project no budget.
- My reasoning is that Mr. Itoh put an intern in charge of a system that could cause major damage. It's like giving the intern keys to your AWS console and shitting your pants when he terminates all you EBS root disks that you didn't back up.
Mr. Beck wasn't culpable because he didn't understand the full effects of his actions or the tension of the current situation. Ioth should not have let Beck in the door that morning and he should not have given that much power to the intern.
- He was the one who was more responsible for the incident than the intern.
- 1 point
- Itoh should have been fired.
- 1 point
- 2 points
- My favorite part of this service is the Continuous Integration of your build.
http://docs.binstar.org/continuous_integration.html
One stop shop to keeping your builds up to date with master.
$ conda -c <your_channel> update <package_name>
- 8 points
- 5 points
- I love how you call Julia a wannabe but then go on to list features it has to build up the newer greater Python =P
- 3 points
- Sure, consider a compiler that produces an (foo.o) object file and an annotation (foo.a). Now if a target requires both foo.o and foo.a you have to create two targets on them (even though its really one command).
You can do implicit rules which requires a very verbose makefile, which is what automake and other make generation tools do. God help you figure out what went wrong.
If you make people go to a directory approach you've now imposed a new structure on their code. One reason for the multitude of packages is each one matches their target community better.
- Misses the fundamental point that Make is broken for so many things. To begin with you have to have a single target for each file produced. Generating all the targets to get around this is a nightmare that results in unreadable debug messages and horribly unpredictable call paths.
nix tried to solve much of this, but I agree it can't compete with the bazillion other options.
- Not really, the internet points to this doc: http://www.multicians.org/shell.html Where Louis Pouzin of Multics claims to have coined it.
Ken Thompson describes it here http://v6shell.org/history/unix/unix.pdf
Looking around, this seems more interesting (implying it is a metaphorical name of a prophet's shell listening): http://unix.stackexchange.com/questions/14934/why-was-the-wo...