skysight-inc/HackerNews huggingface dataset:
Only thing I took issue with was "Instead, explicitly define your servers in your configurations for as long as you can."

Maybe you can get away with this for a small scale deployment, but "as long as you can" sends a bit too mixed of a message. You should only defer a service discovery implementation until you get to the point where you have more than one read path in your stack.

IMO, as soon as you go from load balancer -> app -> cache -> database to having a services layer you should start thinking service discovery.

The simplest bandaid is to leverage DNS as much as possible until you get even bigger, and use static CNAMEs.
DockerCon today: New Relic uses docker to make deployment easy
HEEERRRROOOOOO
>> ssh -p but scp -P

I hate inconsistent command line interfaces, too. If you type `ssh` it dumps usage information. Most commands will respond to `command --help` (but not ssh, irritatingly). Failing that, you can write shell functions to wrap your own interfaces around commands -- I do this all the time.
furka herro me bak god dammiiiiiiii
ArchiveTeam rescues Justin.tv videos
Did you ever try to give people the option to filter by school district or school district ranking?
Wasn't a federal agency; instead a subdivision that has 2% of the US population. So, it's possible in a hundred years, most such bureaucracies won't see a single such case.

Caseworkers don't Google extreme scenarios regarding obscure words ("chimerism") that they've probably never heard of before. Apparently, neither the mother nor her own obstetrician nor her lawyer came up with this theory, either, for quite a while, so who's fault is that? (The people with the most at stake couldn't find the magic research promptly, either.)

It wasn't until after the 2002 paper about the Keegan case, and then other media coverage of this Fairchild case, and then followup stories/dramas and more recent research, that people outside of research had any idea anything like this could happen. No, low-level state caseworkers are not going to come up with the idea themselves. And the fact they kept running tests, including monitoring a live-birth-and-immediate-DNA-test, and deferring final judgement, indicates that the system was entertaining the possibility that this was an edge case.

There's some serious hindsight bias in the know-it-all criticisms here.
As mentioned in the article, rack stare [1] is in the app store. So masturbation bad, sexual harassment good?

[1] https://itunes.apple.com/us/app/rack-stare/id385786751?mt=8
Well, it certainly would depend on the use case and the quality would be influenced by both the scoring threshold and extent/quality of training materials. Using large data sets, with a particularly difficult lowest sufficient score, could produce a small quantity of highly relevant and substantive content. If the purpose is to discover a handful of articles in a specific subcategory (ex. theoretical physics) that a user could confidently share to social media - then there is a significant utility to the service - not just a business case.

What would this service have to offer for you to actually pay for it? Of course you could say you wouldn't pay for it, simply curious...
To test on what audience? There are hundreds of things I'd rather be hacking than a personal copy of some forum software.

> You're submitting too fast. Please slow down. Thanks.

fuckin thing won't even let you have a conversation ...
This is a very interesting project! I backed it.

I've only tried Xiki in a semi-broken state for now, via the SublimeXiki plugin and with Ruby 2.0 (which mostly doesn't work).

One question I have is how are you planning to handle navigation? E.g. when a command produces large output, it isn't very convenient to scroll around in the file. I didn't see this addressed in the videos.
Not if there are no (desirable/worthwhile) companies that take people on without a non-compete.

And what if you work for such a company but want to strike out on your own? The non-compete clause doesn't differentiate between an existing competitor and one you found yourself.
iOS 8 includes code for running apps side-by-side
I am reminded of a quote:

"Indeed, a major source of objection to a free economy is precisely that it ... gives people what they want instead of what a particular group thinks they ought to want. Underlying most arguments against the free market is a lack of belief in freedom itself."

Sure, Apple can do with its platform what it wishes, but the arguments I see being put forth here are troubling. "The ignorant masses are making the 'wrong' choices for themselves, and we in our benevolent wisdom should substitute our preferences for theirs." Where does that sort of thinking end?
Let's get on a more basic level, even.

