skysight-inc/HackerNews huggingface dataset:
Seems like a simple problem to solve - raise the wage offered in the tier two city. If the benefits of moving to a less desirable location for work outweigh the drawbacks, people will do it. Your company probably just doesn't want to pay people enough to move there.
Show HN: Cracking passwords with a simple genetic algorithm
Thanks for bitbar @Shikkic, this will really help me to keep up my daily OSS contributions. Your plugin is also the reason why I downloaded bitbar, as I knew about it but never had the need to bloat up my menu bar even more. But this gave me all the reason I needed! :D
For more modern humour poking fun at the Victorians, there's the brilliant BBC children's series Horrible Histories:

https://www.youtube.com/watch?v=AHFNK-3lZ1U

(video annoyingly rotated presumably to avoid copyright detection)
Ask HN: Why am I banned from submitting?
Every link I submit, it goes dead automatically.
If you’re using MPI, you’re doing message-passing. If you’re doing message-passing and you have no methods for notification or recovery from faults, you’re doing it wrong.
There's only one external storage. And in an attempt (irony alert!) to make permissions "easy" for users to understand, some Android people decided to call the permission that grants access to external storage "Photos". Because that's where the photos are stored, and it's sometimes/often the most important/sensitive thing there.
Oh I'd go much further. They should be judged like a Nazi German in WWII. If you are complicit in supplying technology to the surveillance state and have the knowledge that cowardly drone-operators are killing innocent[1] people around the world (while calling their children targets "fun sized terrorists"). Then they should not say "oh but I needed the job". Millions of Germans were also only doing their jobs during the holocaust. The difference is those who happily concur and support these sick systems and those that rise up and distance themselves from it or fight it.

It is that black and white unfortunately. But only because current US legislation with their war on everything made it so. It is up to Americans to change it and as a non American I'd judge anyone who doesn't rise up and distance themselves. You should be on the streets protesting and not behind laptops and cowardly half-arsed remarks hiding yourself. Downvote me all you want I really don't care.

[1] https://theintercept.com/drone-papers/

edit forgot to add the link
Having actually used "dumb terminals", like the DEC VT-100, Qume QVT-101 and others over RS-232 connections and shoe-box sized modems way back in the 80's I found the start of your comment to be somewhat funny.

Not criticizing your post at all. Simply making the observation that what we might call a "dumb terminal" today is a million miles away from where this term originated. Just like the "film industry" is really the "digital image industry" today.

I remember running AutoCAD 1.2 on an 8086-based S-100 CP/M system with the addition of an 8087 match co-processor card, 640K of RAM, 1 MB on a RAMDISK card, a tablet with a puck that used a magnetic coil to sense position and, yes, a DEC VT-100 "dumb terminal". Sometimes I had to unload stuff from memory just to be able to plot. Fun times. Funny that today developers think stuff like vim is cool. We couldn't wait to get off those damn terminals and use "real" editors.

Who knows what Ctrl-K-X belongs to?
I didn't expect it to be a hundred and fifty dollars; that's a little high for such a product with these specs in today's world of $10 to $20 "micro computers". It's a pretty awkward price point, given that it has a niche market but is being marketed as if it didn't..
Conway's game of life seeded by JavaScript equality table
You missed the biggest part: raw caffeine is incredibly, incredibly bitter.
Maybe you could hire promising people and let them learn those skills, especially if you want people who are "less researchy."

I'm not aware of a huge pool of "Machine Vision + Deep learning" people who are trapped in India because of Wipro using up all the H1Bs on J2EE programmers.
Ask HN: Will JavaScript take over front-end?
I am seeing unbelievable amount of blog posts, releases, upgrades about Javascript frameworks and libraries during the last 12 months. I personally only used AngularJS 1.x for one of our projects, but did not have time to try React, or AngularJS 2.x.

My conclusion for Angular is that it takes 40% more development time to finish a project with AngularJS than without using it. We gained some speed for sure, but I think we could do better in the same amount of time with back-end optimisations.

- How was your experience with React or any other?

- Should I invest more time to keep me updated with one of them?

- I still think, front-end should just present the information, not the whole application logic. Am I missing anything? (I just discovered polymer-project and loving it so far!)
Is this true? What are the major obstacles preventing you from dividing your problem top-down in a FP? Just because you're able to better divide programs bottom-up in FP doesn't mean the other way around is harder, right?
"when Steve Jobs saw a demonstration at Xerox’s Palo Alto Research Center of a computer mouse visually interacting with files on a desktop, he launched Apple Computer Inc. to bring that dream to consumers."

