skysight-inc/HackerNews huggingface dataset:
I am not a full time dev, but do write little scripts and web apps to help out my team members. I have a server that I have to support for this (no external support) and I actually like it that way.
That's a really bad idea, glReadPixels is usually a full pipeline flush + read back and stall which kills perf for all sorts of reasons.
True, but when you have an awful lot of layers, you can play some silly buggers with it. Even if you botch a layer, it won't neccesarily ruin the whole thing, since the interference betwen the sets of layers also act as filters. I haven't worked on these sorts of stacks, personally, but I'd be surprised if the whole stack dies because one layer was a bit screwed up (I'd expect a degredation in the efficiency, but not necessarily a total reversal - now ask me what happens if your goal is to tune to neutral color and you make a slight error and then I'll flip sides and say "rainbow").

What I'd really expect is that if you make one layer slightly larger, your process almost certainly making all the repititions of that layer larger too, and now yeah, your bulk properties are just hosed.
So, I was definitely once one of those people arguing for lax airline security on the basis that fear of terrorism is irrational and resources would be better spent on actual, mundane, every-day threats (like automobile safety).

But I think you're actually right about this; my original argument ignored human psychology to an extent that makes it nonsensical. Actual threats are important, but so are perceived threats. It's not entirely irrational to protect against the things we fear the most, even if those aren't actually the most likely things to kill us.

This also comes up a lot in arguments about city living. I know a lot of people for whom urban living is frightening to an extent that is not supportable by crime statistics. But so what? If they were to move to the city, they'd be constantly afraid. That matters. Rational or not, their perception greatly impacts their quality of life. And if you want those people to move back from the suburbs, then you need to address their concerns.

There is a reason, after all, that airplanes are such an attractive target for those who'd like to cause terror.
To be fair, my last employer (aerospace manuf.) ran an incredibly dated and ancient OS with pretty decent results. It was simple, to the point, ugly as hell but got the job done without needing constant updates etc etc. Also we never had a problem with malware (because who writes malware for a 30 year old OS?)

I understand this article mentions many different sectors and functions for antiquated systems but sometimes an update simply isn't needed.
It very much depends on the auxlang. Most of them do try to make things easy, but auxlang creators tend to be a little more linguistically naïve than other artificial language creators, so they end up using themselves as the benchmark. Esperanto is a notorious example of this, where you have initial consonant clusters like 'sc' /st͡s/ and internal consonant clusters like 'tĉ' /tt͡ʃ/. Zamenhof essentially took a simplified version of the Polish consonant inventory and applied it Esperanto.

There are plenty of studies of consonant and vowel frequencies in human languages. We know, for instance, that [p] [t] [k] are found in virtually all languages, that most languages have at least one liquid, one nasal consonant (which can be realised as [n], [m] or [ŋ] depending the position of the consonant that follows it is). Most languages also have [ʔ], but you never notice it as most only allow it initially and exclude it when spelling: if you were to choose any word in English beginning with a vowel in isolation, you will almost certainly start it with a glottal stop.

As far as vowels go, the classical five-vowel system is very prevalent: some approximation of it is used in lots of languages, and there are very few languages that use simpler systems, though Modern Standard Arabic, with its three-vowel system ([a], [i], [u]) is a widely-spoken counterexample. If you wanted to include more consonant clusters, you could add schwa as a epithetic vowel: in our hypothetical language, the word _plum_ could be phonemically /plum/, but phonetically [pəlum] for speakers who have difficulty with that initial consonant cluster.

Still, knowing what sounds people can pronounce is only half the battle: a good IAL would also have well designed _phonotactics_. That's a bit of a rabbit hole though!
Hacker 2016 To-Do List: Botnet All the Things
Contrails also have a net cooling effect on climate: https://www.researchgate.net/publication/11218772_Climatolog... such that global dimming counteracts the effects of global warming. Less planes, less contrails accelerated global warming.
The major investors (Bessemer, USV, Fidelity) amount to 48.2%. Bear in mind that other founders and employees will also hold equity, and that Jeff Lawson already cashed out a big chunk of equity (detailed in the doc).