Which of the two apps is more pornographic? The cutesy anthropomorphized vagina giving anatomical lessons, or the game that rewards you for staring at cleavage?
We don't have to ensure that men have parity before granting women the same privileges. I'd suggest that educational resources are much more needed and demanded for women than men in this market.

Also, as discussed in the article, Rack Stare seems to me far more objectionable (and I doubt it's alone in the App Store). If Apple's going to endorse sexual harassment of women, it might as well cut them some slack in learning about their own bodies.
I didn't get that at all from the article; how did you arrive at the conclusion that discontent could only be valid if there were apps for both sexes on the market? It seemed to me like there was a whole lot of article giving ample ground to stand on.
The (dense) vector and matrix functions have lived in Lapack and BLAS for 40 years, longer than there has been a libc. Every serious language has a standard interface for them, and the issues discussed in the article haven't caused problems for decades.
I came very close to missing the fact that there was a page 2 here, but to anyone that wants to read the whole thing: there's a page 2.

I strongly agree with much of what the author is saying here, but she may be reading too much into the fate of this particular pair of apps ("never attribute to malice...", etc.). I mean this as a nit and not the dreaded "middlebrow dismissal". :) The saving grace of the piece is that her thesis is more about attitudes towards sexuality in general; this particular incident only provides a convenient example.
I took a couple of physical anthro courses in university, and I never did get a satisfactory explanation for why genus homo evolved a parabolic dental arcade. After reading this, one has to wonder how a parabolic vs. U-shaped dental arcade functions when it comes to spreading force from a fist-blow, either head-on or oblique.

Modern humans have proportionally less upper body strength than australopithecines, but what about neandertal's? If there was a linear relationship between reducing jaw robustness and upper body strength over the last few million years, neadertals have got to be an outlier! If a parabolic dental arcade offers better protection against blows, perhaps fisticuffs remained an evolutionary pressure but nature just found a more efficient way to address it than making thicker bones.
I guess this answers why they're not doing archives anymore. 1,000 TB of videos with fewer than 10 views!
Not bad! Did you use rst2pdf or go through TeX?

I'm trying to decide where to upload my ePub to - the main Github repo, or the exploreflask.com repo. Thoughts?
I first learned about chimerism in the early 2000s, but it was a huge shock to me (it has some very deep implications beyond the scope of this article), and I was a biologist at the time.

Long ago I was pretty skeptical of the absurdly high confidence levels in forensic DNA testing because they made a number of very basic assumptions, which chimerism (among other things) show to be wrong, at a rate within the population which is higher than the reported confidence rate.
The author is claiming that girls and women aren't getting access to adequate information about their bodies. If that is true then the fact(?) that there isn't an app about male masturbation is irrelevant.
How many dates are you parsing at a time that optimizing this would make a noticeable difference to users?
This seems... mostly stupid.
Yeah. Do we know what Justin.tv's hosting costs for all that data was, or what infrastructure they used to store and serve it? That's a lot of data to take care of for a service with no direct monetization.
I was worried about commute times from three different points when looking for a house, so I wrote a quick and dirty little ruby script to hit the Google Driving Directions API. It tiles across the area you specify and spits out a kml file that can be loaded into google earth and lets you see which areas fit your parameters (https://github.com/chrisamiller/commute-times).

There's lots of room for improvement in the code, but it's in the same vein as what this guy did and helped us quite a bit.
Change your color scheme on the content, that is hard text to read! Greenish background with orange text is bad. Awesome product though. :)
The "subclass"-type inheritance is due to the underlying union filesystem (AUFS). Each command in the Dockerfile is applied as a layer and then cached, and each resulting image can be referenced as a starting point from another Dockerfile.

So you can branch out from a common base image, but you can't somehow co-mingle multiple parent images into one child. If you think about it like the filesystem giving you a snapshot at each line of the Dockerfile, you can see how inheriting from a single snapshot is trivial, but somehow inheriting from multiple snapshots into one would require much more awareness in order to merge them.

