skysight-inc/HackerNews huggingface dataset:
I'd be interested in seeing why instagram didn't implement the suggested user service as a batch process that populated some KV store. Online evaluation is great for guaranteeing up-to-date results, but the tradeoff is that you now have to bring up and maintain a fairly critical production service.

> The SU service fetches candidate accounts from various sources, such as your friends, accounts that you may be interested in, and popular accounts in your area. Then, a machine learning model blends them to produce a list of personalized account suggestions.

> This enabled us to reduce the number of instances of the Suggested Users service from 720 to 38.
So only people with meaningful things to say or build should get noticed and hired?
Standard Deviation Puzzle: Add a number to set {1,2,3} leaving the STD constant
To clarify I'm not advocating for rage-filled screeds as a viable method of communicating nuanced information, or even as a viable method of communication. As you said sharing conflicting viewpoints is valuable. I take issue with the suggestion that this is only valuable if the conflict is framed in appealing language or "toned down" to "acceptable" levels, whatever those are. Conflict is ok. Resolving it is how we get shit done.
That's exactly what hotfixes are for. A completed hotfix will merge directly into develop and master simultaneously (practically speaking). This allows you to keep your unrelated develop commits out of the master until you're ready to merge it all.
I'm one of the admins on SSG, thanks for posting!
The only potential use I see for Docker's potential is to distribute applications with data as combined appliances: so if you want a PostGIS server preloaded with maps, you can do `docker fetch some_postgis_server` and end up with something you can query. But then when you try to build such an appliance (containing a lot of data), and push it to Docker Hub, it ends up failing with a mysterious error code overnight, and you open a ticket, and nobody follows up on that ticket. Docker has to get better at that kind of thing before I can consider using it again.
Show HN: onHand - Accept appointments from your website
garbage content is also bad for you
> We're talking about rendering a more distant bigger screen, so the solid angle and the number of pixel used is constant. The point obviously isn't to give the appearance of a tv-sized image placed 100 meters away, it's to render the appearance of a kilometer-sized screen 100 meters away.

If you stretch a fixed number of pixels you reduce the detail.

If you shrink a fixed number of pixels and display that at the same or lower resolution, you reduce detail.

In either case detail is lost.
> Meaning objects get smaller, meaning that they take up less space on the resolution

Why? It's a virtual screen, why wouldn't you scale it up as well as moving it further? The sky is really far away from me, but it's pretty huge in my field of vision.

> Nobody is talking about viewing angles. I certainly never brought it up.

Which is why we are all saying you're wrong. It's entirely dependent on viewing angle and not distance. Distance and virtual screen size are how you can determine the viewing angle.
I'd agree that containers will be huge in the future. But it might not be with Docker, that's all.
Why do you jump me to a signup form as soon as I go to the URL? Let me get a good look at you first. Tell me your story. Buy me a drink. Give me some good pillow talk.

When I read the copy on your site, it feels like it’ll be cool and casual and mysterious, which is the right approach. This aggressive Typeform maneuver ruins that feel.

I would sign up for this if there was a way I could indicate that I don’t want to talk about work.
>About half of Bitcoin brokers, and most of the Bitcoin online wallet companies, have gone bust, most of them taking customer assets with them. Any questions?

Do you have a source for that?
It's far from obvious that the industry would be more diverse and less consolidated if regulations were relaxed. The overwhelming majority of that gigantic flow of money is not main-street retail activity; it's financial engineering serving the operational needs of giant corporations, none of whom are interested in e.g. working with a YC startup for their commercial paper needs.
So, let me give you a practical example. Three years ago I bought a condo for $55,000. Six months ago, I sold it for $70,000. Factoring in various transaction fees, and interest, I made about ten grand.

Why ever would I consider renting? We're still at a relatively low point in the market, and there's a pretty good chance the value of your property is going to go up, not down.
What I'm wondering is if this model would work for other things besides hair, where the retail outlet is constrained on the ability to hold inventory. Maybe mechanics shops?
Sure. But as I said, it's a descriptor used in reporting- not a target for those in the trenches
Would you mind sharing any of your experience building it with Swift?
My favorite:

>> Tech is an industry of moving fast and breaking things. Finance is an industry of moving fast, breaking things, being mired in years of litigation, paying 10-digit fines, and ruefully promising to move slower and break fewer things in the future.
I believe Google already did something similar with mugshots[0].