Given that Twilio has raised a lot of money across a number of rounds (six listed in the document) as a loss making company, none of this seems that strange to me.
​Who Invented the Electric Guitar?
Hasn't he used uncredited ghosts in the past?
Security Theatre was Job #1 behind the invention of the TSA.

A close second job was building a behemoth Government Agency to funnel money, direct contracts (to supporters), and lastly supply jobs for those people who were probably otherwise more difficult to employ.

Now I don't know about you, but I would call that a win-win situation.
Bonus: Probably much cheaper to do.

Concern: Real randomness gives you streaks, which may cause unanticipated clogs and delays in the process. On the other hand, an "smoothed" system means attackers would try to slip in right after a "random" check occurs for an innocent.
> The nice thing about git is that your commits can be garbage.

That's a dangerous practice. When you first commit the changes, you have all the necessary context, and hopefully flow hasn't been interrupted. If you rebase hours, days, maybe weeks later, then that context is completely lost---it's just like trying to get back into a project that amount of time later.

The reason the detail you'd put into your commits is so useful is because you have a perspective that others won't; if you return to it later, you'll be reading the diff and suffering just like others, albeit with a bit more knowledge.
I find this interesting, as I recently completed a book (1).

My co-author (much younger and smarter than me) mentioned while we were in the middle of writing it that he'd 'never read a computer science book'.

I had to reflect on how much had changed in 15 years of software development. When I started I was using Dogpile to search for 'documents' on the 'net (which had an apostrophe then) while balancing a 'learn C++ in 21 days' book on my knee.

So 'coding without books' (and coding well) is already more than possible.

1) https://www.manning.com/books/docker-in-practice, since you ask.
The amount of people who moved for tax reasons is far lower than I would've expected. Only 2.2%
Yeah true that Google, Apple, FB have NY offices, but all of these companies are very HQ focused. Especially Apple and Alphabet, with most of Alphabet's based are based in SV (Calico, Verily, YouTube etc.). Apple is also notoriously Cupertino centric.
Lenovo: Motorola acquisition 'did not meet expectations'
From a 1986 Fortune article: "With pretax profits running as high as 34% of revenues, Microsoft needed no outside money to expand."

[1] http://fortune.com/2011/03/13/inside-the-deal-that-made-bill...
But 10% of the population has always been in the bottom 10%. How can you use a constant timeseries to explain a time varying one?

Also, even assuming relative inequality is what matters, why does it matter only within national boundaries? If this were true, couldn't we re-draw boundaries to fix the problem? I.e., we could make NYC into a Luxembourg-like rich nation, West Virginia into an Italy-like poor nation, and solve everything?
> history is basically unusable.

I can see how, in the second workflow (feature branch workflow), this can become a problem. If the history looks like this

---------
/ \
--A E--
\ /
B---C---D

then we can sort of guess that commit B started a feature branch and E is the merge commit that merged the feature back to master. And commits B, C and D can be "unusable" intermediate work, maybe even uncompilable. But if nobody ever works directly on master, all development is done in the feature branches, then when E has two parents, A and D, and A is a merge commit and D is not, then you know that A is in the master branch and D was in a finished feature branch.

This gets more complicated in the third (gitflow) workflow, when all feature branches also have their own "feature master" branch and developer branches. Then all commits in the several "feature master" braches are merge commits, and then all the commits in the main master are merges from those merge commits. Then a commit in the master branch has only merge commits as its parents, so how can you tell which one of the parents is the previous commit in the master, and which one in a closed, finished feature branch?

If you could tell, then when bisecting or whatever, you could first just go back in history in the master, and only when needed, take a look at more details in the feature branch commits which contributed to the single merge commit in the master.

