skysight-inc/HackerNews huggingface dataset:
Yes, you can buy your way into the US in several ways:

http://cis.org/north/aliens-guide-buying-american-visa-three...

Or you can pursue a green card on the basis of extraordinary ability:

http://www.bbcamerica.com/mind-the-gap/2012/09/13/how-to-get...

Alternatively, there's the slow, gradual process. If you were making decent money, you can also hire professionals to attempt to expedite your process as much as possible.
Pretty cool. Interestingly, it seems to me like it's getting the vibrant colors just slightly off. Like the red from the dress should be brighter, and the yellow from the car should be a bright yellow instead of a mustard color. Is my brain just perceiving that the text on the car is bright yellow, while the actual color in the image is much darker?
Sure but most of the opposition was from the Democrats. It just irks me that libertarians think they invented civil liberties when it has traditionally been a liberal issue, for example with the ACLU. War, police powers, law and order, three strikes, the drug war are not "communist" ideas, capitalist conservatives have always been the biggest proponents of these idea.
This article is a bit misleading. Not all ranges are as badly handled as the one they mention, and many many people just shoot outside.

In addition, the major illustration is pretty much false. Almost all bullets are fully jacketed and not just partially as indicated. There isn't going to be lead from the bullet anywhere except at the backstop at the end of the range. There is a bit of lead in the primer (which weirdly the article fails to mention) but it isn't nearly as much.

From the third article -"At a shooting club in Vancouver, Wash., 20 youngsters tested positive for lead overexposure. ‘We would get lead on our hands and eat finger food,’ one teenager recalls."

Education is key here. I'm not trying to minimize potential risks, but they aren't nearly what this article is projecting. Yes, don't lick your fingers after shooting. At every range I've ever been to, food and drink are prohibited. Wash your hands people.

also from the third article - "While lead poisoning among casual shooters is rare, the risk increases the more they shoot, particularly if it’s in poorly ventilated and maintained ranges."

Happy to agree. only use well maintained and well ventilated ranges, or just shoot outside like most people.

The risk is real, but it's really minimal with a little bit of common sense. Focus on educating people of the actual risks rather than scare mongering like this article.
You created a burn account just to complain about this?

As you know, generics won't appear before 2.0, if ever. It's fine if that's a nonstarter for you. Perhaps you'll like Rust instead. It needs a big community too.
>the whole world came knocking on his door

That's... a bit of a stretch. How big do you think the market for bingo card generators is?
https://github.com/golang/mobile
IMHO, that grade maybe was appropriate.

I applaud you for doing that, and I personally would have gotten a lot out of your talk. Good, clear, verbal communication is fantastic! Good on you for attempting it. I have similar leanings and skills.

The hard truth I've learned is not everyone can take in it that form. If you have any sort of an audience, the potential for those people will be actualized, and you lose on overall communication fidelity for those people without a visual reference. Secondly, there are people who really need to vocalize to learn, or do something, or experience it in tactile ways, etc... You will find these people asking questions, seeking to be a part of the dialog, taking notes, making motions, drawing, closing their eyes...

Multi-sensory communication is high fidelity as well as broadband. Think of the different axis possible. We often do this with young people, giving a talk, letting them speak, having them touch it, or do it, take notes, etc...

Adults work the same way, though their greater body of experience generally means they are well equipped to handle visual / aural presentations fairly well. You can get the majority of them with a dual style.

This takes some extra work, and might not be in your personal sweet spot, but it's generally worth doing.

YMMV, but 20+ years of communicating to individuals, small groups and crowds composed of amateurs, business people and techies speaking here.
This is most definitely piece of fearmongering journalism by a newspaper notorious for promoting an anti civil liberty pro federal agenda... But, it does raise a few good points. Range owners _should_ be aware of lead dangers to employees and follow safety practices. I hope it does raise awareness, but certainly there's no reason to go run for the hills.

What I find most interesting however, is this flies in the face of another anti civil liberty agenda promoted by the BATF. They recently attempted to _ban_ lead free and reduced lead ammunition (aka "green ammo", m885, or "green tip") under the guise it was "armor piercing" (to soft body armor). ...which is laughable because soft body armor can't even hold up to a knife attack.

