skysight-inc/HackerNews huggingface dataset:
For what its worth, Unity is a pretty global company. They have marketing based in SF but also have an office out of Bellevue. The majority of development though is still based out of Copenhagen and other European companies.
I thought the product was pretty cool. It "automated" networking with other professionals who might be good hires or potential co-founders in the future. You'd sign up for a specific time (e.g. Friday at 9am) and once a week get an email with someone to meet and a location to grab coffee.

I went on a few of these meetings and thought there were some interesting people in the network. Sad to see it shut down :( That being said, the service was free and I don't know if I would've been willing to pay Weave.
You never dispensed any advice, so your disclaimer is unnecessary.
The purpose is completely different. You use interfaces and composition to decouple the implementation of some objects, you use inheritance to define some object hierarchy. Inheritance specifies the is a relationship, Composition the has a. As you can see these two are totally different concepts.
I've also had exchanges very similar to the above. What I think happens is that managers think that we're negotiating. Negotiating for what? I have no idea, but for many managers, it's their default assumption.

In fact, we're not negotiating. We're describing the situation to the best of our understanding. Indeed, when often these situations have started to feel like negotiations, I've stopped and emphasized that this is not a negotiation, this is my very best estimate as to what I need to get the job done, nothing more, nothing less. Sometimes this gets through to them.
>People need to know why they can't trust you.

Why can't people trust him? Seems like a good guy to me.
> The point of the parent was that the statistics are not better for auto pilot

No, that was not his point. He said "Probably not."

That's wrong. It's not probably anything. Both the parent and gp are wrong.

And the negative tone of your comment is wrong too, since there is no evidence to suggest a problem with autopilot. Wait until the data is in. One dead dude and a couple of accidents doesn't mean a damn thing with millions of miles driven. It might be worse, it might be better. That's not an indictment, that's the case with anything new.
I agree with your second paragraph very much. However, your third paragraph points out the adage that continually needs to be reiterated, and you kind of hint at it. If you are writing a basic app that fetches some json and displays it to a small group of users, then no, a framework stack like react/redux is not needed and you can stick to the basics. But when you have a complex application that needs to scale, react is a handy tool to help accomplish this task.

Furthermore, I think it's normal for react to bloat a little bit while programmers suss out new features and usage. However, hopefully paradigms will solidify over time and that bloat will start to deflate.. hopefully.
If the prison provides them, they might be made location-aware and tamper-resistant. "Unit 23892 was in Hallway 11A at 1130 hrs when it went offline. That hallway was occupied by Prisoners 981, 1481, and 1891 at that time. Unit 23892 had previously been checked out by Prisoner 2110."

It just stands to reason, as the Panopticon is assembled for those of us who are yet "free", the same technology could also be used for those who more obviously are not.
Well , let me take a stab at explaining what the service is. I used Weave for about 5-6 months (infrequently though). Its exactly like Tinder, Once you sign up and fill out your profile - the App starts showing recommendations , and you get to swipe left or right , and then if there is a match , you start chatting.

One of the base use cases was Recruiter-Candidate connections.If I am looking for a job, and then I bump into a Recruiter's profile who is looking to Hire in my area of expertise, I hit like & if there is a mutual like - You start chatting and go for a coffee to learn more about the opportunity. Sometimes , these are directly the founders of small companies. The timing did not align all that well for me ,though I chatted with a lot of entrepreneurs , I never ended up meeting any one in person.

I suppose , this would have eventually grown into some sort of 'professional introduction' platform - And Weave would have charged you for the introduction. Unfortunately , looks like they couldn't get to that point at all.
This article reports on a study finding a link between "systems thinking" oriented parents and autism.

http://arstechnica.com/science/2011/06/kids-autism-may-be-re...
Is anyone (especiaially on Linux) still using Skype these days?
You're conflating 'The British' with British Rule. Two very very different things.

also, no need to educate me on my history my friend. I understand it deeply but I'm not defined by it. As are the vast majority of my countrymen.
If there would be a realistic way to reliably identify 'luxury' purchases, you could just have a really infuriating interstitial that:

* displayed the amount of money in a personally relatable manner - "ShineyTron300 costs the same amount as your last 2 months of food expenses, are you sure? (y/N)

* make it easy to cancel/stash or defer the purchase, including as you suggest, an enforced time delay before re-prompting

* make it hard to complete (require several captchas, solve a maths puzzle, or complete a couple of levels of Duolingo or something) before letting you through.

* Enforcing a personal 'luxury sales tax' that padded the total amount of some %, and transferred that amount to savings if you complete teh purchase.

Basically, go hunting for dark patterns, and use them against yourself.

I'm not sure how far you could go without it just being too annoying and disabling/bypassing it though.
It's very unusual to have such a complete change of board membership, isn't it? I'm all for new blood, but I'd worry at the near-total loss of continuity.
If you use shallow render for your unit tests, Enzyme is much much better than Test Utilities. Just to name a few reasons:

- better event simulation

- easier to update prop

- allow setting and getting state

- easier to refresh after triggering changes

- comprehensive selector support
you can craft all the laws you want, the mega-tech companies will always cluster in SFBay. If you're Dutch and you start a subsea oil exploration robotics company you will certainly open an office in Houston. And then your biggest customers and market will rapidly be Houston, and so your largest office becomes the head office. If you're Colombian and invent a brilliant trading algorithm, you will probably move to New York, regardless of the laws in Colombia.

This is just common sense. The best bet is to proudly foster these small companies which go big overseas and also have an ecosystem of smaller players who don't have huge multinational ambitions, likely also funded by these unicorn exits when the money recycles locally.

Of course, tune and craft laws and regulations to create the most output. But stop trying to fight this clustering effect...
GPU-Accelerated Black Hole Simulations
I might say, "I don't think I can do a startup with you and still maintain our friendship. And I'd rather be your friend." (Without telling him/her why you can't do a startup and still be their friend...)
Imperative vs. Declarative Programming – Free Code Camp
For those of you complaining about "javascript complexity":

I think one of the biggest misunderstandings about JS and a large portion of the community complaining about "churn rate", is that JS does not have a churn problem, it has an inexperienced developer problem. Which is not to say that is a bad thing, JS/web is the first language for MANY programmers now.

When you get stuck on learning this framework vs that framework, or a antipatterns within a framework and "complexity" being added to a framework, take a look back and understand the WHY first.

Many ideas and the fundamental design of React are not new. Infact, they are very old, even before there was such thing as the internet.
Functional programming patterns, also very old.
Immutability, a very old concept.
Composing rather than inheriting, old concept.
Eliminating all side effects (through immutability and composition), very old concept.

The idea of a "higher order component", is not new, nor does it have any direct relation to React. It is a design pattern. This article is simply teaching you a design pattern that aligns with the design patterns React was built upon and works very well. Instead of complaining about React and "added complexity", I encourage you again, to ask why. Learn why this blog post, from the React core team, recommends doing it this way. It is in no way a requirement. React is just a tool. It is just Javascript. It is just programming. Welcome to the development world.

Also, understand the problems you are trying to solve. Facebook uses these design patterns because they have thousands of components at a massive scale. The majority of users will not be working on something of that size. Don't feel like you have to use everything that comes out and is available in the React ecosystem. Infact, I would urge you, never start using something UNTIL you come across a problem and need to find a solution. It is a common thing for inexperienced developers to feel the need to incorporate everything they have read about, when they are using them to "solve" problems they don't understand, nor even have. This applies to problem solving in general, not just React, not just programming.

TL;DR
Understand WHY something is used in the way it is before throwing it out as "too complex". Don't solve problems you do not have, until you need to actually solve them. If you do use a pattern/tool/etc., understand the WHY. (Don't use Higher Order Components or redux if you have not had the need for them and do not understand the problem they solve.) Also understand that many design patterns coming to JS are not a result of JS churn, they have been around a long time and have a very good reason for existing. JS churn is not real, it is a misunderstanding of using a solution in a world that has many solutions available.
I work at Sony R&D
Always Be Closing: The Best Sales Tool for Startups
An that process has a provision for the customer to file a dispute and this obsolves the host and sends the matter to court. Ot did you
Miss that comment?
Right. What we're talking about here are tools. We can't understand or debug the electrons moving through the chip. But we build systems using languages and we build tools to translate execution back into those languages (Debuggers) Or tools in the execution to allow us to understand what happened later (Logging, metrics.)

I think the key problem right now is that there are not too many models for which tracing the execution lets us know much about what's happening. A single decision tree. A linear model. But add ensembles to trees or layers to linear models and the ability to understand what's happening through logging disappears.

In this sense I think we're essentially in the pre-assembly language state of machine learning. For most programming languages, we assume correctness as a given. If it produces the wrong result on correct inputs, that's really bad.

With machine learning, we don't have perfect correctness. Aka accuracy. We focus so much on improving accuracy that we rarely consider the trade-off in debuggability or interpretability.

I think this will have to change. Advances in NLP and image stuff from deep learning are very exciting. Ignoring the evil AI concerns, I think the best step will be trying to understand better why the models did what they did. I think it will be a while before we can just ask the model and get a reliable answer. In the meantime, I think we'll work on a kind of meta programming where we integrate models better with their broader context. An example might be sequence to sequence models that have a way to expose sentence fragments and documents in the training set that influenced a word choice. Or automatic labeling of clusters in image representation layers that have semantic meaning to a human. There's some interesting work already on debugging tools for image classification that I really liked. On the phone so I'll try to provide the link later.

The trouble is it all seems very domain specific. Figuring out how do it in a way that's not so domain specific is i think a very interesting thing to work on.
I apologize in advance for my lack of detailed knowledge about low-level IO, but,

Would a library like libuv/pyuv that provides an async interface to networking and file IO help in this regard?

I understand that your goals were to implement as much of the Python stdlib's APIs so that programs can run unmodified, but could you envision Python applications that are coded against pyuv running on a platform that bridges pyuv calls directly to EFI without the stdlib as an intermediary?
This is only tangentially related, but there's a legal case that was discussed on Radiolab (the Buried Bodies case: http://www.radiolab.org/story/the_buried_bodies_case/) which you might find interesting.

Essentially: A serial killer told his lawyers where two of his victims were buried. Should the lawyers disclose this information even though their defendant was the only source?

It's interesting because it's not merely hypothetical, and their reporting is fairly good.

While it doesn't answer your question, the spirit of the answer can maybe inform the spirit of how one would answer your question.
Before the ACA, there were a handful of ways insurers could balance their risk
pool. One big tactic was just to avoid covering sick people, filtering out
individual customers who appear likely to need lots of expensive medical care.
But Obamacare made that type of discrimination illegal: One big selling point
of the law was that everyone would be eligible to sign up.

Companies that profited off of denying helping people with pre-existing conditions are finding they can't profit anymore? Allow me to play a little ditty on the world's tinniest violin for them.

The honest reality is that these costs did exist before, it's just they were paid by the sick in our society by dying, while the health insurance companies skimmed off the cream from the healthy. No free lunch, right? So this cost existed, only by law, it was pushed onto the healthcare companies after the ACA

It is quite bad though, as the article details, costs have reached 100% of premiums at least in NC it looks like. That is unsustainable, and since the ACA went ahead with requiring healthcare companies to help pull this off, without something like a public option to cover say the super sick, this isn't good news.

All around, this is a bad. But it's not like ACA made it worse, it just made the costs appear somewhere else, and as the article states, absent of any new policy, that cost will shift back to the sick who will have to die again.
Multi-Piece Shipment Support Available in the Shippo API
How to Use the Facebook Pixel for Your ECommerce Business
Yeah, in the middle of a big city, particularly one near a park/common congregating place, you might run into problems if you're competing with a spot that has two or three lures going off in close proximity. But lures don't last forever, and the landscape is different in the evening vs. in the morning vs. during lunch hour. Also weekends vs. weekdays. You can literally just watch the lures go up, and then dissipate as players come out and go away, and have different objectives in the game.

You don't have to actively play the game just to have an account and keep an eye on what's going on in your area, and business owners could place lures strategically when they think players might find them most useful.

This worked really well for an ice cream shop near the beach I went to recently. Lots of people walking by collecting Pokemon, and they were one of only a few shops within 40 meters (there were a lot of residences in the area). People who clearly were not at the beach to get ice cream basically swarmed the place -- they saw the lure and thought "Oh, actually, it would be nice to sit down for a while
and have an ice cream cone, now that I think about it..."

Also, players can see the name of whoever set up the lure, so you can use your player name to advertise your business, and then post it on a physical sign outside, as well. I haven't seen that done, but it would be pretty cool.
Source? Do AAA games even use that engine? Do most AAA games not have their own engine?
Ask the mods to edit the title. The title should be ShowHN: We've just made a FREE Rubik's puzzle app
That said, music practice after Bach did acquire more tricks in the notation to indicate performance. There are more constraints on how to play Chopin or Beethoven, say.
I do not believe radar is part of the instrument set.

There is a "gravity sensor" which is really, I think, an extremely careful Doppler measurement which will allow us to infer the mass distribution within Jupiter.
It's really quite a nice crash reporting product. I think that outweighs the closed-source point for a lot of folks.
Redux-Mori
> Do we at least agree that actual factual airplane autopilots are fairly analogous to Tesla's?

Nope! That's the whole point of contention, actually. Autopilots are very advanced and can do almost the whole flight. Because the control problems for airplanes and cars are very, very different.

If something goes wrong with the autopilot in an airplane you've got minutes (at least) to figure it out and not die. ~30,000 feet of altitude and huge glide ratios and nearly empty skies do wonders.

In a car your average car-to-car separation in rush-hour traffic is a few seconds along the line of motion, and perhaps less sideways. If you're not on the freeway you might be a jerk of the wheel and half a second from a head-on collision.

Now you might say that the technical capabilities of both systems are the same, but nobody really cares about that. They care that it can meet some criteria that they already have in their head and they aren't going to go to school for 5 years to understand that it's not the autopilot's fault that their kid enabled in bad circumstances and died, they're going to sue Tesla to hell and back. And judges and juries will quite likely be sympathetic.
.... "but its for our safety"
Redux-mori
I love the nature of his prose, but it's definitely not for everyone. One of the best things about the book for me was his emphasis on understanding the concepts through experience (singing against a drone), but of course this isn't everyone's goal.

Still, for me, it continues to be a life-changing read which fundamentally altered the way I think about and hear music, and I've worked as a professional musician for more than 20 years.
Ring My Phone
> To play devil's advocate: Drugs and the criminal networks supported by drugs are a massive problem in the Philippines. Police are too weak and too corrupt to deal with it, but this is a solution that works, even if it does offend our first world sensibilities.

To play devil's advocate: Jews and other degenerates are a massive problem in Germany. Police are too weak and too corrupt to deal with it, but this is a solution that works, even if it does offend our first world sensibilities.
You're missing a subtlety: it's a live migration. You've also got to migrate the data the VM's writing while the migration is going on. Depending on how your network's set up, it might well be possible for the VM to saturate out the migration process. Plus this won't only be planned maintenance, it'll be to get off dodgy hardware, too, including spannered RAID controllers where you really don't want to risk hanging around. Add in that you're likely going to be moving sets of discs at once (so possibly a couple of TB at a time), rather than individually, and you're very quickly looking at spending a day (or a night) at a time watching in case there's a network blip which means you need to restart any of them. This does not lend itself to a peaceful, happy existence.

It doesn't take doing this very often to make you realise that this is fundamentally backwards: you want the disc data already present on more than one storage server so that if one goes pop, you're not stuffed. Once you've done that, you can make the observation that hardware RAID is no longer necessary, and save yourself a layer of complexity.
> little memory of CPU as a modern terminal emulator.

Browser instances can be quite svelte. But uh... I mean... shared lib pages tend to be actually shared pages. That's why the physical memory for multiple browser instances is a lot lower.

What's more, I'd gladly pay a higher price for a richer experience. We no longer need to or should rely on ANSI interfaces. In fact, they're becoming increasingly awkward in a world that really wants endpoints to be stateless by design rather than stateful sockets.

Many people have already discarded the single socket model oh SSH in favor of Mosh. Let's also ditch the console for all but the most basic of tasks. It's not 1997, the lingering stink of proprietary rich client environments is cleansed. Web browsers have annihilated that assumption and made something truly open and pretty amazing.

I use a web browser as my core text editor and I miss emacs not a whit and quite honestly it feels more responsive than my emacs setup. I don't notice any tangible performance differences from Vim in a terminal.

We can do better.
The risk of uninsured driver getting himself (and you) in an accident in an improperly maintained car.

This should be addressed regardless of Uber's existence. In Poland we have an Insurance Guarantee Fund (Ubezpieczeniowy Fundusz Gwarancyjny[1]), an institution which pays out judgements to people harmed by drivers without proper insurance.

[1] https://pl.wikipedia.org/wiki/Ubezpieczeniowy_Fundusz_Gwaran...
Why not just mock the HOC to be the identity fn? `(Component) => Component`
This comment makes no sense to me.

What if the client asks you to give them a product once per year. Does Agile recommend telling them no, turning down their money, and reply, "Sorry, but Agile says I have to delivery the product continuously."

The two words "continuous delivery" mean to deliver something in such a way that the customer doesn't experience gaps between the release of improvements, upgrades, fixes, additions, or desired changes, so that they are not staccato changes at major discrete instances.

Crucially, the customer, not you, gets to decide what "staccato changes" and "major discrete instances" means to them.

If the customer says to you, "Receiving these changes any faster than once a year does not help me" then "continuous delivery" for you, in that case, does not mean the same thing as the modern buzzword ideology of continuous delivery.

Nonetheless, you could still use an Agile process in that scenario. I wouldn't recommend it though.
I think this whole open source and right to repair/modify will be very interesting with self-driving cars, because of their interaction with the commons. Here are some issues.

There have been some discussions about the ethics of self-driving cars if it should sacrifice the lives of the people in the cars to save more lives. In a right to repair/modify wouldn't a lot of people pay to have the algorithm changed for their car to always favor the people in the car no matter what?

If the self-driving software is completely open source, you can exploit the collision avoidance algorithms to favor aggressive driving with your car. For example if the software tries to keep a 15 foot buffer between cars, you can"tune" your software to use a shorter buffer and cut in front of traffic more easily.

Law enforcement will campaign for a remote "pull over" command to prevent people from fleeing police.

The answers to these types of questions will be very important for open source going forward.
Nightcode the Clojure IDE