[0] http://www.cnet.com/news/google-works-to-demote-mug-shot-sit...
It will take time. For example carbon nanotubes are now finding their way into production, and have gone through a similar craziness phase some 10-15 years ago but are far from the "wonder material" the press has presented them to be. I believe graphene will have a similar evolution, maybe even a bit faster if you consider the amount of funding that has been poured into it. I'm sure it will find its way out of the lab sometime though, however again I think it will not be the "magic do-everything" material. I believe there is some blame to the press, since they tend to always over-exaggerate about scientific progress. I would even say it's damaging to science because it creates hard or even impossible expectations, that downgrade the crazy amount of research that has been put into them to the eyes of the public.
In my city, we have a cinema that has a 18m by 8m screen and uses 4K projectors with reald 3D. It’s still an amazing quality, and faaar cheaper than IMAX. (About 3 times cheaper). And they clean the room after every showing, so the floor, although carpet, is always clean, you get reserved seats, and the popcorn is fresh.

IMAX, especially as current IMAX Digital theaters have similar screen sizes and also only 2.8K (two 2K projectors on the same screen), just isn’t really worth it anymore.
I don't know why you're vociferously defending FPH against the charge of brigading.

A sub being mentioned (but not linked) in FPH would result in massive traffic spikes. Smaller subs with a couple of hundred subscribers and a couple of thousand visits per week would suddenly get thousands of visits per hour. The increased traffic is fine, but some of those people would comment.

You've mentioned the huge numbers of subs to FPH. Even if it's only a small proportion of those people causing problems it's still a lot of people.

And you use, yet again, trivial examples that no-one (certainly not Reddit) cares about. No-one cares if you call some minister fat and stupid. What they do care about is getting people fired from their jobs; having child protection social workers called; huge amounts of brigading; hate mail to real life addresses.
Telegraf – InfluxDB Server Agent
Show HN: Online marketplace for handmade cremation urns
tl;dr Broccoli isn't bad for you; it's good. It can be made to seem bad by telling half a story, just like any other thing. Be moderate and try to eat more fruits and veggies.
Sorry if I misread that particular one, but you post a lot of these and we need them to stop. You're welcome to keep contributing as long as the posts are substantive and civil.
Do you want to make a snowman? http://imgur.com/YDUgG3U
How many things are brand new and innovative? Most aren't, most are iterations, or just a more successful effort at something that has been done before.

If you want to build it, build it anyway. Build it for passion, for the experience, for interest, or for any other reason. Or don't, that is ok too.
A tool that does not naively sort the commits by date but groups linear parts of history together should allow for better overview.
I want to like Docker. I just don't have the time to learn the tooling and keep up with all the changes. Maybe in a year or two when things stabilize.
Notifications should be limited to the messages visible within your bounding box. If I've zoomed in on a city, I don't want notifications from somewhere half-way around the world.
The difference between this and a fractal in which you shrink as you descend into it would actually not be all that different!
Builder of Berkeley apartments has paid millions in balcony suits
I'd love to hear more about your company and how they scaled support, if you have time, ping me john@heapanalytics.com. If there's something I can do early to make scaling support easier later, I want to know :)
That sounds awfully like famous last words...

In addition, I would say the mentality of scalability when constructing applications is part and parcel of the design ideology of ruby, but too often far removed from its practice.

I see no reason to prefer Rails API. It is a reverse-frankenstein situation whereby they had the monster, and started removing limbs...
"They’ve become boring clichés. Nobody really wants to read “considered harmful” essays any more, because we’ve seen them a thousand times before and didn’t really learn anything from them, since we were too busy being annoyed to really listen to the arguments presented."

It's a boring and pompous cliché. In 1968, it was original. Now, write your own title.
Kevin,

I saw in your other thread that you would be giving feedback to Show HNs today and I was really hoping you would come across ours and provide some insights. Thanks for taking the time to dig through the site and reply with your thoughts!

We can definitely improve the homepage to answer those basic questions more directly. I think one thing we need to do is identify the target audience(s) and try to address each individually. For example, like you said, the sender/receiver obviously cares most about how it works and what they have to do to try it out. The IT guy wants to know how it works (is it really secure) and how to install it.

Do you have any advice for a good approach when there are 2 or more target audiences you want to have call to actions for on the home page? Perhaps we need to pick one and then have a clear link for the other target (secondary?) audience and address their concerns on another page entirely.
I'm curious why you're putting so much rhetorical energy into not giving a simple answer. I'll be blunt: I do not believe that you believe that there was any possibility Swartz could have received a 30 year sentence, or even a 10 year sentence.

In fact: since you seem to be a kind of nerd that is very similar to the kind I am, I'll bet you've actually read the relevant sentencing guidelines --- not just the table, but the big document that lists all the criteria that add points to CFAA and wire fraud charges. If I had to guess about what's in your mind, I'd guess you agree with me: the prosecution's threatened 7 year sentence was also mostly bluster.
‘Mini IPOs’ now open to the public
What would be really useful is if you could compare API behaviour between different graphics cards and driver versions.
I take it you only read the opening couple of paragraphs before writing that. Go back and try to read the whole thing.
It is along the same lines as boost's futures implementation. We have a different mechanism for expressing thread management, born out of trial and error and Facebook engineer feedback. At the time we set out to write this boost futures were slow and buggy (1.53), and C++ standard monadic futures proposals were in very early stages (it now appears that there will be monadic futures in C++17). I do not know if boost futures are now more robust and/or more performant in 1.58.
Show HN: Quaint Server – Serve webpages from the browser
Rats, the terminology is backwards from the E/JavaScript promise/future distinction: https://en.wikipedia.org/wiki/Futures_and_promises#Read-only...

