skysight-inc/HackerNews huggingface dataset:
> Wait until you see a badly managed git server that serves a central repository. You'll quickly change your mind if pushes start failing randomly.

But I can't code a better sysadmin into either git or Perforce. A badly managed Perforce server will have the same issues. (Unless, of course, you have an argument that Perforce under bad management somehow performs better than git under similar conditions.)

With git, however, I can still commit, and I can still push and pull changes from other people using side channels such as email. I can, for the most part, keep working. Is it more difficult? Of course. But in the particular scenario, git outperforms Perforce, in my opinion. (But this is not the primary reason I use git; at work, we use GitHub and git in very much a centralized manner. GitHub has its outages, and they're annoying. But not work-ending.)
I have to agree with the whitepaper, "Tendermint is awesome. The future is now." It seems like a marked improvement over proof-of-work style blockchains.
The point of accident investigation is to be able to learn and improve from what went wrong, to reduce the risk of the same type of accident happening again.

One could certainly make the point that occasional mysteries cost less than sealing up all the holes, but it's silly to say that knowing what happened to MH370 would be pointless because everybody is dead anyway.
This is a really important question. I am from India and good bandwidth is a luxury here.
> Other OSes have different file monitoring capabilities though. Anyone up on file monitoring on Windows / OS X? Is directory-specific monitoring possible?

yes
Scientists have figured out what makes Indian food so delicious
> Why, are external developers able to consume restful APIs without the need for any documentation on the system they're talking to?

In a fully RESTful, an external developer would be able to consume it with only documentation of the resource types used, and identification of a single base URI for a known resource from which the rest of the API's locations were discoverable. (That doesn't mean that an API owner wouldn't still want to document more, but it wouldn't be strictly necessary.)
Killer app? I don't know about killer, but here are some super useful things I can imagine smartwatches doing:

1. Use as a navigation device (walking, driving, biking, etc), so you don't have to constantly pull your phone our and check which way to go.

2. Control music / tv / computer from across the room without needing a remote (always on your hand, always paired)

3. Homekit control (lighting, locks, appliances, etc) e.g. set your oven to preheat, go in the backyard and do whatever, watch notifies you when over is ready

4. Healthkit (many people wear health trackers already, this will just bring more features to a device they already wear). Also biometrics.

5. Someone texts / calls / emails you as you sit in a meeting / walking with your hands full / etc you can glance at your wrist and see how important the notification is before you excuse yourself to take the call or whatever.

Basically, most of the potential with this device is doing things which phones can already do but in a less intrusive manner. These features alone interest me in smartwatches; I can't imagine what other people will come up with.
I found it a little funny, but not funny enough to justify being that level of asshole.
>The people yelling at you are trying desperately to pretend like it was easy so they don’t feel like an idiot for how long it took them to figure things out. This in turn makes you feel like an idiot for taking so long to grasp the “easy” concept, so you happily pay it forward, and we come to one of the two great Emperor Has No Clothes moments in computing.

This part doesn't make any sense. If anything, people would want to convince you it was hard to not look stupid for taking long.

That being said the phenomenon clearly exists, but the reason is probably more along the lines of calling everything easy to try look smart in general.
Can I store the state of my machine, or do I only get one instance/snapshot at a get go? What if the machine gets corrupted? What kind of backups?
I'm not a fan of solutions like git-annex, every time I've seen people try to do this type of stuff, two years down the line they end up having built a buggy knockoff of maven/gradle. Why not do things cleanly from the start? The entry barrier is really not that high, and the benefits are huge.

Then again maybe I'm a bit psycho-rigid on build management :)
So right on about doing the same thing by accident.

Early in my life, I programmed synths in a studio - and I practiced a variation on this. I would listen to what sound they wanted, then I would play them something that was likely pretty close. They they would complain about it not being quite right, so I would play 3 or 4 different sounds that I knew were completely wrong, then return to the first sound. To which they would invariably say "yeah that one - that's perfect!"
This is one of the sections of Ristic's excellent book Bulletproof SSL and TLS.