The practical effect is that either you build a more one-size-fits-all "base" image which you reference for all your services, or you have multiple base images with different more tailored sets of dependencies built up, or you have a very thin base image (e.g. not much more than ubuntu-latest) and just add what you need inside each individual Dockerfile.

I ran into the same issue at first when laying out the Dockerfile hierarchy for all my services/roles, but I think in this case it actually falls under "less magic is better" / KISS. Dockerfiles are so easy to read and write once you get going, you won't mind the simplistic approach.
Please read the entirety of the article, including page two (which is unfortunately easy to miss). There she writes:

> I’ll acknowledge that, although disgusting and possibly dangerous, Rack Stare caters to a certain market. The real problem is there aren’t many alternatives to this construction of sexuality
It is really out of date but the high scalability article has some information http://highscalability.com/blog/2010/3/16/justintvs-live-vid...
I agree on the font size. A bit bigger would help a lot.
Indeed, there is a line; the existence of a right to free choice of labor ain't it though.
> nix-pkg -i github.com/my/project

What you describe would be fairly easy to script. I'm playing around with similar ideas. It's not exposed by default, but the included script `nix-prefetch-git` dumps a git repo into the nix store, and when you run it from your shell, you have access to ssh keys and ssl certs (that are unavailable within a normal nix build).

