skysight-inc/HackerNews huggingface dataset:
My understanding is that when compiled it is nearly as fast as C.

But my feeling on "fast" is generally; how fast does the solution need to be? I have a co-worker who complained that more business logic client-side would slow down our application (it won't, of course). Our application gets on average about 2 requests per second for any given customer. It is by all human perception plenty fast. It doesn't need to be any faster and even being a little slower would go unnoticed. Its all behind a login and isn't intended to be crawled so SEO isn't an issue. Yet once again the ultra-vague benchmark of "fast" gets bandied about needlessly.

But back to Red. From what I've seen its pretty fast but its also early days for the language and they're not focused yet on optimization. Looking at how it is designed I can see how it will be eventually VERY fast once optimized.
Japan’s first VR porn festival shutdown because too many people wanted to come
What are the numbers for being a policeman being shot by a black person? The PC crowd won't like those numbers but its higher than the reverse. We have a police violence problem but it is no where on the scale of the crime rate of one community whose statistics blow everything out of proportion.

We need a culture change. We need politicians not afraid of using the truth. Instead it benefits politicians to exploit the issue for political gain. The real crime is that political manipulation leads to more minorities deaths because they will not act on the real damage and instead go for the sensationalist side.
I would greatly appreciate that list...
> This might be good advice, but it's terrible that we live in a country where this is good advice.

Actually, it would be terrible to live in an environment where it was not good advice.

After all, its good advice if and only if you have some confidence that deadly force will not be used if you cooperate, otherwise, the advice to cooperate when a gun is drawn is bad advice. Otherwise, you should only superficially cooperate while actively looking for an opportunity to overpower or escape (neither of which has a good probability if the attacker has a gun already drawn, but if you don't expect cooperation to be effective protection, you've got no good options.)

Now, it might be terrible live in a place where it is not less likely than it is to be useful advice -- because where we live now, the circumstances in which people might need the advice come up more often than they should. But it would be good advice (with the caveat above) even if it were less frequently needed.
> 2. The toolbar malware, while stupid beyond measure, only applies to the consumer Java installer, which nobody installs anymore due to item #1 above.

Here in Brazil, the program used to submit the income tax forms is written in Java (http://idg.receita.fazenda.gov.br/orientacao/tributaria/decl...). This means that a lot of people need Java on the desktop. I have relatives which have Java installed on their computers solely for that reason (yes, I have disabled the Java plugin on their computers).
I'm sad I'm being downvoted. Our generation needs to learn it can't solve all of its problems with a screen in front of its face all of the time.

A lot of this technology is enslaving us. Piling it higher and deeper isn't the solution.
I agree with you, apologies if I was talking past you instead of with you.
@ghettosoak, Dmitry from RhodeCode team is here! Have you considered https://rhodecode.com ?

RhodeCode CE is free, self-hosted & open-source, with code review tools, user management, and automations. It takes ~5mins to get your own instance up and running. Most of RhodeCode users have secure, behind-the-firewall repositories, where conventional tools are not enough. Seems like a good fit for your case.

I realize you are using Git, however if you collaborate with an external partner or customer, RhodeCode supports Git, Mercurial & SVN repos _simultaneously_ . See, should you decide to migrate from one VCS to another, we got you covered :)

Besides, we have a great engineering culture, hence performance has never been a problem (e.g., we use Elasticsearch for full-text code search). Ask our users on #Slack: https://rhodecode.com/join
> This means that this library will never be subject to arbitrary code execution, leaks of secrets, buffer overruns, double frees, etc.

This sort of blanket statement doesn't fill me with confidence. Rust can only ensure some of those things, and putting this much faith in your (admittedly very cool) tools Seems remarkably cavalier
I'd pretty much call the creator of the Signal protocol an independent verification. It's not like he's employed by Facebook.
Yes, an employee of Washington State. The state government is divided into agencies, who can approach hiring differently (some almost exclusively use contractors, other try to use exclusively employees). Contractor pay is negotiated by each agency with the contracting firm; but employee pay is set all the way from the top (the state legislature).

So, for example, if I say "I can't hire anyone that meets your 'expert' qualifications for $65K/year", there's nothing my supervisor, or his supervisor, or the CIO, or the agency director, or even the governor can do; other than recommend we switch to using contractors which has its own downsides.

There's been an increasing push that has been heard for IT salaries to be "re-evaluated", but it's suffering from politics and all the usual high-level government malaise. It'll be at least 2-3 more years before anything happens, and there's a 50/50 chance that the outcome is "we should pay you more, but we won't."

That's the same excuse they've used for not giving "cost of living" increases most years. :)
To be used in Pijul as a pure Rust implementation of SSH client and server. They similarly replaced Pijul's LMDB dependency with Sanakirja[1].