Um, Apple I? Apple II? Woz?
Maybe you could go with different layouts that you can set via the env file? Like Compact mode (for people like me that have a 13" laptop) and a normal mode. Or perhaps your config can go more complex than that. But I think if you download this plugin, you will also know what those numbers mean, I would think. I'm a UX noob though.
I'm always glad to see maps using OpenStreetMap data over Google Maps.

I always find it fun to look over the edits I've made, and it helps point out where more detail would be useful for different use cases.
Two important things about JavaScript that enables easy "asynchronous programming" are:

1) First order functions that you can pass around.

2) The fact that those functions can be closures over the local scope, so it's easy to pick up from where you left off.

Two big mistakes in the design of JavaScript that work against easy "asynchronous programming" are:

1) That "this" is not lexically bound in the local scope (technically it's a magic "keyword" that's dynamically bound by the interpreter), even though in most cases capturing "this" lexically is what you really mean to do.

To mitigate that problem, you have to do silly stuff like "var self = this;" to copy dynamically scoped "this" into lexically scoped "self".

2) Each { block } doesn't have its own variable scope, so variables you bind inside loops that repeatedly create closures (like callbacks for a list of menu items) have their value changed out from under them to the last loop iteration when those closures are called later on.

To mitigate that problem you have to wrap another function(){ ... }(); around the loop body to capture the values for each loop individually.

Both problems cause subtle hard to find bugs, even when you know about them and are expecting them and programming defensively to avoid them. And both problems were bad naive design decisions that many other languages had previously gotten right.

But modern bleeding edge JavaScript now has "=>" fat arrow functions that bind this lexically, and "let" that declares block scope variables. (But that's not supported in all browser yet.)

Yay for progress! Worse may be better, but once you've wiped out the competition and taken over the world, there's no reason to keep it worse on purpose.
Nobody in the conventional telecom industry with conventional capital and operating cost structures thinks it's profitable. Just as nobody using Sun servers and Oracle could have built the Google search engine. Evidently Google has learned how to turn communications infrastructure into a cheap commodity platform. Starting with leaving out the deep packet inspection crap, perhaps.
> Who knows what Ctrl-K-X belongs to?

WordStar?
I share a similar sentiment with a different phrase: "code is a living history of past ideas, good and bad."
> stopping companies like Cognizant and Infosys that game the immigration system by applying for the cheapest H-1Bs possible

Cognizant and Infosys will stop the gaming the minute you detach the H-1B from the company - something along the lines of "If an employee spends N months at a company on H-1B, not get into trouble with the law, pay taxes and be a productive member of the community, then that person can work at any similar job without being tied to the employer".

Facebook, Google or Microsoft are not doing H-1Bs so they can trap those employees into working at low wages - Cognizant and Infosys are. Removing the power these firms have over the employee is the only true way to reform H-1B.

President Obama's executive action plans did state intent along those lines [1], but those seem to be torpedoed by vested interests. There is currently a draft rule from USCIS titled "Retention of EB-1, EB-2 and EB-3 Immigrant Workers and Program Improvements Affecting High-Skilled Nonimmigrant Workers" [2] open for comments until Feb 29, 2016.

If you are interested in acting towards a solution to this problem you identify, please consider reading and commenting on it this weekend. You can do it online by going to www.regulations.gov and searching for the eDocket number USCIS-2015-0008 [3].

[1]: https://www.dhs.gov/sites/default/files/publications/14_1120...

[2] USCIS Seeks Comments on Proposed Rule Affecting Certain Employment-Based Immigrant and Nonimmigrant Visa Programs - https://www.uscis.gov/news/uscis-seeks-comments-proposed-rul...

[3] http://www.regulations.gov/#!docketDetail;D=USCIS-2015-0008
The site says all of the data is taken from the British Library's digital collections, which I'd imagine would have an API.
The typical dose varies by your past consumption ;)

If you typically get 200mg through coffee every day, that's not going to do anything for you and you'll have to go significantly higher.

I can say from experience that taking large amounts of caffeine comes with a rather pronounced crash afterwards with headaches and general sluggishness.
I see quite a long list of large compensation (> $200k) numbers there, including for regular "police officers". It seems that by just going to work for the government, these guys have achieved a level of secure material wealth (equivalent to pulling money out yearly from a HUGE retirement savings) that most of us here think we need a near-unicorn IPO to achieve.

I'm happy for these guys, that they're able to live in what I'm sure is an upper middle class lifestyle even in San Jose. It's not that I want their standard of living to be lower for sure. But this draws attention to the facts for the rest of us that aren't put on a pedestal by society and government. I'm well compensated, and I know plenty of other people who are well compensated, but unless I stay in the top 5% of my profession I don't expect to be pulling home $200k+ per year during retirement.
Yes this is a challenge for developers. I don't think the answer is yet another package format.
> “micro-digitate silica protrusions”

Or in Thing Explainer-speak, "little rock fingers that stick out."