The next step is harder like you say, you'd either need to include nix expressions for all dependencies on down through libc and gcc, or just assume/hope that "whatever happens to be in the local nixpkgs" is appropriate, but then you kinda lose out on a lot of the point of nix. It'd be nice if there were some way to reference a version of nixpkgs from which the expressions for "ruby20" and its dependencies would be drawn (but then you'd end up with hundreds of slightly different versions of nixpkgs tarballs from every github project with no easy way to update).
This is like playing the parlour game "Mafia". When the "mafia"is discovered, it's really not a surprise. It's just "oh, hey, yeah, that's the end of that round, who is next?"
Sam Altman Talks to William Channer on DRT.fm
A very fair set of warnings. Thanks. I will keep thinking about it, and probably install it on my old laptop before doing anything serious with it on my desktop.
I think part of the reason that most apps don't use these techniques is that there are not enough examples.

The examples that are available on SO, the apple docs, and IB generated/influenced code work great for the simple case but fall down a bit when your app grows. there are much better and simpler ways to handle some of the common patterns in large apps, for example the great thin view controllers article.

Objc.io is a fantastic resource.
I call this "expert band-aid applying skills". I think UITableViewController is one of the worst designed parts of UIKit and it's always a way to gauge how good a developer's OO skills are if they can point out the problems with it or if they're just okay with it.

If you put the delegate and datasource in a separate file at least makes your controller look a lot cleaner but still there's still so much stuff going on in them that doesn't separate well. If you feel the need to add #pragma, categories and that kind of things to make your code more manageable the underlying code violates the single responsibility principle.

I tend to not use UITableView unless I need either the performance or I am using a lot of built in stuff and there's no fancy stuff going on. Having to know up front what the height will be of a yet to be rendered cell really leads to a lot of ugly code quickly. I will not use it if I simply want to repeat some items vertically.
Feedback and videos from #TdcSf14 : Tizen Developer Conference 2014
That's the thing that is worrisome - ever assuming our knowledge is 100% solid. When we're in a reflective mood, we say we'd never do that. But it happens all the time. I remember in sixth grade learning that stellar red shift absolutley proved the universe was not expanding, thus provin the big bang. Well, despite KNOWING, turns out it was wrong - the universe was expanding after all. In this case it didn't change the underlying meaning, but was wrong. That left me questioning science more than I should. I can say I hate hearing "now we know..."
Why coding as single founder ain't so bad
I've heard lots of internet/SaaS/software product founders and bootstrappers talking about important it is to stop coding and outsource all of the tech and design to a freelancer.

I think if you have capital to hire a good designers and developers who know what they're doing, it's ok. If not, I think it can be a huge downfall. The main reason being, hiring really cheap programmers and designers yields really poor quality. Not only the stuff people see, like design, but also the quality of the code. I've hired freelancers who have done really stupid things, made really basic mistakes. The only good designer/developer I hired was always too busy to actually get the thing complete and sometimes took weeks for the simplest stuff. I didn't have the cash to pay a programmer $30/hr or even $10/hr.

This is the problem when you're tied for cash and you're going the bootstrap route. If you don't have enough up front cash, you have to do it yourself. Writing code and designing for me isn't so hard since I've been doing it for 10 years. The solution is learning how to maneuver it all so you have enough time.

What are your thoughts? Is industry standard design possible on a couple hundred dollar budget or do you have to learn it yourself? My opinion is that you can't afford poor quality when you're just starting.
I think you were downvoted because your comment, while humorous, doesn't really add to the conversation. Humor is appreciated more on HN when it is coupled with insight.
Some time ago at school the teacher asked to make a crawler so, as always I do it in node.js and mongodb.
The site to crawl has around 80K pages and 300 records on each page.
My script crawled and saved all that data (80K * 300) in less than 1 hour with around 100 concurrent requests.
The other students that wrote in ruby, python and php took days to do the same thing. Also they had to do by parts because if they requested all by once their pc would crash because of memory.

Also I didn’t need any test because since the first time I ran node.js it was instant fast, not like php, ruby or python.
nginx + FastCGI would probably put PHP on a more level playing field.

The test isn't completely invalid, but there is a lot more going on than what is described. It's a bit misleading to say that the server blocks waiting for file_get_contents. Actually, only the thread running the PHP script blocks. Other threads/processes can run. This experiment isn't quite a test of blocking versus non-blocking I/O. It's more a comparison of a heavy apache + PHP stack versus a lightweight, single-function node.js http server, which also probably benefits from non-blocking I/O. But non-blocking I/O is only one of many things that make the node script faster.
Square, Stripe and maybe even Coinbase to an extent. You could even throw in Amazon payments and Google wallet as well. They are in a tough spot, and their brand is always taking damage from how they run things.

I think they will die from not one big dog taking over, but a bunch of smaller companies each taking bites out of their market share.
But there's a bright/flip side to this, in that particularly big brands who approach the problem correctly could create some really good community. I'm thinking of the "maker" space in particular, where tool vendors could sponsor forums, events, etc that would be actually useful to their customers. (Mid-size b2b software vendors actually do a pretty good job here, with their webinars and such.)

Basically, it's the generalization of the sporting event sponsor: you sponsor that skate-boarding competition to inspire more kids to do skate boarding.

The problem of course is that it's hard to imagine the communities that would form around "canned tuna" or "sham wows". But then, I've never really understood those kinds of products, or why they'd even bother advertising. Is there really a difference between Crest and Colgate? Why would either of them bother advertising anywhere, let alone on the web?
Where do you see that statistic?
either way has issues, yes
if you manage more than a few projects, you already run into libs that will get updates and break things, at least weekly ;)
It's only problematic when you're doing it before the extension is public.

Likewise, property on Second Avenue on the Upper East Side of Manhattan has been cheap lately, because blasting out subway stations is unpleasant. But a new subway coming to an area that was recently relatively far from one means property values are shooting up.
Does it cover all of ISO8601? I'm sure it covers the common cases so is a valuable library anyway but I seem to remember that ISO8601 is quite complicated I.
PHP is a lot easier to use. Which is pretty much why it's already king.
The rest of the tweets in the thread:

> What about grabbing the 9 views, 8 views, etc? We have more time!

-@erazmus

> The problem is that at some point, we end up with a LOT of disk space used for VERY obscure videos.

> Normally, archive team does not care, but in this case, the disk space will increase to over 1.1pb. PETABYTE