All this is solved by the named branches in Mercurial, where a commit carries forever a nametag, to which branch in originally belonged. You can add informal extra info in git commits in commit messages, so with some extra tooling you could make the history in these branching models usable again.

Then again, in the fourth workflow (forking workflow) when developers pull directly from each other, and there is no central repo, permanently tagging a commit with a branch name would make no sense. And this is the use case with Linux kernel work, for which git was originally designed.
where do you see that? I don't know how to read those things
Customers Facing up to $1M Lawsuits Over Bad Online Reviews (One star on Yelp)
It's fixed. Sorry we wrote the code for this site drunk in a night.
I flew on about a dozen flights (including 4 flights in europe) over a 6 month period before TSA discovered that I had a prohibited multitool with a 1.5" blade. I asked him if I could use the bigger multitool in his discard bin to snap the blade off the tool and he said that no one is allowed to touch anything in the discard bin, and even if I did, I'd have to go out of the secure area and be completely re-screened. So I let him take my $20 tool and drop it in the bin with the rest of the tools.

If I really wanted to threaten someone, I think the metal pen in my bag would be more of a threat than a tiny multi-tool knife that would probably fold back and cut my own finger if I tried to use it as a weapon.
> On a private branch, people should commit whenever they want on any whim of a reason.

The concern was when that private branch isn't cleaned up before it is make public; it then becomes an issue.

Though see my reply to developer2 (sibling of your post) for rationale against garbage commits to begin with.
I cannot disagree with your attitude more. This company is saying they have an existing threat to their ongoing operations that _will_ be fatal, that they are unsure will ever be solved. This is fundamentally different than saying ad blockers could impact Google's business.

In a way, their honesty is unexceptional because they are required by law to be honest about their risks. But the level of risk is not usual.
Looks like a great release. Controlled unwinding looks very interesting. #GreatJobRustTeam
Apple should do many things, but doesn't do it
Tumblr: Babby's First Hack Day: Fast Queue
What I find funny about this example is that at first I thought the "it happened" argument was going to be used in defense of the person doing the stabbing. Which, of course, it could.
> Sure it's still safer; that's not the point.

That's entirely the point.
"frequently restarts for no apparent reason,"

Doesn't happen to me. Not argueing one way or another, just stating a different experience.

I once had a Sony Xperia, bought the same model as my then-girlfriend, from the same company, probably the same batch. She had often spontaneous reboots, but I never had. She complained quite much about that and would never buy a Sony smartphone again.
He was already paid out amounting to $9,310,100 prior to the IPO. Consider that insurance just in case an IPO never happened.
A fistful of wires
Airport screening made 70,000 miss American Airlines flights this year
There's a lot there not to like:

Revenue: $166,919,000
Net Loss: $38,896,000

So they're still not profitable. This is surprising, since they don't have any big capital investments. They're not doing anything that takes a lot of R&D. The thing runs on Amazon AWS. They've been operating for years and should be profitable by now. Yes, they're growing fast, but the costs don't rise in advance of the growth. You don't have to prepay Amazon for AWS.

"Each share of Class A common stock is entitled to one vote. Each share of Class B common stock is entitled to 10 votes and is convertible at any time into one share of Class A common stock."

So the public stockholders have no power. The insiders can't be fired. Google and Facebook did that, but they were big successes before the IPO. It's unusual to try to pull that off when you're unprofitable. The NYSE, on which they want to list, didn't allow multiple classes of stock until 1986.

WhatsApp is only 15% of their revenue, so that's not a big problem.

Twilio's big thing is telephony integration. They have a SS7 gateway and can integrate Internet and telephony. If Amazon or Google offered that, Twilio would have a big problem. Google has Google Voice and Google Hangouts, but doesn't offer telephony integration via a usable API. Yet.