Its interesting that it was Spirit that detected this- big new discoveries are still coming up after driving the same robot around on the planet for years! Humanity has just barely scratched the surface (as it were) of understanding Mars.
I'm excited about the Hyperloop:

https://en.wikipedia.org/wiki/Hyperloop

http://news.nationalgeographic.com/energy/2016/02/160223-Elo...

http://www.wired.com/2014/12/jumpstartfund-hyperloop-elon-mu...
Except React has been getting simpler with each release. First there was React.createClass. Then came ES6 classes. Now components can just be pure functions.

Also, the author is using a Scala toolchain to build the JS frontend code. The standard toolchains (with the exception of Google Closure and Facebook's Flow) are all built around node.js.

There are even a number of code migrations available for React: https://github.com/reactjs/react-codemod -- but of course even those can't help you if you use non-standard tooling and let a web frontend codebase collect dust as browsers (and your dependencies) march forward.

Projects are never finished. If you cease working on a project, it just becomes unmaintained code.

EDIT: As someone seems to have flagged my account and I'm now apparently limited to two replies per hour or something ridiculous like that (yay for passive aggressive moderating tools?) my reply comes as an edit:

> That's a pretty shallow definition of easier.

It's a library that lets you describe DOM subtrees based on application state. How much simpler could it possibly be?

If you mean the toolchain, the keynote at React.js Conf made it clear that improving that part is a major goal for 2016 but none of that will help you if you want to solve everything with your existing Scala tools.
I think #2 is supposed to be "wisdom". Note the OCR errors, eg "so;" is rendered "soj". It's still not entirely clear to me what the point of the passage is however, it is IMO poorly written.

https://archive.org/details/bookhumourwitwi00projgoog is the text "Humour, Wit and Wisdom" - "the latter days of Bonaparte" is on p.2.
It is not common for cities to have income taxes in the US. It mostly is paid at the federal and state level and then trickles down.
I am relatively new to this myself, but at my work there is a lot of discussion of the SOLID principles:
http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod
more cost effective humans.
Except inflation doesn't really help. If you own property, as I do, inflating money 2x just means my property goes up 2x in value.
http://www.newegg.com/Product/Product.aspx?Item=N82E16856659...
I found it, but the $100 variant looks like better value with it's Windows license and identical processor.
https://news.ycombinator.com/newsguidelines.html

>Please resist commenting about being downvoted. It never does any good, and it makes boring reading.
This is my biggest gripe with the modern technology industry. We've gone from "you have the background and skills to do the work - here's how we do what we do" to "You don't check these thirty boxes specific to our company?! No job for you!" It's getting rather absurd, especially when you're job hunting and the recruiters give you the "you have an impressive background and could do this work, BUT you don't have <exact ten things> ergo we'll pass." Very few people take the route of finding talent then training them up. Companies willing to take the time to train their people and focus on finding raw talent they can mold will make a killing. Not only will the people be trained exactly how you want them, but I'd argue they'd be cheaper and you could tie compensation increases to hitting defined mile marks in the training program or demonstrating competencies.

From the flip side, I see the company concern - kind of. If I bring in raw talent and train it, I've sunk $X into the talent and if they leave shortly thereafter, I'm out $X with no benefit. The counterpoint to that argument, I think are signing bonuses and defined time contracts. In exchange for us training you to do this job and completing the program, you get a signing bonus of $X at the start, $Y at the end, and sign a 2 year agreement to work here. If you leave beforehand you agree to payback the $X+Y signing bonus (unless laid off by the company).

There are ways to address the "skills shortage". The problem is, no one wants to take the time and the cost to do it.
Presumably your employer needed your specific skills and genuinely couldn't find an American with them. This is exactly the purpose H1-B visas are supposed to serve, and as you've demonstrated the lottery makes them useless for that - the odds of the person you desperately need getting through are too small. The reason H1-Bs work for the outsourcing firms in the article is because they're just using H1-Bs to get cheap, low-skilled replacements for US workers. They can simply take on so many applicants that after the lottery, enough are left to fill their recruiting targets, because they're not looking for any special skills.
Theoretically it could also be a 75 year old man in his 55 year old corner grocery store. Just playing devil's advocate here. I agree with you.
The way the announcement was presented at React.js Conf this year suggests that the version shift also represents a change in stability. Personally I think that from now on React will treat major releases more like Node does -- but of course many people would still consider that pace anxiety-inducing.
Don't quote me on this but I think Ghostery is supposed to whitelist the benign stuff on Google domains such as googleapis.com automatically. I don't know enough about technology in general or NoScript in particular to tell whether this was a recent change or if it is then whether NoScript wants to mess with configuration for existing installations (my gut reaction is probably not as this is a little different from just getting updated fanboy's list for ad blockers).
Slightly OT, but why are you calling unmountComponentAtNode before render? That seems like a bad idea. ReactDOM.render will update in-place, rather than tearing the whole thing down and instantiating new versions of everything.

https://facebook.github.io/react/docs/top-level-api.html#rea...
I'm not sure that this experiment is all that useful in determining the practicality of using Raft instead of Paxos. Anybody implementing one of these algorithms is going to be spending more than one hour learning it. In my experience, there a lots of corollaries that must be proven in order to actually implement the spec described by the Raft paper (mainly due to weak assumptions that cannot be assumed in all production systems). Paxos is a bit more established, so this is not as big of an issue; however, I still do not have an intuitive understanding of Paxos. This can (and will) lead to non-deterministic bugs in your implementation. A more useful study would track bugs in Raft & Paxos implementations.
Three ways it can help:

* A lot of plugins/libraries require jQuery, so by using jQuery you can use those plugins.

* It's easier to hire junior devs that can write good enough jQuery, compared to native JavaScript.

* As a very mature library, there's lots of documentation out there for standardising the way you do things. This makes it easier for other devs to pick up your work.
Lots of people seem to be getting O visas anyway. I don't really know how, but ask a lawyer.
I'm in the US and I've never heard that term before. Google seems equally confused.
The JSX is not the same as it is encapsulated in the render() method withing the JS file. This is the whole point of why this implementation is not a separation of concerns. The view is essentially embedded in the controller in order to simplify how a controller passes scope to the view.

This isn't the first time people have fallen prey to embedding HTML as a string into JS to write the DOM. 5/10/15 years ago, if we saw this, devs would just shake our heads. If anything React is an old hack, an anti-pattern brought forward again.

I misspoke about views in business logic, as you said, it is the controller logic, which should be decoupled from the view itself as well. The naive example of converting a webcomponent to a JSX component may look similar, but more complex components will only require greater complexity for the render() method to handle.

I understand your rationalization, but the crux of the arguments here are concerned with the anti-pattern React introduces and why developers who've come across this before have seen this as technical debt. The arguments for React are a matter of opinion, wherein the arguments against it are based on the practical principles for programming UIs, principles have been forged to be tried and true since the 70's.

I personally favor standards, such as webcomponents and OO programming for modules. I understand that this may not seem popular at this point and time, but 20 years of dev experience has taught me otherwise.
Previous discussion: https://news.ycombinator.com/item?id=7568175
They are both:

1. Human beings
2. Americans
3. Popular
4. Males
5. Parents
There was at least one court case over it, in 2008, regarding Michael Dell buying a hotel in Santa Monica via a holding company, where he prevailed in court: http://www.santamonicadispatch.com/2013/05/prop-13-gives-edg...

It seems it's more complex than what I implied, though. The property needs to not only be owned by a holding company, but sales of the holding company have to be structured in such a way that overall ownership of the holding company isn't deemed to have changed. If the above article is correct, that's triggered when a new owner acquires a majority stake. So to avoid triggering a change in ownership in this case, Dell structured the sale so that he, his wife, and another business partner all bought interests in the company, split so that no single purchaser acquired more than 49%.
Do you have a link on the LMDB verification?

What I know is that SQLite IS safe to use even on unsafe file systems. There was a discussion here few months ago (link was from danloo.com).
That is super nifty, love the design!
> It feels more solid in your hand

Something I learned soon after I launched my first hardware product:

People still have an instinctive physical relationship with products that must be the result of evolution making a connection with heavy or solid = more-food/safer/better or something like that.

I remember devoting a ton of time to making my first product as light as possible through sophisticated mechanical design and attention to component choices in the electronics.

During my first trade show in Europe, this Italian guy came by multiple times to look at the product. He asked for a price on his second visit. It was USD $8,000. The next day he came back one last time and asked: Why is it $8,000 if it is so light?

Absolutely blew my mind. Was not ready for that question at all. Upon return to the US I directed our sheet metal vendor to switch from aluminum to steel of the same gauge. We also added a small steel bar riveted to the inside to increase the weight a further. In all, I think we easily added about five pounds to the thing. Now it was "worth" $8,000.

Over the next three years sales and comments during sales presentations proved, in no uncertain terms, making it heavier had been exactly the right move. People would make comments when they picked up this damn paper-weight such as "wow, feels solid", "wow, lots of tech in there", "wow, I know why it cost so much now".

It was amazing to see how many times the moment the deal was done coincided with the instant they picked it up.

Amazing.
I suspect that key value store is just the user interface and that whatever heavy lifting there was to be solved is related to tuning for time series data from sensor networks.
Also, post hoc fallacy - lots of failed companies also have ceremonies.