There's been a push to standardize "Promise" to be the read-only side and "Future" to mean the resolver/promise pair, but Folly Futures use the opposite convention.

Agreeing on terminology is hard. :)

Edit: I think it's fine that Folly adopted the C++11 convention. I'm just whining in the open that that promise vs. future may never be agreed upon.
Excellent library and writeup !!

This is very similar to HPX, the general purpose C++ runtime system for parallel and distributed applications by the Stellar Group - https://github.com/STEllAR-GROUP/hpx.

I recently saw the excellent video presentation by Hartmut Kaiser on this https://www.youtube.com/watch?v=5xyztU__yys and a lot of concepts in folly futures are quite similar. However the most striking thing in HPX was that all the building blocks are serializable, and the presenter mentioned that it is so because you could serialize and move a thread to a different machine and run it there.
> Nothing that Docker does is completely new, and people were doing all these things before Docker.

You're contradicting yourself, because in the same article you wrote:

Into that world drops Docker: a new way of doing almost everything. It throws away old rules about operating systems, and deployment, and ops, and packaging, and firewalls, and PaaSes, and everything else.

Then all the hype about the "future".
I'm looking forward to using Docker (or another container format) for reproducible computational work. Now, it's still somewhat difficult to keep versions of programs in sync on clusters (even using environment modules). It will be really nice when we can store the application environment as a container and be able to pull that configuration off the shelf to repeat an experiment/analysis.

Unfortunately, that use-case usually happens on multi-tenant HPC clusters, where we can't use Docker yet until the security issues are figured out (or we can get a solid and standard micro VM for running containers). Job scheduling is also a non-trivial issue.
Your post is invalid at some point.
Of course Docker is great, of course new technologies are great.
BUT the first point isn't so much of a joke.
Docker is not the future, at least not for everyone.
Currently Docker will not change the way how apps will be built, Docker will change nothing, ... at the beginning.

To start out new development, people should and never forget this, don't care about microservices and docker and anything else. They should just build a fucking big Monolith. After they did that, and they are getting more people for development or more people at their page / service / whatsever they can still start to split everything.

Don't build a fucking Unicorn just to be accurate. Start out boring. Do this every time and don't listen to anybody that tells you how good microservices and docker is.
Deploy your app manually (okai this step could be skipped), then use a tool LIKE ansible or puppet, then if you need more, look at the things that bigger companies use.

But never ever over architect your project / application / service.
All of those advantages are true, except for performance. We actually don't know which approach will be faster to compile, nor which approach will emit faster code. There are reasons to guess either way.

The new backend being begun here is something of an experiment, as LLVM shared backend infrastructure was just not designed for this kind of thing (emitting a high-level AST IR without physical registers, etc.). There are still significant open questions regarding which parts to use there. It will be interesting to see how this develops.

Regardless, a new backend makes sense for the other advantages you mentioned, especially that wasm will grow and add features, and a new wasm backend is the best place for that.
WebAssembly itself doesn't have anything to do with asm.js near as I can tell. It's more the ecosystem surrounding WebAssembly.

I looked through the specs a little bit. What it is, is a binary encoding of the AST with some optimizations thrown in to decrease size (symbol tables instead of using the full tokens).

I'm unclear on why asm.js is even mentioned but I suspect it is a temporary stop gap since those languages using LLVM currently target asm.js. Now, they can just target the AST but it will take some time for the tools to change. In the meanwhile they will look like: C -> AST -> asm.js -> AST -> binary. In the future, it can just look like C -> AST -> AST -> binary.

Why is it significant?

1) Language designers can just target the AST, then pass that to WebAssembly to compile to a binary. There's no need to compile to JavaScript. It saves them a step.

2) Size. They are claiming 20-30% smaller than minimized gzip versions of Javascript. There are optimizations that can be done (at the AST level) that exceed what is possible with generic compression like gzip.

3) Load time. Since it can be decoded straight to the AST, it saves the Javascript parsing step. This results in faster page loads.