This IPO is an exit for their VCs. They were all the way up to a series E round, and since they grew fast by losing money, the early investors had to pour in a lot of cash.
In a democracy, the voters, via their representatives, decide what's legal for the government to do. So if the government does things that are illegal and hidden, then I'd say anyone has the authority to reveal it. That authority was granted by the voters who made the activity illegal.

If the government's activity is legal, on the other hand, then it's harder to make a case. A whistleblower may still decide to reveal it as a matter of civil disobedience, but at that point he's trying to change the minds of the voters, rather than enforce their expressed wishes. He should expect more legal jeopardy, though if he succeeds in changing people's minds, then a pardon would be appropriate.

If our legal system doesn't make a distinction between revealing legal and illegal secrets, then I'd say our system is inconsistent.
Any chance of tracking Terminal.app?
Legit question: Let's say that we'd do what you suggest and we'd allow them to drive, unsupervised, random people back and forth.

Let's say that something bad happens and they assault a client or whatever.

Client finds out they have priors. Asks you if you think you made a wise choise, or if you'd change something in your hiring process.

What would your answer be?
What I find really funny is the obvious shills who wrote such generic five star reviews without commenting on the item, the picture, or the product itself.

No wait ... now that I think about it I'm more saddened that even our spammy Mechanical Turks who might have been paid a penny for each review are now being replaced with bots.
Not to mention, having type erasure made them backwards compatible with non-generic implementations. I don't think it would have been acceptable to break old Java code or introduce an entirely new collections library like .Net did.
I hop into Rust beginners from time to time, but it's usually pretty empty so a bit hard to get an answer. I'm very likely explaining the problem incorrectly, so let me give you an example: https://gist.github.com/anonymous/3d72907031ce18d002364e756f...

As you can expect, line 13 is trying to borrow a value that does not live long enough for `req`. Unfortunately, hyper::client::Client's req.body() requires a &str it seems. Somehow i need to pass it a &str (which i would normally do via &String).

Do i need to move s:String out of the block? Do i need to specify a lifetime? These are the sort of "What do i even search for!?" moments i run into heh. Granted, less so these days.. thankfully.

Note that `&mut Some(ref c)` looks pretty terrible, i'm experimenting with an API i'm writing.
I think it's possible to draw a line between angel/VC with sane valuations and the "unicorn" phenomenon.

The former does not seem to be in a bubble per se, though we have seen a cool down. A "hot" market is not a "bubble" and a cool down is not a "crash." Bubbles are violent and insane and that's not what we've seen in seed/series A.

The latter may well be a bubble.

What I'm hearing about right now is that it's getting a lot harder to raise money in later stages if you don't have great revenue numbers and real revenue growth. Earlier stages have cooled a bit but not catastrophically.
Do I need to use a CSPRNG when creating salts for user accounts?
Could you? Tons and tons of companies are forced into using outdated versions (for tons of reasons) where point release updates are still possible.

I'm sure it's a lot of work, but a lot of your core and original users would appreciate it. Not implementing something as useful as that just has a "we got 'em, no need to do anything else for them" vibe.
Show HN: This Is How We Made a 7'5“ Tall Version of Mega PocketC.H.I.P
In Las Vegas this weekend, coming back we did not have to remove our shoes or laptops, just toss metal items in our bags and walk through the metal detector.

I was through security in less than a minute.

I suppose a bunch of hungover people aren't a convincing security threat.
> but I so wish he said "Look Son, I don't know it's water, so I'm asking you to dispose of it"

I'm sure he did that when he first started, but being berated on a daily basis ("Are you calling me a liar?!") probably made him decide that his current method is the path of least resistance.
Being a man or a woman is more than just your biological makeup. It makes a very significant difference in what behavior people expect from you and how they interpret what you do. In other words, there's very much a sense in which men are those who get seen and treated as men.