I owe him a review of it but the short version is it's great if you need to learn about SSL and TLS and great because it's entirely practical. Highly recommended.
The Drug Lord with a Social Mission
> I'm by no means an expert in the field, but if I understand the role of Vulkan correctly, you -- as an application developer -- won't be writing your programs against the Vulkan API.

If I understood correctly, for graphics at least Vulkan gives great flexibility to application developers, giving them to decide how to manage multithreading. If developers care about high efficiency (and games usually do need it), they'll use it.

Of course if developers are using third party engines which already handle it for them, they might not need to deal with Vulkan directly. But engine developers would have to in such case.
I don't think so. The very structure of contract work encourages slapdash products (after all, if you've checked off the boxes, you've "delivered" and can be paid, regardless of whether you meet the customer's actual needs). I bet that if the US government hired a team of programmers who answered only to their government bosses quality would go up (I understand the UK did this and that was the result they found).
> wait for the person who does it better.

Which means less work for wambotron. Assuming that wambotron was paid hourly and not on commission basis, wambotron does less work for more pay, which is effectively a raise.
This is also relevant and fascinating: "A Star in a Bottle – The International Thermonuclear Experimental Reactor" (http://www.newyorker.com/magazine/2014/03/03/a-star-in-a-bot...). The HN discussion is good: https://news.ycombinator.com/item?id=8307584.
I'm speaking from the experience of a developer who has built numerous public APIs and client libraries over the years. Yes, you still need documentation for a REST API (I'm not a HATEOAS utopian), but you can easily attach your documentation to concepts with which many (probably most) developers are already familiar.

The article is basically saying "You know how lots of cars have steering wheels and pedals? Well, I think it's annoying to build cars that way, so I'm going to use a system of levers and buttons." There's a ton of utility in anchoring new systems to familiar concepts, and unless you have a good reason not to you should strive to do so.
So, a thin client connecting to a virtual machine under some other company's control? No, thanks.

The fact is, computers are plenty fast now, and can handle 90% of peoples' usage patterns (browsing reddit, watching cat videos) with ease. The last thing I want is to have a remote desktop that lags out whenever there's a network hiccup.
bare minimum: You should add a link at the bottom where you say "Get Yours First -- See our !!FAQs!! for even more details."
It is, but unless they make a law against it these things change very slowly ("Everyone has always send in CVs with their picture, why should we change that/why are you doing it differently than normal"). International companies or software startups probably move quicker in these things than banks or production companies.
But you don't really need them. The red book tells you pretty much all there is to know (I say that based on memory from years ago, the last time I used SVN. I liked SVN. It was easy to use, easy to understand, and did everything we needed for our project (a half a dozen developers all working in one office). It was such a breath of fresh air coming from our previous VCS (Visual SourceSafe).
A sweet feature prioritization method
The author CLEARLY has no idea what REST is or even why REST is used. How the hell did this garbage make it to the front page again?
Fuck empiricist reduction. So sick of this bullshit epistemology trying to break us down to equations.
An Early Look at WebGL 2
I used to work at a place where our dev team was split in 2 and separated by 500 miles. We had centralized source control and there were days when our company network was slow. On those days I had to wait 30 minutes to check a file out and 30 minutes to check a file in. Try to meet deadlines with a workflow like that.

Never again.
I had the misfortune to have used Arch around 2005-2007. That was an excruciating experience. Updates that would take over an hour.
Not really related to the acquisition, but what's the status on running GitLab on the arm architecture such as the Raspberry Pi? I'd love to run that.
An aspiring indie with zero track record should choose based on the strengths of the tools themselves. Making $3000 in a quarter is a pipe dream, let alone 100k over any time scale.
"Almost everywhere" doesn't include IE and Firefox?
This looks pretty awesome.

What if I muck up my space, can I go back to a fresh install? Which flavor of linux?