> That's space that can be used to save a LOT of other work out there that needs love. Tough decision.

- @textfiles
I'm not saying that the users know that free options have lower cost-benefit tradeoffs, but in reality, experiments show that they do, specifically the on I cited.

But you raise an interesting point. It could well be that the "mental cost of even having to do a cost/benefit analysis" is too high for many people to consider paid options. That reenforces the proposal that Apple should wean users off of low (even negative) utility free options and train them to make such evaluations efficiently, the way many of us who are used to paying for software can. Again, all of this predicated on the thesis that benefit - cost - mental cost (which improves as we learn how to evaluate software) of many paid apps is higher than the average benefit of free apps.

As for my notion that people's actual behavior doesn't conform to a model of rationality, perhaps we should agree to disagree. There is plenty of research to suggest that people are bad at making calculations and require intervention.
>>I'm suggesting that the factors contributing to a languages widespread adoption are varied and complex.

Yup, thats true, and being performance oriented isn't the only selling-point for node.js. The fact that all node apps are single-threaded (and thus conserve cpu capacity), combined with the functional-programming approach of javascript (which makes things like async I/O easier, don't hurt either.
The post says: "For large object structures with thousands of date time objects this can easily add up." At 0.1ms per parse, that's 100ms per thousand dates, within the range of noticeable. (Their profiler screenshot has it taking 589ms.)
>I don't think it's going to be a cold war like the last one. With the amount of globalization and how much U.S and China rely on each other economically (China is becoming the biggest market for many American companies, and America is still the biggest importer of Chinese goods), it doesn't benefit anyone to have a real hostile relationship.

There were saying exactly the same thing for European powers just before World War I started.

The same things almost to the letter, actually: "The economic interdependence between industrial countries meant that war would be economically harmful to all the countries involved."

From this boom for one: http://en.wikipedia.org/wiki/The_Great_Illusion , but there were many other sources with similar thinking.

The thing is, relying on each other means almost nothing. It's a temporary situation, and it can change in a heartbeat when the two countries get to compete for the same resources and/or third markets. And also as the relationship between who is the supplier of "cheap labor" and who is the "market", with the affluent middle class, changes.
Woman on NPR claims hackers, "Are shy, obese and go 72 hours without showering."
Yup. And thats only because of precious CPU time saved by doing async I/O which the functional paradigm of JavaScript supports so well.
The beauty of an abstraction is that you get to reap its benefits without understanding precisely how it works.

...and get to be manipulated and screwed over by the people who do.

While I don't expect the general public to know the details of WiFi down to e.g. the level of the 802.11 spec, I think that some general ideas, like the difference between passive/active scanning, are both simple enough to be understood by analogy and critical to privacy that they should be known more prominently.
Not sure what that means. Why would it have to be a "savior"? And why it's a "liability"?
Jurassic Park: Trespasser CG Source Code Review
They said they archived 10TB (and that covered everything with at least 10 views), and that the total including all videos would be 1.1PB, ie 1100 TB. So there is over 1000TB of videos with less than 10 views.
>>Actually, only the thread running the PHP script blocks. Other threads/processes can run.

Yup. But imagine a situation that suddenly around 10000 requests have arrived at your server and sitting on the queue. Now that "one php thread" suddenly becomes a life-saver.
In the posted thread.
You tell me where you think the line should be drawn:

(a) You agree not to leave Apple* for Google, for 3 years.

(b) You agree not work for Google, ever.

(c) You agree not to develop software for anyone besides Apple for 3 years.

(d) You agree not to develop software for anyone besides Apple, ever.

(e) You agree not to do any kind of work for anyone besides Apple for 3 years.

(f) You agree not to do any kind of work for anyone besides Apple, forever.

Personally, I don't think any of those contracts should be enforceable by law, regardless of what people foolishly choose to sign.

* (the choice of Apple being entirely arbitrary)