skysight-inc/HackerNews huggingface dataset:
I don't know abut GoPro, but Fitbit deserves to fail. Their hardware is terrible. The warranty only lasts one year, yet I've had to replace both Fitbit devices I've had twice within that one year. I'm now Fitbit-less because the latest, a Charge HR, failed for the third time, and it's now out of that one year warranty.

To give you an idea of how bad the Charge HR is, its charging plug attaches with metal prongs, but it plugs into a slim plastic housing that is only glued to the rest of the device. The obvious result is that the plastic housing eventually gets pulled off with the plug. That's how two of my three Charge HRs have died. It'd be like if your laptop were ruined within four months because the power cable pulled off an essential piece of the laptop housing rather than detaching cleanly, and now it won't attach in order to charge. The third Charge HR bricked itself during an unprompted firmware update, which started randomly and then I guess got interrupted midway through when I moved my phone too far from the device. It never recovered.

I don't know what the hell they're optimizing for over at Fitbit HQ, but they're trying to sell $10 throw-away quality devices for >$100. It's outrageous. I actively discourage everyone I know from ever buying anything from them, and many other people I know have also completely sworn them off for the same reason. Their product just sucks.
I'm comparing running on linux+docker vs running on linux. Virtualisation is present in both. If you've got the possibility to run the same app directly on OSX and you're not preparing for deployment on another system... why wouldn't you do that instead?
We bought a top loader recently. It was by far the cheapest option that met our volume and reliability requirements. We estimate that an equivalent front loader would break even in about 10 years, which isn't very good.

Also, we buy used/refurb appliances when possible, and there aren't many available front loaders.
> What happens if you want to use a metaphor or turn of phrase that's been forcibly obsoleted?

The same that happens when you try to read any old literature. Like the Illias, which talks about "wine-colored sea" (it was dark blue – the brightness was meant, not hue), or shakespear, etc.

> It's simply not something that belongs to the state, or even to the country.

That likely differs here because the German language was unified in the first place by an academic, and not through consensus.
Not everyone has the privilege to be a single C coder owning the code without anyone else from different skill levels coding in it and without any additional use of third party libraries.
It seems to me that the only diversity in tech that actually matters is diversity of thought: How does this person approach problem solving differently? What heretofore unknown problems do they spot before it's too late? Etc.

Skin reflectivity, ancestry/parentage, anything related to genitalia (be it shape, usage, TypeMismatchExceptions from the brain, etc), net-worth, or history of any of those strike as poor proxies for the diversity that does mater.

Can you solve the technical problem to hand? Great!

Am I missing something that it needs to be any more complicated than that?
Next to Steve Jobs, Tim Cook was the single most important executive at Apple before Steve's death; counting among his successes the ipod. If SJ wanted to install someone who would fail TC was a bad choice.
How is it a conflict of interest? They are all interested in making money... It isn't like he was a public official and decided he was going to give himself tax money.

It is also a private company and can do what it wants in this regard.
My first thought was "Kaiju are coming"
> What i’d want is a generic support for preventing buffer overflows, or bad memory access where i need it

You have that.

For example, if you have contiguous memory, the various forms of the [T] slice type can be used, they don't impose any allocation expectations. (And, once the standard library allows pluggable allocators, you'll likely be able to use Vec directly, for a growable vector type.)

If you don't have contiguous memory, then it's a bit more work, but one can still use features like generics and privacy to spend a few lines building abstractions that bounds check in the right places. It's not like using a proof language to extract a program that is guaranteed to have no out of bounds accesses, or a compiler that some how deduces what the bounds of your data structure is, but the former has its own complexity downsides, and the latter seems infeasible, in general.
Thanks for the wonderful reply. How long do you estimate it took for you to get to the level you are now?
I haven't, either. I've come across plenty that would save me from having painful gdb sessions to fix code inexperienced (or lazy) developers write.
Supposedly Swift 4 is introducing an optional borrow-checker. Types can opt-in and you get the same kind of lifetime guarantees and semantics as Rust. If you don't opt-in you get copying for value types and reference counts for reference types.

