skysight-inc/HackerNews huggingface dataset:
I believe as time passes, we are moving away from the simplicity that made React win. Flux, Redux, higher order components generate too much complexity most of the time. React used to be simple, it still is, but the ecosystem and the mentality has gotten needlessly complex.
The whole idea of "just work for us for a while" is so ridiculously employee hostile I couldn't resist mocking it.

The idea that I should risk my current job for a chance at working elsewhere is terrible.
It might be better to design a prison that actually rehabilitated people. Then perhaps there might be a little less violence.
This looks really interesting but I personally really dislike the pricing, maybe others will love it but to me it's nearly impossible to guess how much this will cost me. When I start a new project I have no clue how many requests or queries will be made. I get the advantage of not working about infrastructure but I'd rather pay a flat fee and then be able to scale up to handle more requests.
Thanks for feedback. The post contains what is in title. If you want to see a demo please tell me.
It is quite dissimilar in its applications on pretty much everything but national security.

You won't see things like this in the US http://europa.eu/rapid/press-release_IP-16-1937_en.htm

Some European countries (such as Sweden and Germany) and the EU as a whole have been stepping up censorship of both social and traditional media these past few years.
While it's easy to classify this as just fighting "right wing extremist" much of what is being censored wouldn't be considered right wing nor extremist in the academic sense in any way.

This does not only include traditional "hate speech" like immigrants are bad... mmkay or jews are evil but goes deeper and threatens to classify any criticism of EU policies or anything that causes political disturbance as "hate speech".
Whats even more disturbing is that many of these measures are enacted on the back of terrorist attacks in Europe and over the world, but end up being used in combating local political dissent.

If you'll want to make an analogy to what happens in the US then the latest EU movements to cramp freedom of speech are not that different than the massive surveillance program that the US embarked on post 9/11, if anything it is probably worse.
While surveillance might have a negative effect on expression and it sure can help breed homogenous group think, dictating what can and cannot be said, and what should are should not be thought is considerably more dangerous.
More of an emacs philosophy than a unix one.
Show HN: Checkin – One-question surveys through Slack
Whoops! It happened quite a few times that some artist submitted their work (photos, illustrations, etc), our experienced editorial team polished them and the attention and traffic really kickstarted their career. Here are some selected stories: http://www.boredpanda.com/success-stories/ .

Also, I believe, we contributed significantly to the coloring-books-for-artists trend which was quite a thing in late 2015 and sold loads and loads of copies, because I think we were the first major publisher to publish a story about them.

Not something world changing, but it's good to know that I contributed in one way or another to actually help some artists :)
> This is a good step forward, but until we (the citizens) are able to say that LEOs are no longer using parallel construction[0], this is a lot less helpful than it could be. This just means LEOs have to work a bit harder to mask their illegal activities.

But that's good. Don't let perfect be the enemy of better. Before this ruling, they didn't even have to go that far. While we assume that LEOs are good at parallel construction, standard human laziness applies and something will trip them up a lot of the time.

If a three-letter-agency is out to get YOU, specifically, you are hosed no matter what. However, that is a different problem from an LEO being able to vacuum up a ton of stuff and sift through it cheaply simply because they need a couple more collars to make their drug arrest quota.

If the NSA is out to get you, they will simply fabricate the evidence, no parallel construction needed.
Yup, that's what those big pixels are good for.
Tesla launched autopilot like a startup in beta mode before big co's and regulators could slow it down. If you believe computers will eventually be safer drivers, would you prefer:

A) Autopilot launches gradually over 20 years by a big co, costing hundreds of thousands of lives due to 10 year delay or

B) Tesla launches fast below the radar, iterates quickly, makes data-driven incremental updates to autopilot and saves 10 years of human error deaths?
I think a very important nuance here is that it is not enough to just tell other people to commit crimes against people from a religion/race/color/gender/..., it must be suitable (I have trouble translating here) to be effective in that matter. The reason is explicitly the human rights, because nobody should fear to be harmed because somebody told other people to harm people from a certain gender/race etc.

There are BTW other "Äußerungsdelikte" (statement offenses, free translation), like slander and deformation. All these are based on the human right that no harm should be inflicted on you because somebody says something wrong about you (in a very simplistic way, you normally would have a lots of hours of law lectures just on this offenses, their reasoning and distinction).
It's hard to stress how accurate this is, once you've had a manager who's good at this it's very obvious what separates the wheat from the chaff.

Same is true in the Program Manager/Tech Program Manager/Producer roles.
With a looser definition of religion, we already have modern forms of religion: Apple, Whole Foods, ...