[1] http://pijul.org/sanakirja/
I think what the Rebol guys found was that it was generally tough to get into by experience programmers who were used to looking at C-style syntax. New programmers, however, tended to pick it up very quickly.
I think you're absolutely right here -- and I would add the other meme common in that headspace: "No one knows what they're doing", a meme I also hate with a passion.

For all we know, Holmes could have harbored grave doubts about the viability of the tech, based on doing all the right sanity checks. But if she took the meme seriously, "hey, no one else knows what they're doing, no one knows why anything works, they just meander through life and things eventually fall into place. Once you have enough status, you're bulletproof, right?"
Probably because in the cases being discussed, it is the police who have the guns, not the citizens. I don't think even the most hardcore gun control zealots are advocating for the American police to give up their guns (at least not their sidearms, I suppose the military weapons are a subject of a different debate).
I thought that just like the notebook, IPython was a "view" into a python kernel. Is that wrongly understood?
#11 is the same as #20
It boils to down lying like crazy and saying/giving private information to the potential employer I didn't consent to.
Sure. But if you're already using CPython (as most users are), and you know Pypy will be 3x slower on your platform, why switch?
A "ham sandwich" is evidence, often a handgun, placed at a crime scene by law enforcement.

See: http://www.pbs.org/wgbh/pages/frontline/law-disorder/blog/20...
Literate programming is more than that. It is encouraged to order things such that they make sense to the reader, not to the compiler. You can give names to chunks of code and later glue them all together in a different order.

My tool of choice for this is Emacs org-mode with noweb support. The source file is "tangled" (i.e. individual chunks of code are glued back together in a specified order) to create the source for the compiler to process.

Haskell itself has only limited support for literate programming. Most importantly it lacks the ability to reorder chunks of code. (noweb or org-mode babel can be used with Haskell, of course.)
It's strawmen all the way down...

> If all 1000 people were involved in a shootout and fired on the police first...

These are quite specifically NOT the kinds of incidents at issue.

> there are contexts where your right to privacy should be suspended too.

Again, we're not talking about these specific contexts where evidence and investigation are thorough. We're talking about exposing biases when evidence and due process are either minimal or nonexistent.

> And if there were 10,000 privacy violations nationwide and all of them were well-documented emergency circumstances, I'd hesitate to even call it a problem.

Yes, of course. This is clearly not a problem because of "well-documented emergency circumstances." The original article is about revealing trends from circumstances that are very poorly documented, and rarely or selectively reported.
I don't know that it's necessarily plea bargaining that's the problem so much as pre-trial imprisonment and the bail process. What typically makes plea bargains so unfair is when the alternative is to sit in prison, lose your job, etc., just waiting for a trial. Talk about leverage.
This is cool. If anything though, i'm more intrigued by Pijul haha.

I use Git day to day simply because it is the defacto.. but i have never liked it. I've longed for a better dvcs. Granted, i'm not sure i'll ever get it, but seeing new attempts is always appreciated.

edit: It should be noted that in my case above, "better" simply means more intuitive. I'm not complaining about Git either. But, it has a history of not being intuitive.. i think we can all agree there. That's all i mean.
But there could be a racial bias that causes police to be more likely to stop black Americans.
Rant as much as you like :-)

I _think_ we are saying the same thing. I'd put 'done' in quotes for exactly the reasons you mention.

Timeboxing is merely used as a forced checkpoint; to re-assess across all activities/plans. It doesn't mean we can't follow on with more spike work.