I'm curious how either approach will work out in the long run. I understand why Rust made the decisions it did wrt ditching built-in GC/non-GC support but it will definitely hamper its adoption for writing GUI applications. If Swift manages to thread the needle in supporting systems-level / kernel programming with borrow-checked types while not imposing that mental and maintenance cost on GUI apps it will be an amazing thing.

In any case it is exciting to see high-level languages with memory safety proving you can have something much better than C without going full-on virtual machine, runtime, and JIT.
I went through all the Rust features. It doesn’t eliminate memory safety issues at all.
> A hire that knew linux and docker, would solve the problem.

I'd pick a hire who also knew a platform. I like Cloud Foundry because I work on it, Red Hat folk would prefer OpenShift, there's also Deis and Convox and others I am cruelly neglecting.

Containers are a building block. An important one, they make new architectures practicable. But past a certain point, rolling a custom PaaS that you will have to maintain at your own expense, with no commercial or opensource support whatsoever, forever, doesn't make much sense.
In our case, we've been buying the last of the Speed Queen line of completely mechanical washers and dryers (multiple houses). They're reasonably priced, built like tanks, and can be repaired by mortals with screwdrivers, soldering irons and wrenches.

But, apparently, they're on their way out. Frustrating.
Mysterious, unlocateable sounds have always fascinated me. Right now I was just looking for that impossible to triangulate low frequency vibration that plagued that one town i can't remember, but then I typed "mysterious sound" into YT and found out about this world wide event [1] [2] that occurred this year Jan 9-14 and nobody was able to explain it

1: https://youtu.be/mTOQvDzihTU?t=223

2: http://strangesounds.org/2016/01/unexplained-booms-increase-...
systemd is never going to work that way and it sounds like maybe you already know that so it borders on trolling to bring it up. This functionality is pretty straightforward so I'm not sure what the value of multiple competing implementations would be.

You can do something like ExecStart=bubblewrap foo, but that's a different syntax than systemd's native sandboxing.
They did develop the SGR-A1 sentry turret about a decade ago.

https://www.youtube.com/watch?v=azQzwI9-GHU
gRPC is and certainly will never be the fastest protocol for small request/reply messages. The reason is the stream multiplexing layer that is required for it. You almost certainly need to copy data from the connections receive buffer into a streams receive buffer into the application and the opposite for the sending side.

If you don't have the stream multiplexing and just write complete request or response packets to a connection (similar to Thrift) you save quite a lot of overhead.

However this multiplexing feature is also the biggest upside and achievement of gRPC, since it enables you to stream big requests or responses and not only small packets. And it enables multiple big streams (file uploads, etc.) in parallel over a single connection without one blocking another. And of course it enables flow-controlled bidirectional streaming IPC, which can not be found in other systems.
They are quite terrible at all of the other aspects: macro, broad strategy, tempo & timing, planning tactical surprises, etc.

This results in a very low overall competency, when it comes to winning games against highly skilled opponents.

It will be a challenge for researchers to improve performance in these areas. The problem space is very complex -- it makes solving Go look like a cake walk in comparison.
Docker for Mac uses the built-in Hypervisor.framework through xhyve. Still virtualizating Linux, though, so there's some overhead.
These “cultural factors” have to do with strong social and economic institutions like public schools and libraries, reasonably fair and legitimate court systems, a free press and freedom of association, a somewhat accountable and accessible political system, stable and reasonably clearly defined property rights, highly functioning distribution networks for basic goods and services, a fluid job market with protection of labor rights, a wide distribution of political and economic power across many regions and industries, a taxation system which leaves everyone feeling they have “skin in the game”, and so on.