Where are my files stored? Say I want to take those files on the plane with me and work from my laptop, will I need something like Dropbox/OneDrive/SpiderOak?

Liked the video as well.
So, how is this different than using RDP or VNC to connect to my PC?
>it reads to me like them saying "we created this program to get women into things because they can't hack it any way else".

While you might feel that way about it when you see it, it's neither the reason for nor the intent of the groups running the programs. There are a lot of real and ugly issues that exist that keep women (and minorities) out of the tech industry and push them out that have nothing to do with the qualifications or abilities of anyone.

Trying to increase opportunity to help balance the actual institutional sexism, racism, unconscious biases, hostile environments, and other factors that keep valid candidates out of tech isn't sexist or racist, they are an effort to counter the effects of sexism and racism and bring more people in who are just as qualified, capable, and talented but who despite those factors have added barriers to entry and added pressures to push them out. Those core problems can't really be addressed until there's enough diversity.
Does anyone else think the bold colors distract away from the content in Material Design?
Asm.js Speedups Everywhere
Multiplexing RPCs onto a single WebSocket has some serious downsides. For one you now have an entirely custom protocol that standard proxies will not understand and cannot route. GRPC is very careful to be valid HTTP/2 for this reason.

One of the major reasons for the existence of WebSocket is to support duplex streaming. HTTP/2 explicitly states

"A server can
send a complete response prior to the client sending an entire
request if the response does not depend on any portion of the request
that has not been sent and received"

With better HTTP APIs (particularly in the browser) you would get full-duplex and the need for WebSocket would diminsh.
It's difficult to top AWS just based on an apples-to-apples comparison of buying servers versus turning up EC2 instances. EC2 is pretty price aggressive if you know what your needs are, identify an instance type that fits well, and reserve it for 3 years. A lot of people don't actually achieve all three, but it's often possible.

Most comparisons overlook the crucial price differentiator between AWS and a datacenter build: bandwidth costs. AWS bills based on bytes transferred, every IP transit provider bills by 95th percentile or similar.

A 1 gig commit on a 10 gig circuit is $1-2/meg in a well served on-net building, so let's say $2000/mo. The switch is $5000 or so, something that can't do full table BGP but is layer 3 capable, and support is $1000/yr. The cross connect is $300/mo. Plus a little bit more for optics and fiber. Over three years the cost is $91,000 (plus power to run the switch), if you never go above the 1 gig commit. Seems like a lot of money right?

Compare this to transferring 500mbit/s constantly to the Internet over 3 years at AWS pricing. That amounts to 156 TB / month transferred. Per month that will cost $11,878.40. Over 3 years the cost is $427,622.40.

There are some other key differences between AWS and datacenters:
- it puts all of your spending into opex, eliminating capex (this matters for some businesses);
- it limits the ways you can solve problems, there's no VRRP support for example, which is very limiting for a lot of service types;
- there is no ability to peer or receive settlement free transit if you deploy in AWS

However, in terms of raw dollars, the method that AWS uses to bill bandwidth consumption is always the major cost differentiator.
>So right on about doing the same thing by accident.

There is nothing that can describe the mixture of confusion, shame, and artistic/technical self-doubt that you feel upon realising that the compressor you just spent half an hour lovingly tweaking, to seemingly great effect, is bypassed.
Revealing it this way leaves a bad taste in my mouth. At the very least, I'm glad that they revealed it during the main campaign rather than shortly after, but it's a pretty significant shift in the campaign. It's like an even bigger "fuck you" to the Kickstarter model, because clearly they knew they'd be doing this.

Plus, it resulted in a big shuffling around of orders, which means a bunch of people were able to "cut in line" and get the extra discounted Early Bird level.

Though all of that is only in regards to the Steel model, I'm actually extremely interested in the Smartstrap system, and I'll definitely be interested in tinkering around with it once I receive my only slightly discounted non-steel Pebble Time.
You have a technical problem. You want to solve it with XML, and now you have two problems.