Sadly, a lot of older indoor ranges are made with the wrong kinds of steel and cannot be certified to have green ammo shot inside them without damage to the structure.
Much agreed. Call me a masochist, but I prefer extra typing if it means readability, to me. And while subjective, retyping Point{} is much clearer to me than {}. It just looks...wrong.
You can do all these things.

Android is very open, if it wasn't how could other companies take the OS and make their own very successful clones. Such as Amazon or any of the Chinese variants. No one has done that with Windows.
Except it turns out that:

a) The boss has changed his mind and now we're building a pool, so we need to cut off all this f* rebar sticking out. More time to remove it, plus the cost of adding it in the first place.
b) Its software, so adding the rebar is as easy as F6-refactor.

You are scaring the children. Stop it with the FUD.
Lead is just so awful - it lowers IQ of children by a very large amount, even in low doses. Why not just ban the stuff in bullets? I don't see the problem with outlawing it. These are clear, super negative externalities. Alternatives exists. Enforcing proper handling of lead bullets seems much more difficult than just banning them.
>implication...the alternative to YAGNI is somehow diving in and developing everything up-front without reference to...

I don't think that's the dichotomy that's being presented, nor do I think it would matter if it was. That is, one doesn't have to go to that extreme to incur the downside of a "non-YAGNI" approach. It's very easy to have contemplation of future features negatively impact a project.

>one reasonable guideline for modular design and separation of concerns is that each module should roughly correspond to a unit of change, in the sense that a change in requirements would ideally affect a single module without interfering elsewhere in the system

Wow. I think that's exceedingly difficult to pull off and trying to design in such a way itself seems tremendously burdensome to the project out of the gate. It also seems that it would tightly couple the code with business requirements in such a way that change actually guarantees maximum impact to the code. Because, rules don't change in a neat, stovepiped way. So, when they change, cross-cut, overlap, etc., then all of your modularization goes right out of the window.

So, interestingly, given that approach, it probably would make it more important to anticipate future changes, because your code will be less insulated from those changes!

>modelling bank accounts

Thanks for bringing this down from the abstract.

But, this is where generally good design can help. If you have your debit and credit functionality neatly encapsulated, plus a good overall model for chaining/demarcating transactions within your app, etc., then you don't need to rip apart your entire model to support transfers. In fact, I'd say you have a good head start.
In general I just use npm... I don't use bower or jspm... for that matter, I don't think browserify where needed is so bad.. there's also options with babeljs, which I'm liking more and more.

A base set of packages, for your external functionality, your core (shared functionality) and the rest makes a lot of sense, and isn't that hard to do. In the end it's pretty easy to reason about, and with sourcemaps and better build tools it's easy to use. Though having to have a watcher or build process when JS changes takes some getting used to... if you're used to compiling server code, it really isn't bad...
The analysis and tracing tools look really wonderful. Have those been in the works / maturing for awhile, or is that all new tooling for 1.5?
DVDFab iFoneRestore-World's Best iPhone/iPad/iPod Data Recovery Solution
So maybe the best CMS in the world saves you 10% in costs over an averagely competent CMS.

It's not really a material difference in terms of sustainability.

You are correct in stating that established media companies are struggling because of their cost structures. But those cost structures are mostly salaries (and capital investments in buildings etc) rather than something that a magic CMS can fix.

Put it like this: when a "new media journalist" uses their mobile phone to take a picture for their story (instead of a staff photographer) that has made a bigger difference in terms of cost structure than the worlds-best CMS can make.
Breach Exposes I.R.S. Tax Returns
A lot of the questions are pretty terrible, it forces one to cram their opinions into 2/3/4 choices. The moral quandries with "this is wrong / this is right" are the worst
If anyone here is from the google fonts website, theres a typo in this document:

"Bold 8.5/12pt
Roboto supports 16 weights as well as advanced typographic features such as smallc aps"
Even though there are just 6.5 million people in this industry, there is a lot of interest in technology news from young people and non-tech people of all ages.
Have we reached the crest of the post 2008 startup cycle?
The big ones like Facebook, twitter and many others that start just before the crash or after the crash cashed out. Many companies that started with the premise of a sharing economy like Uber are probably not at their peak but close to it. Sqaure and others have peaked and plateaued(?). There are a lot of startups in the ad space and the competition is fierce. I am not sure if there is consolidation there or not, I don't follow that space.

To me it feels like we are at or very close to the peak. The question is part to validate the hypothesis and part to gain some knowledge if I am wrong.
This is a point that needs to be beaten into our collective heads to get past the WWE-style "competition" fostered by the two parties, and start talking about the ideas.

Unfortunately, every time we get close to that realization, the parties bring out "The next president will appoint several Supreme Court Justices that will have a decades-long impact" knowing that we'll swallow the lesser of two evils. I regret to say that worked to make me vote major-party the one time (Kerry, ick), but we have to think even longer-term to break out of this two-party cycle.
The mythical expert programmer...

Everyone has a cognitive limit on what they can keep track of/in working memory. Once your codebase exceeds that limit (in # of files, lines of codes, types, interfaces, etc.) you lose productivity. 10k lines of python is a lot harder to grasp than 10k lines of go.

And that's not even considering the ramp up time for someone new to the code to jump in, which is even worse in most dynamic language codebases.
Meet 'Tox': Ransomware for the Rest of Us
Why Rust? It doesn't really compete with Go anywhere. Haskell is a much stronger player in the space of high-level, garbage-collected languages. The only thing Rust and Haskell really have in common is not willfully ignoring the last 50 years of programming language design research.
A Hackers Guide to a Successful Launch
Ext4 encryption
In particular, you've gotta have DLLs if you want to deploy on Android.
Stack Exchange Data Science Beta Site
Training Young Doctors: The Current Crisis
Tech Support Scammers Go for Pornographic Shocker
Hi, I think there's actually quite a lot of differences between Atomic and InVision, so I'll focus on what I think the main reasons are that you might try Atomic if you're already familiar with InVision...

Atomic has drawing tools that let you actually design/layout interfaces in the app. You can also import flat images from other apps (like PS or Sketch) for prototyping if you want to. Atomic also lets you design complex and unique animated transitions, not just the standard ones on mobile.

Atomic has some other special features too: like being able to style elements with raw CSS, visually rewind through your history and make branches/variations from any point, and team collaboration that lets multiple team members work on the same set of designs, even simultaneously.

So lots of reasons to give it a try I think. I hope you give it a go and please do let us know what you think.
The Visitors – Revelations of Sound and Symbol
I find this particular argument rather frustrating.

"Dynamic languages are fine as long as you don't do stupid things." One of the huge benefits of static types is that you can extricate yourself from those situations because the compiler can help guide you through large scale refactorings safely.

It's not even that the team is bad or that the authors of the code were ignorant - it may just be that the software has evolved to where the initial code no longer fits the problem exactly.

"Don't be stupid" is completely unactionable advice.
There's the fact that dom changes related to a given set of events can be made as part of the same changes to the DOM as a whole... which can reduce parts of the render time overall.

However, depending on your needs, a stream of changes may behave differently in different use cases... to me React simply represents in my mind a better way to manage components and rendering logic, combined with something like flux for data and event flows.
European courts declared APIs to be uncopyrightable.
> it's not a problem as long as you don't do stupid stuff

Easier said than done on large codebases with wide variety of contributors.
Such failures are more often because of bad developers than anything else. It's not really fair to blame a single person on a big project with lots of people on it.
If you are talking about company's internal developer facing documentations, they are not going to be on internet.

Some of the best product documentations there are:

https://stripe.com/docs/api

http://www.twilio.com/docs

https://docs.djangoproject.com

https://developers.google.com/maps/documentation/

http://docs.oracle.com/javase/7/docs/api/

https://parse.com/docs/ios/guide
You're right about that - what I really mean is they have an opportunity larger than any other VR company there to put it in the hands of the consumer; in that sense they are creating a channel to an industry that was previously only for the hobbyist or geek.
Children were evacuated to live with volunteer homestay families in the countryside. From what I was taught at school, it was a case of suitcase, gas mask and name tag, then get on the train with all the other kids. This is how The Lion, the Witch and the Wardrobe (and many other books/films) starts.

For those that stayed behind there was a post-war pride that they stuck it through and didn't give in, but it must have been unimaginable even with the bomb shelters and London Underground. Again, this is what I've been taught from my elders so not first-hand experience.

EDIT: I should add that I realise it was not just Britain for whom things were unimaginable.

EDIT 2: Another factor that must have had a big effect on Londoners was that the king and queen stayed at Buckingham Palace (which was hit a few times) during the war.
FIFA Officials Arrested on Corruption Charges; Face Extradition to U.S
I suspect he used something slow to emulate sets in Perl 5. I get:

$ time python3 send.py
9567 + 1085 = 10652

real	0m16.388s
user	0m16.299s
sys	0m0.049s

$ time perl send.pl
9567 + 1085 = 10652

real	0m16.838s
user	0m16.732s
sys	0m0.063s

With:

use strict;
use warnings;

my %digits = map { $_ => 1 } ( 0 .. 9 );

sub choose ($&) {
my ( $set, $sub ) = @_;
map { $sub->($_) } grep { $set->{$_} } keys %$set;
}

sub guard { $_[1]->() if $_[0] }

choose { %digits, map { $_ => 0 } ( 0 ) }, sub { my $s = $_[0];
choose { %digits, map { $_ => 0 } ( $s ) }, sub { my $e = $_[0];
choose { %digits, map { $_ => 0 } ( $s, $e ) }, sub { my $n = $_[0];
choose { %digits, map { $_ => 0 } ( $s, $e, $n ) }, sub { my $d = $_[0];
choose { %digits, map { $_ => 0 } ( 0, $s, $e, $n, $d ) }, sub { my $m = $_[0];
choose { %digits, map { $_ => 0 } ( $s, $e, $n, $d, $m ) }, sub { my $o = $_[0];
choose { %digits, map { $_ => 0 } ( $s, $e, $n, $d, $m, $o ) }, sub { my $r = $_[0];
choose { %digits, map { $_ => 0 } ( $s, $e, $n, $d, $m, $o, $r ) }, sub { my $y = $_[0];
my $send = $s . $e . $n . $d;
my $more = $m . $o . $r . $e;
my $money = $m . $o . $n . $e . $y;
guard( ($send + $more == $money), sub {
printf("%d + %d = %d\n", $send, $more, $money);
});
}}}}}}}};
Doesn't it? Why do people seem to compare them all the time...
agree on all points. Even if lead isn't in the mix, its incredibly stupid to lick your fingers after firing a weapon. you get covered with ridiculous amounts of gun powder residue, oils, and god knows what else. its also worth noting that copper isn't exactly healthy in your body either.

One last thing, the map is almost comical. The 'red' on half of those states is due to the fact that those states don't have many in door shooting ranges. I'm pretty sure Montana has like.... ZERO.
There is almost nothing that needs to be done to be safe. Wash your hands and clothes. Don't eat or drink while shooting. This just isn't that hard.

There is a tiny contingent that needs to be more aware, and that is the business owners and employees. There's just no reason to massively increase the cost when very simple things like washing your hands fixes the tiny chance of an issue. Don't lick your fingers when they have lead on them.

EDIT: Also the politics in this country disagree with your hypothesis. It would be so much harder to ban lead bullets than for people to wash their hands after they shoot.
They seem to say you may choose to continue specifying it, as you prefer (?)
I feel about the same way the author does.

I've written one largish (large for a 3 man team) production codebase in go (as well as numerous side projects). At first I loved it--it was simple, and I really loved the fact that it compiles to a native binary. I also really liked gofmt. But looking back through what the code has evolved into 2 years later, a huge portion of it is essentially copy and paste code to work around the lack of generics. Another large portion is copy and paste error handling.

I was essentially using go to fill several niches. I wanted a higher level language to handle business logic, but I also needed to work with serial ports, and I wanted something that would run fast with a small memory footprint.

Go seemed to fit the bill perfectly, but eventually go started to feel like jack of all trades master of non type of thing. Since I had to eventually rewrite my serial port code in C anyway, I think I would have been better choosing a language with more modern features for the rest of the project.

Maybe it's because I've been using F# (and C# to a lesser extent) lately, but I just don't think I want to go back.
For me it's worse: all I see are constant overheads between trivial prefix-free equivalents...

But then I also love C and hate everything Python with a passion, so go figure.
I don't have the ability to down vote, so I'll just say I don't car about gun ranges or the people who go to them (as reported on HN or elsewhere).
For low latency messaging like this you'd typically want to avoid cross socket data transfers. However, IIRC cacheline snooping across sockets is a bit quicker (Intel QPI at least) than remote dram access so if the lines stay in cache the communication may be under 100ns. Also, depending on access pattern, hardware prefetch may hide some of the latency.
great! perfect!
Why JetBrains needs Kotlin (2011)
This is a nice take on the language; and doesn't descend into the regular lampooning ("lol no generics") that's found on languagey posts. Kudos!

> The attitude of the decision making around the language is unfortunate, and I think Go could really take a page from Rust’s book with respect to its governance model.

(I wrote part of Rust's current governance model and was a part of polishing it up; though I wasn't so involved when Rust initially started using a consensus based model. I've also tried Go, and written about it [1])

... I don't know if this would work out so well. One of Go's strengths (also weaknesses, but it is a strength) is that the language designers can afford to just make hard decisions for everyone. This is where the simplicity comes from, IMO. Rust is complicated because it tries to cater to a wide range of needs. Go makes decisions even if they cut out use cases, and the language stays simple. Both approaches are valid; but IMO switching approaches would make Go lose one of its best plus points.

[1]: http://www.polyglotweekly.com/2015/04/24/thoughts-of-a-rusta...
Openstack is a very good example of a very large python codebase split into smaller projects. But it's still a large codebase. It's still hard to work with different components and the only thing that happens to hold it together are loads and loads of tests and lints which try to come close to what static analysis could provide.
Furthermore, the years they spent where dynamic linking were not allowed incubated the culture -- even though dynamic linking is now allowed, it really will be a special case!
Which Bitcoin Players Matter? [audio]
Best Seed Funds Angel Investor for Indian Startup
I think we should be very conservative with toxins that lower intelligence. At the very least, children should not be allowed in indoor shooting ranges. Were I the Lee Kuan Yew of America, I would still ban lead bullets. Double the cost, seems like a good deal to me.

Our capacity for free choice is implemented in our brains. Libertarians allowing this type of pollution seem pretty self-limiting.

>It would be so much harder to ban lead bullets than for people to wash their hands after they shoot.

Untrue, enforcing the washing of hands would be much harder than banning lead bullets. As there exists alternatives, most people would use them were lead bullets banned. Most people will not change their hand-washing habits. Banning bullets requires inspecting a few manufacturers. Enforcing washing of hands, basically impossible. Educating people to acquire more virtuous habits, ha - a blanket ban is a far easier to implement.
var tokenize = function(input) {
return replace(/\(/g, ' ( ')
.replace(/\)/g, ' ) ')
.trim()
.split(/\s+/);
};

shouldn't it say
return input.replace( ...
It might also make it possible to write Node/PHP/Ruby/Python libraries in Go instead of C++. I've been looking at Rust for that use but the ability to compile Go to a C archive throws in back in the running.
That has generally been true as far as Go packages are concerned, but by default the binaries that Go generates still dynamically link against any C libraries - in particular just about any Go binary will break in the absence of a compatible libc.

I don't know the background on this choice, but I've spoken to a few Go shops that have complained about memory usage when running a bunch of different Go binaries on the same machine, so hopefully this will help there.
Is There Tree Plantation of Main Entrance at Your Home?