And personally, I see no reason why having male genitals is necessary for getting seen and treated as a man. If you behave like you want to get seen and treated as a man, I'll see and treat you like a man. The only people who have a remote interest in the actual biological makeup underlying that behavior are people who are romantically involved or interested. Oh, and medical personnel.
Right, but the reason for the TSA's existence isn't blowing planes out of the skies, but using them to attack buildings. Hence it became a national security matter. However, the solution to that particular problem was the reinforced cockpit doors.

As for the exploding aircraft, as you seem to imply, airports and airlines have a vested interest in preventing that from happening. But unlike the TSA, they also have an interest in efficiency and happy travelers. And they're spending customer money rather than federal tax dollars.

So I'm for no government security, if that's not what the GP meant. But I doubt the airlines really want that, since it opens them up for liability if something were to happen.
As others have mentioned, most of the videos are served as "gifv" videos, which are much more bandwidth conscious than actual gifs.

It's worth highlighting that Gfycat is managing to operate as a short gif/video hosting service without turning awful, though I obviously don't know what their financials look like.

Gfycat does have a homepage of popular gifs, but they've never shown them to me unless I wanted to see them. The viewer page is just the viewer.
I get 200+ visitors and 1000+ pageviews each day and analytics shows an upward trend.
Real talk on finding a Co-Founder – and why it could make or break your biz
Wow nice. This is kind of random, but can I ask how you got/licensed the photos of goats?
I'd like to test the bluetooth functionality of the ESP32 to see power consumption of that vs wifi. My requirement will be cell phones connecting to this mesh network. Data rates aren't a concern for the next project. The mesh nodes should connect to each other. And on everyone's phone, it should look like one wireless network.
I've found that the most effective projects to try disconnected are often the most difficult, in terms of fundamental CS needed. You don't want to do something like a mobile app or realtime Node.js SPA, where the majority of the work is in looking up API calls and debugging why a third-party framework isn't working. That is, unless you really know the technology well...I wrote much of the code for a startup a year or so ago on Caltrain, because it was Django and was like the 4th or 5th Django app I'd written, and didn't really stretch my comfort zone much (technically, at least; the social challenges were new and difficult).

Instead, things like compilers, complex algorithms, data formats, data mining, etc. are good candidates for offline coding. Most of the knowledge for them exists in your head, and the ratio of thinking time vs. reading time is much greater. In the case of data mining & machine learning, there's also a long iterative process that involves looking at your data, coming up with insights, implementing your insights, and evaluating how well it improves the algorithm. If your test data fits on a laptop (not all interesting data does), it's a good candidate for offline development.
Said much more clearly than I could:

http://stackoverflow.com/questions/20918650/what-are-the-ben...
>I'm not blaming react, everything else in the javascript space is just as bad right now. There's at least 4 different ways of loading modules (UMD, AMD, commonJS, es (babel) modules), 2 of which (require(), import .. from) are used within this example.

Personally, I got so frustrated with ever-increasing complexity of tools and growing networks of dependencies that whenever I can I try to package my JS code in self-contained modules/files that depend on nothing -- not even on one another. Needless to say, it's not an approach that's very popular, but it works remarkably well for websites of moderate complexity. One thing I'm sure of: using those modules feels far more satisfying than using a framework.
Wanted: Better Defenses of Peter Thiel
That claim is made but, speaking anecdotally as someone who has been traveling for a long time, I don't think so.

Families going on vacation usually have checked luggage anyway (because they have a lot more stuff than they could possibly carry on) while business travelers, who would typically expense any fees, hate to check luggage because of the extra time.

>perception that checked bags are mishandled, lost, or slow down your travel time

All accurate perceptions, especially the latter two. I'd add that having luggage checked also makes it much harder to do re-routings or flight changes when there are problems.

[EDIT: I'd also add that many (most?) business travelers already have fee waivers on checked luggage for various reasons, but they still rarely check luggage.]

What I do wish able-bodied travelers would dispense with is roll-aboards which IMO are responsible for a lot of overhead space issues.
That's interesting, how does she go from making small talk with a Korean person to determining that they're a spy?