They stimulate the same neural paths [1], they have the same cult following, and they for sure have reliable revenue streams from their members.

[1] (low quality link, sorry) http://www.businessinsider.com/apple-is-a-religion-neuroscie...
I've never seen that before. Using a gerund as a noun seems very unconventional and incorrect almost by definition.

Simply ‘work’ reads much better—is it really frequently used as ‘working’ in mathematics‽
What does that example have to do with parallel construction? They could easily get a warrant in that situation, ending in a raid with the same result.
Very well timed. I wonder if they held on to get more valuation on the positive PR.
1. Clicked "try it now" for demo.
2. Went straight to a "give us your email" page.
3. Left and will never go back.
The analogy is with anything with a brain, not just animals. Take a poorly trained human and put him in a decision-making position, he will probably make bad decisions. But no amount of training will guarantee you that he won't make any. The learning data set is just too big to be sure you won't have any bias.
Alternatively…

"LIKE GOOD STUDENTS, COMPUTERS NEED TO BE ABLE TO SHOW THEY'RE WORKING"

heh.
Is the article arguing that ability to execute is not a distinguishing factor for startups? Or just that non-technical execution is more important than technical execution?
They detail their reasoning in their tweet, otherwise I'd suggest you ask them, but I'd suggest that we avoid a speculative discussion about race based on some random person's twitter rant.
Anything that starts with "For the most part, I was wrong." gives me a boost of trust and respect for the author of the post. It is hard to admit your own fault and it is much harder to admit to it publicly.
Ever since I started driving in US streets, I've been shocked and terrified at the amount of people checking their cellphones in dangerous situations. Inching the car forward at a traffic light without even looking forward, texting doing 70+ mph on a bridge, yelling at their kids in the back seat, changing lanes without looking at their blind spots...

I'd really prefer if those vehicles were driverless instead. And mine as well.
For appcrap and webcrap startups, that's true.

But thinking like this is how Theranos crashed and burned. Their funders needed to ask hard questions, and didn't.
I usually use Bonnie++ when testing disk performance.
http://www.coker.com.au/bonnie++/
> without invoking the supernatural

I see this being a key common ingredient for a successful religion today.
You can use React without Flux/Redux if that works well for you. The “mentality” is just people solving their own problems in a way that makes sense to them, and sharing those solutions.

As noted in the blog post, higher order components are not a React feature. And it is not related to Flux or Redux. It is just a thing you can do with components, like you can do it with functions.

We think HOCs are a useful pattern so we explain it, but you don’t need to use it if you don’t get value from it. (We got a lot of value from using it.)

That said if you have different solutions to the same problems that don’t suffer from the drawbacks of mixins, we’d love to hear them. This post is not there to force you to use HOCs. It’s for the people who had the same problems we experienced, tried to use mixins to fix them, and couldn‘t scale those solutions.
Do Brits use gerunds other than ‘working’ as nouns or is it specific to that case? Either way, that's really weird.
In my experience, as long as you have a well tested data model and use proptypes/Flow/TypeScript, testing the components themselves becomes almost entirely irrelevant.

However, I can see the utility of component testing if I were wrapping something like Ace editor or a jQuery plugin or something of that nature.
Building a modern functional compiler from first principles
I made the mistake of reading the comments section. I can't fathom how people take such pride in their lack of knowing how computers work. Sure, there are things I don't know, but I don't think I'd ever take pride in that ignorance.
I feel like React is shifting in the same direction as the JavaScript ecosystem at large, which is unnecessarily complex, disorganized, and fast-moving.
That's because people are using it for real things now, not just as a jquery plugin replacement, and it turns out that ignoring hard things doesn't make them go away.
A (fixed) trial period is analogous to having constant list prices or, in statistics, simple average with some constant time period. A more flesible approach would be to gradually decrease the amount of resources available to the account. Or even better some kind of machine learning algorithm could compute how these resources should be varied in order to maximize some goal function (like probability of switching to a paid account).
If simple things were possible before with React, then they still are, and that's not changing. You don't need Flux and Redux a lot of the time; in my experience they're overused and React component state is underused.

I agree the community mentality of adding lots of complexity on top is a problem. We're working on improving this, but if you have ideas I'd be interested to hear them too.
Maybe I'll finally be able to understand music.
Check out cycle.js. I haven't learned it quite yet but the promises seem really interesting. It's a fully reactive framework unlike react which is reactive only in view.
"It’s kinda like having 10 Facebooks to simultaneously look through, then make sense of. Actually, no, its worse. Facebook isn’t about returning back to, its about relaxed consumption of content. Slack on the other hand is meant to be about getting things done and being there to respond."