You have a management problem. You want to solve it with micro services, and now you have N problems. N = number of micro services.
No problem, thanks for asking. With the 1GB RAM Pi coming out running GitLab is a lot easier. It would be nice to have a precompiled Omnibus package for it (like the ones for other platforms on https://about.gitlab.com/downloads/). We hope someone will contribute this.

For now you'll have to install from source https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...

More about the memory requirements can be found in https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...
In China the control over internet is simply control over people, there is absolutely no benefit for the people - if you keep speaking against the government without hiding your identity, you are in trouble. So, there is no debate over whether more control from the government is good or bad.

In the West there is at least still a debate between privacy (potential impact to free speech) and safety against terrorism.
Show HN: Couchback – A back end for static apps on CouchDB
Kinsa - New York City or San Francisco

Head of Software Engineering

Senior UX Designer

Senior Mobile Engineer, Android

Senior Mobile Engineer, iOS

Mobile Engineer, Android

Mobile Engineer, iOS

UI/UX Designer

Kinsa is a mission driven startup that's building the world’s first real-time map of human health with our ultra low cost smartphone-connected thermometer.

We're growing rapidly and are looking for the right people to work with. Check here for info on all open positions. https://www.kinsahealth.com/working-with-kinsa/
Firefox Media Source Extensions Update
> They were, of course, uniformly non-white, non-Asian girls.

> The poor students weren't poor students because they were female, or because they were non-white, but because they were unintelligent and/or uneducated.

And why is that? If you reject the absurd notion that there's some causative relationship between technical ability/intellect and gender/race, what's the explanation, other than the possibility that those people didn't have the same exposure to the subjects that you did? And that's not even including the confidence factor: Of course a white dude can do this stuff, they do it all the time. Your story seems to suggest we should actually be doing this long before university. I would agree with that.

This part will probably be unpopular, but I'll say it anyway: What makes you so special, that your life is the one that gets to be changed? If we were all on equal footing, who says you're even good enough for your university geek-kid program anyway? Or me, for that matter - I was part of a similar program in high school[1]. What if we could be fifty years ahead of where we are now, if only we had an environment that was actually competitive across the whole breadth of our society, rather than jokers like you and me running the ship?

[1] http://www.usfirst.org/
Another, very different pattern of bus arrival times evidently arises when buses slow down to prevent bunching: https://www.quantamagazine.org/20130205-in-mysterious-patter...
Pedantically, RFC 2616 is obsolete, and you should point to http://tools.ietf.org/html/rfc7231#section-4.1
Remainder converts to equity somehow then?
Somewhat off-topic, but it's kind of disappointing that the intro video doesn't play on my copy of Firefox nightly on Linux -- Kickstarter videos play fine, since it seems like they provide a webm video.

Error says:

Awww, snap!

This video can’t be played with your current setup.

I could open up Chrome or Opera to play the video, but that's too much friction for something I might not care too much about.

It _looks_ like Vimeo -- I wonder if they let you know how many people tried to view the video but couldn't.
Dropbox Is Probably Ready To Do So As They Want
In my eyes, using CamelCase is a kind of cargo cult, based on the fact that the programming language Smalltalk used it. C++ adopted the style and moved away from the predominant use of underscores in C. So, people who want to be seen as modern and object-oriented, are biased to use CamelCase to stress their competence in things OO.
Similar to what Steve Yegge said in his unintentionally published platforms rant:

- monitoring and QA are the same thing. You'd never think so until you try doing a big SOA. But when your service says "oh yes, I'm fine", it may well be the case that the only thing still functioning in the server is the little component that knows how to say "I'm fine, roger roger, over and out" in a cheery droid voice. In order to tell whether the service is actually responding, you have to make individual calls. The problem continues recursively until your monitoring is doing comprehensive semantics checking of your entire range of services and data, at which point it's indistinguishable from automated QA. So they're a continuum.

https://plus.google.com/+RipRowan/posts/eVeouesvaVX
Putting on my client/product manager hat for a moment, this is incredibly annoying. You are putting me in the position of either (a) fixing the obvious ducks and not looking closely at the real problems, or (b) having to micromanage you and scheduling another review to make further changes. Maybe you get your desired result (a), but my opinion of your work is going to be much lower since you are making obvious duck-sized mistakes.

If you are a developer who takes this approach, you may want to consider whether the short-term benefit of avoiding criticism is worth the long-term downside of having me think you are incompetent.
Counterexamples: UIUC, Cornell -- among others.
This would be great to have as a paperback, too...
But sugar/starches are present in LOTS of foods. The question is: what makes indian different?

Do you think it has even more sugar/starches than other foods? It doesn't seem like it to me but maybe I'm wrong.
The first startup visa to be issued at the Expatcenter Amsterdam
This is utter nonsense. A very few cuisines such as Gujarati use noticeable amounts of sugar. A large majority of Indian curries at most have a small amount of sugar, not enough to be discernible to the palate, but helps blend the flavours together. It is nothing like barbecue/meat sauces in the west where the second major ingredient is sugar.
Specifically which biometrics? Perhaps the sensors still need to be invented but what would you like to track regardless of technical feasibility?
As in beer, so, the product. Having source code is great, but when I'm trying to get something done I don't really care about e.g. the EFF's moral stance.
The Rise of Superheroes and Their Impact on Pop Culture with Stan Lee on EdX
Major security flaw undermines Apple and Google users, researchers discover
Great story. even better game...i miss it :(
Oh yeah, I remember Diaspora!
> Nexus is pretty good, but if the language you are using isn't integrated well with gradle/maven you can always just use a shared drive fed by jenkins builds.

Here's where I start to have problems with contemporary development culture. You mentioned using Nexus, Gradle, Maven and Jenkins where the guy just want to keep some binaries along with the source code they're generated from.

We're complicating things beyond reason nowadays.
Well put. I have been asked the same question in interviews. Any interview I gave myself < 8, I could see the interviewer was uncomfortable interviewing a 'newbie'. I am wary of saying anything over 8 because I feel there's no way you could learn everything about something. Not with the amount of information there is on language/paradigms etc
There are three things for me (this is just my subjective account):

1) Ease of receiving texts. Reading a text went from 7 seconds to 1.7 seconds for me. Really nice while driving (I can keep my eyes near the road and not be mentally distracted) or when I'm in lab with latex gloves on ("Oh yes, I do want to get lunch in 5 mins, good thing I saw this"). BTW, if my time is worth $50/hr and I get 100 texts a day, saving 5.3 seconds per text, the $250 watch pays for it self in 33 days.

2) Social implications of checking your phone vs checking your watch. The latter is impatient, but the former is outright rude in many contexts.

3) By filtering the important things through my watch rather than my phone, if my phone buzzes but my watch doesn't, I can safely ignore it, because it is of lower-tier importance. This benefit surprised me, but it is actually rather nice to have an automatic hierarchy of notification importance.
Case Study: I N S P I R I T
I think this is being unnecessarily non-confrontational. As long as you explain why the term is wrong or sub-optimal and what it should be called instead, I can't see how any serious programmers should take offence.

Consider it this way: natively speaking English means you have domain knowledge, sharing that domain knowledge should feel no different from pointing out mistakes in other domains. If someone gets English wrong, that's no different from getting, say, VAT calculation wrong.

Maybe I'm just assuming everyone already handles mistakes in other domains with tact and respect.

Also, it's a matter of proportion. If a function name is extremely misleading that's different from a function name just using an awkward synonym, just as a broken piece of code is different from dodgy indentation. You'll want to fix either problem eventually, but the immediate repercussions are quite different (serious bug vs minor annoyance, basically).
Hell, for a ton of companies (including mine) everything is on 3rd party services/servers. We don't have any servers we can actually call our own.