There’s no evidence that immigrants (documented or undocumented) cause any more corruption or crime than native born residents. Indeed, the evidence we have in the USA generally suggests that first and second generation immigrants are less likely to break the law than other residents.

Nativist anti-immigrant rhetoric today in the USA about Muslims or Latin Americans or Chinese is nearly identical in content and structure to anti-immigrant rhetoric about Germans, Irish, Italians, Eastern Europeans, Catholics, Jews, etc. in the past. There’s no reason to believe that undocumented Guatemalans or Syrian refugees immigrating to the US today will be any different than my Irish ancestors were 150 years ago, w/r/t assimilation.
Keep Ruby Weird 2016 talks available
Sounds more to me like an agreement of interest ;-)
I thought so too, until they mentioned one of the events breaking someone's jaw. That puts it more into the land of permissible hyperbole, if you need riot gear level protection to safely approach one during its high energy stored spin cycle....
That's a good point. I was basing it on dates I could find and what I've been reading in Social Architecture. Perhaps the latest C4 is later and PC3 is smack in the middle
Nonono. Godzilla loves (hates?) Tokyo.

This is Canada stuff. Maybe this guy is involved: http://www.thecanadianencyclopedia.ca/en/article/ogopogo/
Gerald Hurst and Chris Connealy are true heroes.
As you note, that's only micro, and it's the easy part since you can do most of that with rather simple rules and just high apm (which is where the benefit compared to human players comes from). The interesting part for AI is how to get there, the longer-term planning, recognizing the enemy's strategy based on what it observes, reacting appropriately, etc. So far those are the things AIs have trouble with.
I know what your point is. I'm not arguing your point. I'm calling it morally bankrupt.

Any person who is at all familiar with the history of the United States of America and has a iota of class stays away from publicizing data that concerns itself with judging whether "those black folks" may or may not actually be "inferior".

Even if your research proved that they are NOT - you'd still have had to question it first to even perform the study.

Personally, I don't believe that there should be limits to what science can and can not investigate. But the individuals who actually perform those studies are no less repugnant deplorables who feel like arming white supremacists with "evidence" is a justified means to gaining scientific recognition.

What does the world gain from knowing this? "Black people are genetically predisposed to being incapable of being smart". Great service to the human race and modern society. Make 500 million people feel bad about themselves in the name of progress. seriously, dude.

And btw, its still just one paper. This is not much in the name of scientific discourse. Maybe "the other side" isn't "researched" because without scientific discourse, you don't actually have much of a result. Without a control study that replicates these results, you don't really have results. You could have engineered them. So long as nobody else is asshole enough to verify those results for you, you effectively don't have any.

Over here in germany, its illegal to research whether the concentration camps actually killed 7 million people. By a back of the envelope calculation, this seems unlikely to me. Its just A LOT. But seriously, lets say some historian assembles all the records and finds its "only 700k"? What kind of person would even want that kind of result on their hands? "Hey look, nazi germany wasn't that bad. It killed only 700k jews. Wasn't even a million".

And yes, I've just compared your stupidity to that stupidity. Because its exactly the same thing. If you want to hate people, do it fucking openly. Put your name to it. Don't hide behind the scientific method. You're just an asshole and we can line up a million mathematicians who would happily poke holes in your numbers all day long if you actually released the real numbers instead of just your carefully selected graphs that "render obvious the mental retardation of the wrong skin color folks".
Who cares? It has absolutely no effect on you, while helping his group of people.

The world would be a better place if people worked on improving their own communities as much as they do policing to make sure nobody else is improving theirs.
drowning in mucus vs. drowning in phlegm

is still drowning isn't it? pretty pedantic.
Top-loading washing machines take up considerably less space than their front-loading counterparts, especially when their doors are open. It is very important in cramped flats.
You gave the link to the database of 300,000 e-mails, and mentioned some detail that has been found there. I wanted to know why the detail is important to you to mention it and give the link to 300,000 e-mails and I wanted to learn in which context you've read about that detail (I guess in some articles) as I don't believe you've discovered yourself and then just point to all 300,000 of the letters, you'd be interested to tell more precise story.