At the end of the day, we, as a business, have to determine what we do (or don't do) and when. And we use spikes (or 'research', sic) to try to help inform those decisions.

If a problem occurs - as per your scalability example - or we identify more 'unknowns', we now need to make more decisions, and use spikes (and experience, and etc) to help inform those ... rinse/repeat.
One question, then, would be - did the suspect understand that the robot was going to be used to kill him? Was this announced? Was that threat obvious to him?

There is also a question of time pressure: if police are just camped outside my door telling me to drop my weapon I will be less inclined to do so because the threat (for both of us) is not yet imminent.

If they instead say, "we are coming in. Drop your weapon or we will shoot" the threat is now imminent for both parties.

In this situation, the police are using deadly force without (a clear) imminent threat. That feels like a big red line to relax.
>Sometimes you can just tell that a project still stay fringe just by how hard it is to get to the sourceocde :(

Yup. It's sad/ironic how many techs get frustrated by never-ending signup forms - and recognise that putting roadblocks in the way of signups is A Bad Thing - yet use non-mainstream stuff, figuring that "it's just 30 seconds to install X!"
Not terribly. You may be able to replace it with nix now.
Since this is about an EU decision, yes, that is exactly what is happening.
FastStone Image Viewer 5.6 Crack and Keygen Free Download
WhatsApp for Android doesn't seamlessly fetch and decrypt messages on new installations; you have to set up Google Drive backups from your old phone, and then set up restore from those backups on your new phone.
I know someone who was given a sulfur supplement/treatment in the ER. The doctors did not know if the low sulfer level is what caused her issue or not, but noted that it was odd.
The unicode/bytes change it the most time consuming in my experience. Second comes the fact that you can't sort arbitrary types anymore and that None is no longer smaller than any other value.

In order to ease porting, I've created a modified Python 3.6 interpreter that generates warnings in a lot of the cases that real Python 3 would generate an exception. See https://github.com/nascheme/ppython .

The goal is to have a 2to3 script that generates something that will run, with warnings, under me modified Python. Once you fix all the warnings, your code should run correctly in Python 3.
>Is it that problematic to simply install it with apt or whatever?

It's the equivalent of having an extra couple of fields on a SaaS signup form.

Sure, not everyone's going to be put off; you are going to lose some people, though.
Could be is an understatement in certain places in the US
I took at as them normalizing for a known risk factor. In other words, if white people are armed at a higher percentage than blacks, they wouldn't want that to skew the statistics.
It seems the question we should be concerned with should not be 'is there racial bias in policing', to which the answer would surely always be 'yes' because there's one bias or another in everything human and police are human.

The question we should be concerned with should be: 'How is policing/governance structured in a way that enables or encourages people to act upon their biases to detrimental results?'

The distinction is important because eliminating bias/whateverism will never happen, but making it possible for the justice system to operate fairly given the biases of its constituent members should be a desired outcome.
I would stay away from the term sociopath because whether or not someone is a sociopath depends entirely on their feelings. And it's quite clearly impossible to know the emotions of another person and whether they experienced guilt/remorse/regret/empathy for their actions, regardless of their facial expressions.

I've also read the Nuremberg Diary. That book, and Hannah Arendt's famous phrase "banality of evil" have influenced my thinking in this area. People who do very bad things are not necessarily "less than human" or "exceptionally inhuman," although it's easy to make that assumption.

Anyway, I think the concept of a sociopath is entirely theoretical. Until we can scientifically determine what someone is feeling by hooking them up to a machine and reading their emotions as we present them with various scenarios (i.e. a Voigt-Kampff device) then why even bother throwing around such a sensationalized word?

As far as Madoff goes, I never understood the obsession with branding him as notably evil. He stole a lot of money from a lot of people and lied to a lot of people. But the notoriety of that case has more to do with him being an upstanding member of society i.e. "the last person you would expect" (also the scale of the fraud). I don't believe his theft is morally more egregious than millions of other thefts that are committed every day.
One more devastating thing is that whenever police make a ride on poachers and take over some ivory or rhino's horns they will burn them. Which decreases supply and increases black market price for them.

The wisest thing to do would be to give it away for free to anyone interested. That would ruin black market.
I think you misunderstand. I admire the man and respect his right to own his weapons and defend himself while he's out there in the middle of nowhere on his own. I was simply pointing out that it's natural for someone to be slightly wary of a civilian with assault weapons.
The public defender system is woefully underfunded in many places too. So yeah, I'm all in favor, but we do need to consider the consequences.
Show HN: Simple Python 3 Flask Template for OpenShift
That is evidence of the problem being difficult, not a rigorous "perpetual motion"-level impossibility proof. I could write something similar about a proposal to have computers play chess, based on the absurd blowup in elementary operations (think 1940s) and logic gate resets needed to compute a good move.
Yeah, fuck Touch ID. In my opinion, a computer security feature that works when you are unconscious is not a computer security feature.
What are your thoughts on Helion?
Disarming most police still isn't disarming all police. The situation you describe is what SWAT teams are meant for.
>Here are some software engineers that are largely getting ignored:

Idk, people who have problems they need solved today (not after stringing along would be devs for months for the latest fad-de-jour) opportunities are out there, but take some looking outside of the crap posting resumes and useless meetups…
Last time I switched phones, Whatsapp did not restore my old message history. Facebook did, but that was before E2E.
Continuum Robot Arms Inspired by Cephalopods [pdf] (2005)
I can tell you from my own experience that the "negative unemployment rate" comment is false. I have been unemployed since March, and I've had no less than 12 in-person interviews, some out of state, and countless other contacts all resulting in rejections.

These were positions I am qualified for, and that I know I would have succeeded at. I've been told it would take me 6 months to start contributing to a Python codebase even though I have significant experience in the language and the problem domain for that project. I've been told I have too little experience mentoring a team despite doing just that at my last job. I've been told I don't have enough JS experience for a position that did not ask for any JS experience.

The market right now is poor for a developer without a fancy CS degree, or one without the luck of a golden pedigree from a previous high profile company.
The first link describes "occasional recurrences" since 2002 with a citation I can't follow. The second article describes efforts to hoard food to protect against a famine. Doesn't seem like evidence that there is, currently, a famine in North Korea.
But actual experiments can find causation, and they did those experiments.
From what I've read, the shooter was contained and did not have hostages. They didn't need to bomb him to death because "negotiations failed," they could have kept him under siege until he was forced to surrender due to lack of supplies. The fact that they had to drive in a bomb is a strong indication that the shooter was not an immediate threat. If he was, a sniper could have got him.

I think the police should never use lethal violence if there are any passive options available to them. This guy was obviously guilty of murder, but I'm more worried about other cases where the police might decided to use techniques like this in the name of safety, such as a "drug bust" against "armed and dangerous criminals" that happens to be carried out against innocents at the wrong address.
i've been tinkering with the misfit bolt which is a bluetooth bulb, and some fella (@fayep) posted that on my GH repo last week: http://www.yeelight.com/download/yeelight_blue_message_inter... - this seems to be common to several implementation of bluetooth bulbs as the bolt works with these specs.
couple implementations for these:
https://github.com/fayep/bolt, https://github.com/sandeepmistry/node-yeelight-blue, https://github.com/flochtililoch/misfit-bolt (last one is mine, largely inspired by the two above)
No problem. I just haven't picked up on the local lingo yet. Thanks for verifying.
But it doesn't include the competitors.
And where did you get your "facts" from? Source?
Ask HN: Interviewers, what are you looking for when interviewing someone?
I've noticed that people interviewing me are jotting down notes, whether testing me for soft skills or technical skills. However, I'm not sure what they are looking for?
> I'm assuming for people who don't have strong security backgrounds

That's already a bad start.

You mean inventing Signal from scratch (which is rough) or incorporating the libsignal protocol into a new messaging app?

All of the libsignal repos have a good readme that explains init [1][2] , so you can start there. Browsing Signal source is helpful not so much to understand the protocol, but to see if any special precautions were taken against side-channel and other implementation pitfalls.

I mean, you could contract moxie (hey moxie, what's your price?)

EDIT: there's also this [3] independent implementation of libsignal in golang that tries to make some targeted modifications to fit their need. Can't vouch for its quality, but it's an interesting effort nonetheless.

[1] https://github.com/WhisperSystems/libsignal-protocol-java
[2] https://github.com/WhisperSystems/libsignal-service-java
[3] https://github.com/OpenBazaar/libsignal
To put this differently, putting a timebox around a spike is really good if and only if "we don't know yet" is an acceptable answer. I find that it usually isn't - you're doing the spike precisely because you don't know enough to estimate or do some other piece of work, and if you don't get to the point where you do, you still can't do it.
Great article. Another nitpick:

> It’s important to dispel any illusion that these decisions were made with precence for the future the domain name would have.

I don't think precence is a word, and I'm not sure what would make sense as its replacement.
I think the main challenge isn't how to filter air at home, but when you are traveling outside, e.g., buying groceries, going to work, etc.
“You’re on Earth. There’s no cure for that.”
> That is evidence of the problem being difficult, not a rigorous "perpetual motion"-level impossibility proof.

That the uncertainty produced by the source chosen exceeds the acceptable variability in the results is an impossibility proof for a testing method relying exclusively on a single sample from that source having acceptable accuracy, since the accuracy of the test result cannot exceed the accuracy of the source used in representing the underlying measure.
For sure they do. But I've spent my time with Haskell and I've seen really simple things obscured under a cacophony of type noise. It's not uncommon at all to see a piece of simple logic with proportionately 3x the amount of type syntax around it or related to it. Especially when you need to do IO or state, as we sadly need to do here on earth, then it seems like Haskell is trying to put a brick wall of type restrictions between you and a simple routine at every turn. Talking not about doing some printouts, but actually making a long-running application where IO and state is ubiquitous.
Dallas Police Shooting: Blowback from Impunity and Structural Racism
I'm not sure if that's more positive..
You mean more* risk (not less).
I mean docs that assume I've never looked at any other GUI system and don't know what an event even is, much less how to register one.

What if I'm a first-time programmer or have only ever programmed in MIT Scratch? What if I'm a PHP programmer? Do the Lazarus components work like Swing? Do you register event handling the same way?

I want tons of examples for every component--examples that start simple and work up in terms of complexity with comprehensive explanation along the way and I want it all linked under "Documentation" off the front page.

Now that's a lot. I recognize that. But I don't care. There are whole books available for Swing, JavaFX, Windows Forms, and WPF, not to mention Web Design. That's the standard today. Book scale documentation...

I'll say it again: I'd like to use Lazarus. I spent the morning programming a desktop application that could have been done in Lazarus, but it wasn't because I'd rather build programs than decipher an undocumented system, and I suspect I'm not alone.