4) Non-Javascript tooling support will improve. Javascript will still be the canonical language but other languages will increasingly get first class tooling support.
it might also lead to people skipping those sites altogether, which is what triggered the whole ad-supported-web madness in the first place.
One important question: does it make a single snapshot at a certain moment during the day, or does it take multiple snapshots during a day, and combine the most highly rated articles into an ordered list?
How much do data breaches cost big companies? Shockingly little
Very few people go the distance with their projects. If you think you'll be someone that does, then go for it. We've had the biggest companies to startups enter our space, and many already in it before we started. The difference, I think, is that few have the courage or focus to push hard on it day after day for years at a time.
From the FAQ:

> PostgreSQL is pronounced Post-Gres-Q-L.

https://wiki.postgresql.org/wiki/FAQ#What_is_PostgreSQL.3F_H...
I can't tell if you are referring to parent's message or the article.
No reimbursement, and though I hadn't been liable for the dues, I didn't feel it would be worth the effort to try and recover them.
Both this and the previous tongue-in-cheek rant are correct. It depends on who you are.

The fact is that not everyone is going to need to scale to Google-like sizes, and not every app is going to need to scale in the same way.

For many developers trying to build products, getting bogged down in all this emerging Docker-centric complexity is a case of premature optimization. Build your thing, polish it, get users, get customers, etc., and if you manage to get so many that scaling becomes a problem then you now have a "good problem to have."

... and the problem with the Docker ecosystem is not that it is new. I love new stuff. The problem is that it's a lot like the web framework ecosystem, which is an example of the CADT development model:

http://www.jwz.org/doc/cadt.html

To a certain extent that's an artifact of all this Docker stuff being new and very much in its experimentation phase. I expect that the web will settle down a little someday, and this stuff will too, but for now it's a crazy wild west of people implementing Yet Another Everything. There's also a bit of a funding wave going through this area, which is causing a lot of me-too Docker startups to pop up and do the same things over and over.
I don't (intentionally, at least) visit any site that has an ad for users who use ad blockers to disable their ad blocker.

I do this because, to me, it is implied they would rather not have me visiting if I do not white list them. Which is reasonable and understandable if ads are their main business model.

If it is merely a request but they explicitly state that continued use of the site with your ad blocker active is OK, I'll continue use of the site.

E:

I went off on a tangent. Removed the unnecessary bits.
Not that I know of, plus it would be extremely difficult to detect as each chargeback would appear to be coming from a completely different customer (different name, different address, different card number). I'd imagine this kind of attack would be especially stressful to SaaS businesses or subscription businesses in general.
Comments moved to https://news.ycombinator.com/item?id=9746405, which is about the same project.

This post looks good, but there shouldn't be two of these on the front page. I'll add a comment to the other thread mentioning it.
Senders hold promises, and receivers hold futures. A promise represents a "promise" to deliver a value at some point to the holder of the future.
Show HN: SheetDB – Connect Remote SQL Database with Google Sheet
/r/conspiracy was harassing a daycare in Utah. I don't like to use that term lightly but yes, actual harassing. As in, the subreddit was obsessed with it because it had some records online that made them think it was secretly running some kind of malicious operation. people were going there and surrepititiously scouting the place and sending back photos and talking to neighbors. Admins were deleting posts, which is why it turned into a "free speech" issue for them and a bunch went to voat.
No. Employers need to realize they don't need to fill every damn position with a "rockstar." But until then, we'll keep playing the game.
It's the same stuff, but it does it differently. So for example, instead of using AMIs to prebake images, it uses a weird AUFS layer. And it deploys using Dockerhub or by pushing images directly to hosts. And instead of using Mesos it has Swarm. And Kubernetes: that really is quite different to what we're doing, but not that different, conceptually, from what Heroku is.
I believe it's the next line of defense after "there is not climate change", "it's not that much", "it's not caused by humans".
But how does one elegantly stop a chain of futures from executing when one is no longer interested in the final outcome of this chain of futures?
There are many stories of creation. The creation myths of Ancient Egypt, Norse, Greece, India, Zuni, Babylon, etc. cover far more than "a mere few pages". As "creationism" is a term most often associated with a specific interpretation of Christian faith, it sounds like you are thinking only of Biblical creation, and not the general category of creation myths. For purposes of discussion, I'll leave the Bible out entirely.

The statement was that most myths contain a kernel of truth. If that is meaningful, then shouldn't many of the creation myths also contain a kernel of truth? If so, what is the kernel in all of those creation myths?

One kernel is "people want a story to explain how they came to be." I'm actually fine with that. But then it's not really a story of oral history, but of human desires.

Another is to keep looking through the myth until something works. This seems rather haphazard in that all stories have at least something which is true. For example, Loki is the son of Fárbauti. Loki is of course either a god or jötunn, and neither of those exist, but some people are sons of other people. Is it really useful to say that this is a kernel of truth?
Yes, the two terms are unfortunately both synonymous (comparing different implementations of the pattern in different languages), and usually have specific meanings in the context of any given implementation. Often, as here, Promise is the write handle and Future is the read handle.