Love it!
Hi, point taken: we can explain on the signup page in more detail why we can't accommodate every user.

Thanks for the feedback.
Yes, Apparently they do. See Gustomaximus's link.
I personally moved all my projects away from mixins a while ago when I first heard they were deprecated. At first I was frustrated because of JS churn but this certainly was the right move.

For anyone who is apprehensive, the shift in thinking from using mixins to HOCs was not so difficult even if it's initially puzzling.

Quick edit: forgot to mention that this shift made my code way easier to understand in some places and thus the initial investment saves dev time in the long run.
Actually, maybe you should try Slack in earnest with a project team before assuming the OP criticisms are wacked.

I tried it with my team about a year ago, and all of the OP criticisms resonate with me. We don't use Slack anymore.
Great to have this feedback! Nothing's set in stone yet. This is what we're launching with but I'm sure there's a good chance we'll have something more palatable for you down the line, if you're interested! :)
It's not a fiction, nor is it "photoshop", it's actual data.

The basic problem of all astronomy from Earth's surfaces is that the atmosphere impedes seeing. So much so that even small backyard telescopes rapidly reach the limit of atmospheric seeing before hitting the limits of diffraction. There are several ways around this. One is to leave the atmosphere entirely, resulting in the stunning capabilities of space based observatories like Hubble. Another is adaptive optics, which relies on various techniques to read the atmospheric disturbance causing degraded seeing and precisely counteracting it by interposing a reactive optical element.

The technique in question is basically a sort of poor man's adaptive optics related to speckle imaging (another technique employed for the same purpose). For bright objects (like planets) an image exposure using modern CCDs need only be a fraction of a second. Which provides the opportunity to collect many of them over a period of time, which is something that many cameras already do quite well by recording video. The alternative of counteracting poor atmospheric seeing is to hope you get lucky and capture a moment where atmospheric distortion is at a minimum. Such moments are rare and fleeting, but over the course of hundreds or thousands of images from a video stream, there will be a few. The trick is to find the best moments of seeing for a given portion of the image from within the frames and combine all of them together into a single image. You then have essentially a "dream team" of atmospheric seeing conditions for every part of the image. Every part is real, and the overall image is a true representation, not a fantasy.

However, your point about the futility of comparing the two is accurate. Comparing a single image from Juno to the best thing produced from a backyard astronomer ever is not a good comparison. Especially since Juno will collect a great many more pictures and is not at all optimized for taking pictures at its current distance from Jupiter. The best pictures of Jupiter from Juno will outclass anything we've taken with any instrument from any observatory or spacecraft so far, but it'll be a while yet before we have those.
It doesn't fare well that a framework that is only 3 years old already has an extensive list of anti-patterns and tons of statements on what not to do. Also having to do manual performance optimizations using the framework is a hassle to application developers and can be a major pitfall (ex. PureRenderMixin, shouldComponentUpdate).
Should work now. Just pushed a hotfix. Thanks for the catch! (You and everybody else.)
It is a pretty delicate balance and requires good engineers.

If you're a religious language defender (bleh, why are you using Java, Perl, etc.), you're not going to be objective. Different languages are useful for different problem spaces. Somethings are starting to show their maturity.

For example, I use to write software that ran on OpenWRT based tiny/embedded systems in Python, because python-mini was present and I could install it, my dependencies and everything I needed in less that 16MB of space. There weren't many options for that footprint other than C, but that was 2011. If I wrote it again today, I'd have to seriously consider using Rust instead.

Being a good engineer/architect requires a lot objectivity. It involves working at different shops with different frameworks, languages and design decisions and filtering through all of that. It involves constantly searching for "I really hate <x>" and "<x> is a piece of shit" every time you find something you really like and have pushed towards your production release, just to see what issues other people have and if their problems are things you may run into. By the same token, when you use something you hate, you want to do the opposite searches as well (e.g "I really love Powershell").