I asked if you believe in some "stronger" (and opposite) statements as an example of some possible views. I never claimed that any of these is yours, I asked to see what you think. That way, I wanted to get you to say something more, in order to learn more myself. I'm still waiting and hoping to learn how is the discovery of the "backchannel" in e-mails relevant and for what, in your view. If you don't want to elaborate, I can respect that too. Thanks.

Also as you consider my "characterization" "not good" I'm interested in your take.
Favoritism?

It is a lot easier to vet someone you have worked with extensively, or if someone you trust gives a recommendation. It isn't like there is some secret society -- it is simply the way the world works.

Those are extra bits of information that go into the equation and they happen to count for a lot. I don't really see a problem with it.

Why wouldn't they give extra weight to those bits of information?

Also, this happens all of the time with positions across the board in startups/companies. If I am a senior engineer somewhere, and we are hiring and the company thinks I have good judgement... of course they are going to take my recommendations of candidates more seriously than someone off the street.
You'd do it that way if you just didn't know any better. "Two tables where A = B" falls into a natural line of thinking for someone who picked up SQL ad hoc rather than formally learning what a join is and the syntax for it.
There's an excellent opportunity to apply machine learning here to automatically let you discover what you like. Starting from a set of varietals and/or random blends, it would generate new blends based on your rating feedback, eventually converging towards your preferred tastes. In addition to arriving at your optimal wine(s), a further analysis of the results (plus qualitative labels from experts) could also generate knowledge useful to you elsewhere, like "You like full-bodied left-bank Bordeaux, and also California Merlots. You dislike light-bodied wines in general."
Well there's LXC, LXD and rkt to begin. Docker have themselves helpfully begun extracting libraries.

The Garden container API which underpins Concourse CI and Cloud Foundry has switched to runC as the container runtime. So far works fine, with no Docker daemon required.

Disclosure: I work for Pivotal, we sponsor Concourse and donate the majority of engineering to Cloud Foundry.
If you see a $100 bill on the ground. Would you not pick it up?

*edit cuz i'm bda at spelling
And you have at most a 110 year lease on the matter of your body.

I'm going to try to leave this place better than it was given to me. Even if it is a small corner.
Yeah, you're going to need to back that one up with some reasonable sources.
I found this explanation of Xiph.org's Daala (2013) very interesting and enlightening in terms of understanding video encoding: https://xiph.org/daala/

Related:

BPG is an open source lossless format for images that uses HEVC under the hood, and is generally better than PNG across the board: http://bellard.org/bpg/

For a runner-up lossless image format unencumbered by H265 patents (completely libre), try http://flif.info/.
No, it's really not. It is a major key to solving it. Not "The" key, because there are a few pieces to the puzzle. But it is a really major detail.
Sorry, but you're wrong about this. This is my opinion on the matter and I understand that not everyone will agree with me.
"He was also fooled in some blind tastings, like believing a white wine was actually red."

This propensity (being "fooled" by white/red of a wine) is very often cited as "proof" that wine drinkers don't know what they are talking about.

In fact, the broad taste profiles of either white or red grapes - and the difference in expression of those profiles based on temperature - can make it very difficult to discern certain reds from certain whites.

"Fooling" someone with red vs. white really isn't that interesting at all.
What's a specific memory safety issue Rust has outside `unsafe` code?
> vastly superior energy and water efficiency of front-loading machines.

Don’t mix up the two different types of top-loaders

There’s the European Model, and the American model. The American model is inefficient, but the European model of top-loaders is just as efficient as front-loaders, far easier to construct, and requires less maintenance.

I’ll quote Wikipedia to explain the European model:

> Some machines which actually load from the top are otherwise much more similar to front-loading horizontal-axis drum machines. They have a drum rotating around a horizontal axis, as a front-loader, but there is no front door; instead there is a liftable lid which provides access to the drum, which has a hatch which can be latched shut. Clothes are loaded, the hatch and lid are closed, and the machine operates and spins just like a front-loader. These machines are narrower but usually taller than front-loaders, usually have a lower capacity, and are intended for use where only a narrow space is available, as is sometimes the case in Europe. They have incidental advantages: they can be loaded without bending down; they do not require a perishable rubber bellows seal; and instead of the drum having a single bearing on one side, it has a pair of symmetrical bearings, one on each side, avoiding asymmetrical bearing loading and potentially increasing life.

https://upload.wikimedia.org/wikipedia/commons/5/57/European...
Yep, me too - more like, if I was blind, I wouldn't notice the difference. Which is why the bitrate is always the first thing I look at when sourcing video.
The Optimal Level of Security Spending [pdf]
Forget self-driving car anxiety: In the early days human drivers were the fear
Now you know two people who describe raising your hand to touch the display as natural!! I'm a great proponent of touchscreens for laptops and even desktops. Sometimes I point my finger at my non-touchscreen desktop monitor, because, you know, it's natural when your used to a laptop, tablet or smartphone with touchscreen.
It's a bit unfair to claim that a person can't have _anything_ interesting to say in regards to _any_ subject because you disagree with the statistical methods in one of his books, isn't it? Moreover, not all of Better Angels relies on a statistical argument, and so it might still be the case that Pinker has some interesting insights into the nature of violence.
The author listed quite a few apps then:

> A couple apps you won’t see on this list are Chrome and Slack

He explained we should:

> in my opinion you should boycott them until the developers learn how to write them to play nicer with memory

I stopped reading. Selection bias is selection bias, no matter how you try to talk it out.
What that article doesn't point out for laymen is that the CP-140 is essentially a P-3 Orion: A specialized anti-submarine warfare aircraft equipped with a MAD[1] and sonobuoys[2]. It's a pretty capable maritime surveillance aircraft.

The fact that the signal went dormant/was not able to be detected by something as sophisicated as an Aurora speaks volumes.

1. https://en.wikipedia.org/wiki/Magnetic_anomaly_detector)
2. https://en.wikipedia.org/wiki/Sonobuoy
If there is evil in this world, it lies in the heart of mankind.

-Edward Morrison
'Computers are capable of extremely fast control, but that doesn’t necessarily demonstrate intelligence, so agents must interact with the game within limits of human dexterity in terms of “Actions Per Minute”.'
Newborns may be blank slates, but college- and working-age people clearly are not. By the time we are ready to join the working world, we are already imprinted by what our culture tells us are "male" and "female" jobs, for example. I don't think of that as discrimination. It's discrimination if a female applies for a construction job and is passed over for being female, not if she never applies because she thinks construction isn't for her because that's something men do. But both lead to a lack of diversity.
You can do a huge load in a reasonable amount of time with energy efficiency and usually reliability.
As someone who currently has a Samsung stove, I can wholeheartedly say I hate the thing. The interface is one of the worst I've seen - touch "buttons" on a stove. It does't work half the time if your hands are the slightest bit wet - which they often are after washing hands. It's incredibly frustrating, and has completely thrown me off about buying any sort of Samsung appliance.

Samsung has such potential, but it's untested things make me wonder about their long-term value.
It doesn't work on chrome on linux for me. But my android phone (LG) and Windows Edge seem to run it fine.
I deeply believed front loading was energy wasting and only here to free the top part for interior design while looking like a fancy boat window.
True, but maybe with this switch to wa tighter release schedule we might be able to see them land in a not too distant future
Docker is unstable trash and does not belong anywhere near a production environment.

Unsurprisingly the linked article is fraught with glaring errors and misinformation. This has become typical of most things I read that is docker-related; it's a circus.

It saddens me to see the Linux community get dragged into and overwhelmed by this mess.