This article is really written from a business perspective. There are a lot of businesses that survive their startup incubation period with terrible design. Some even become profitable. Good luck keeping your developers though.
So WhatsApp had did have bigger team (you're comparing 50 engineers vs 50 employees total), and now it's even bigger. There are hundreds of people working on WhatsApp.

It seems to me that WhatsApp and Vine have a similar staff to user to ratio.
FYI. Our system can also do "minority report" based ad retargeting. Also, we have a few large retail/auto dealers ready to deploy sooner then later. We are getting there but things could be moving much quicker with a little capital for additional developers, etc.
> Is this budgeted?

Yes.

> Is it on a launch docket?

Yes.

> Is there a rocket ready for it?

It's being built right now, the test is in December.

> Is the lander completed?

It's being built right now, the test is soon.

> 2018 is right around the corner and frankly I'm getting sick of "Spacex might" comments.

SpaceX has completed every single thing they have ever said they would do, except for things that remain in the future. I don't know how you could be sick of "SpaceX might" because it generally means "SpaceX will".

> I'd like to see more "do" from SpaceX that isn't LEO flights and landing on barges.

They're planning on colonizing Mars by sending 80,000 people per year until there are millions living on Mars. They have been working steadily towards that goal for 15 years. They are extremely busy and making the most rapid progress in spaceflight since the beginning of spaceflight itself. Take a step back and realize how much SpaceX is actually doing. If this isn't enough "do" for you, then I think nothing in the world or anywhere in the solar system would satisfy whatever you're looking for.
Do you use any tools to make the assertions on the resulting DOM simpler?

What about any components that maintain internal state; do you just step them through the states and assert the DOM state as well?
Not a guide. An index of brain-related articles.
> she has the right to stay and bring the company down in flames if that's what she chooses to do

Not really. Even if she owns it she has a fiduciary responsibility to her other shareholders as an officer of the company.

Unfortunately it is quite possible that Holmes staying put IS in the best interest of all other shareholders given how little else Theranos seems to have going for it...
For me the first part that you agree with as well is the kicker. Slack has started eating the world, but the fact that it has only partially succeeded makes it feel way more painful. My gaming groups are on slack. Various (discontinuous) work groups are on slack. Various open source groups are on slack. But not _everything_; meaning either I have to have yet another desktop app (call me a curmudgeon but I really like to minimize how many moving parts I have going) or constantly click through alert emails to the online slack tabs. As you say there's a use case for that, but when I find it eating use cases that I otherwise would have perfectly functional, lower friction tooling for (email alerts, dl's, etc) I start to get frustrated; especially when it makes it far harder to organize the content between multiple distinct slacks + other silod communication channels when compared to e.g. mail filters.
Hey guys, at the company I currently work (startup 150+ employees) where at a stage in which aligning different aspects of our (newly built) processes and strategies is crucial.

Asking questions to whole team (or a group in particular) is s need that happens on a daily basis and is most often met by a mass email that gets sent around. These often usually come with a Survey Monkey/Type form/Google Form/etc link in it.

I've built this because I've found that asking (in private message) through Slack leads to considerably higher response rates (+50%) and for the responder, there's no new UI to learn every time a new question comes in.

Hope you like it. Looking forward to get feedback!
>"They wanted it all; they didn't want to pay for it."

The above happened on almost every project I have worked for over the years.

Q: "Can we take feature x out of the plan?"

A: "We can't release the product/project without it"

Q: "Can we then add 2 more months to the release?"

A: "Absolutely impossible, the client will not accept it"

You are correct, the reason is severe (and systemic) lack of communication:

Product-roadmap planning either does not involve technical personnel at all, or at least not until the very last minute, when you are brought in to essentially rubber-stamp the plan. Saying "no" takes a lot of courage at this stage, you are seen as incapable/negative.

The underlying problem here is that we are seen as mere technicians/workers, not planners or strategists (we are partially to be blamed for this, but that's a separate topic).
The terrible situation is the implicit "IT Guy" having to do actual sysadmin work and being interrupted with the "hey fix this printer".

Also, being asked to fix a printer is pretty frustrating, because at best someone either is using past knowledge, or using google to diagnose, which is something pretty much any person could do.
Agree 100%. However if you are using component state you will need to test how interactions impact rendering output on the next render pass. I wouldn't consider that implementation detail since you are only asserting against render output.

In the case of testing instance methods, this is definitely a special edge-case scenario, but actually one of the main reasons I put this together. They inevitably happen, but are rare and I tend to forget how to set those tests up.

To give you an idea of how we use this: our application is a "website designer" where the preview is rendered inside an iframe. We use a react component to push CSS changes directly into the iframe via document.styleSheets. Using instance method testing allows us to test the main output results of this functionality without having to render real iframes pointing to external server in our tests.
With charging phones? Nothing.

But the reality is that one person is sat camped out with a chair in front of the thing for the entire day. Nobody else can use it. I've seen folks get in fights over these things already.

I spent part of my life homeless. I still see a major problem with how these things are being used right now. We shouldn't be encouraging people to be out on the street all day -- it doesn't solve anything.