skysight-inc/HackerNews huggingface dataset:
There are a few options. Easiest is to just render HTML strings on the server, not actual DOM. But, you can also use a DOM implementation if you want to, like jsdom or PhantomJS, and then capture the outerHTML of an element as an HTML string to serve. But, that is slower. React.js has a nice middleground approach; it has a fast pure-JavaScript DOM abstraction that can emit either DOM (browser) or HTML (server).
Technically, you're correct, see the biology and chemistry use of the word. But seeing how you're dealing with a mathematically inclined audience, there will be disapproval. I think it's a very useful concept in general, the more it gets out into the world, the better.
No sample? And you want my e-mail?
They also had a constant radio connection with the station, which is the opposite of an "air gap".
Did you adjust the Household size to 2? If you've entered 2 people, then make sure you update the household size to 2 as well. If you're in your late 50s, and your household income is $60k living in San Francisco, you can get free or almost-free coverage.

(Yes it's a bad design)
Sure. Think of void * in C. interface{} in Go isn't really that different, there's just a bit more language support for testing if it satisfies a specific type or not. Add in type assertions, and it's basically as though you had a dynamic_cast in C++ that worked from void * to an interface type.

To me, it just seems ugly. I like a type system where I know what a type is at each point, and there isn't some ugly "catch all" type that you can use when you run out of other options, which effectively just throws away all type information (and this is what interface{} does, as everything implements it).
I am genuinely interested in what you think the artists lose if I have easy access to the written lyrics of their songs?

I just do not understand it?
Amazon Smile: Amazon donates to charities when you buy
read something similar a few weeks ago.

http://andrewlinfoot.com/why-every-1st-time-entrepreneur-sho...

Its a completely different way to think about things when you can push an update versus doing an expensive manufacturing run.
Privacy happens at the endpoints
The problem is that there's a limited amount of good, novel, fun games to choose from. I can't say there are always good indie games to play every single month. You are bound to hit the "less interesting games" sooner or later.
Very good article,though i dont use go(yet) ,that's the kind of writeup i'd like to see more on HN home page.
Why depend on lawyers?

"The reasonable man adapts himself to the world. The unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends upon the unreasonable man." — George Bernard Shaw

Unconventional thinking is what hackers and founders use to shape their world -- it's part of what makes Silicon Valley great. And creative, unconventional approaches doesn't mean illegal, quite the opposite. Creativity is design within constraints.

Today it's a letter by Sasha Beilinson in the "Notices of the American Mathematical Society". Tomorrow there could be another, then another.

To understand why Sasha's Belinson's letter is important, see Derek Sivers' 5 min talk, "How to Start a Movement" (http://www.ted.com/talks/derek_sivers_how_to_start_a_movemen...)
I think it's not necessary because "one is smart and other is not."

Here are some of my thoughts on this:

1) It's probably not a decision of people who understands deep understanding of technology and implication in bigger publisher. It could be some "suit" type of people who don't even know how DRM works, or their legal department.

2) Publishers can actually afford DRM -- I will be honest that I don't know how much DRM solutions actually cost, but activation servers won't run for free. Simply, a lot of independent studios don't have enough resources to maintain DRMs. DRMs would probably increase support case as well (there will be more support inquiries coming in; people will be running out of activation count, or their computer can't talk to activation server) which a lot of smaller studios just don't want to deal with.
IMO Rap Genius falls squarely within the fair use safe harbor of copyright law, since it provides educational/critical analysis of lyrics rather than simply republishing them for profit.
It's closer to "I hired two Koori to help me lug these boxes around."
For some people, the concept of action outside of the officially endorsed channels is so alien, they implicitly treat it as though it is categorically illegal and unethical.

I don't even think it is intentional, they just aren't familiar with grappling with such concepts and make fundamental blunders when talking about this sort of thing.
> Keep in mind the constraints in the article, for example: some shows have 20,000+ episodes, actors show up in 100s of shows, and "We had no way to tell, aside from comparing the names, whether they were the same person".

As others have pointed out, it requires two trips to the database. Given their architecture (distributed nodes), network latency is minimal, so this is essentially two calls to the database.

show {
_id,
title
}

actor {
_id,
appearedIn : [id]
}

db.find({"title":"awesomeshow"},{"_id":1})
db.find({"appearedIn" : showId})

Each actor is unique in the database, when you query, you get back unique actors. I'm not sure why they're scared of joins (or multiple queries in mongo).

The question you ask yourself is not whether you're joining, but how often you're joining. If you're not joining often on actors and shows, document databases can work better, since you represent the show and all its episodes without having to join.
> "The article seems to think this doesn't work because you can't give a large bonus to everyone"

Indeed. Why can't you simply measure people against a consistent, externally-defined bar, and reward them based on their share of their performance group?

e.g., Employees who hit the bar are in group C, employees who exceed it are in group B, employees who are extraordinary are in group A. Each group has a portion of the bonus pool, and each member of a group gets the same as every other member of their group.

You can still get rewarded for better work, but now you're no longer working against an arbitrary bar defined by your peers. If you, hypothetically, have a team full of rockstars then everyone shares the bonus pool equally. Done.

Also, what's up with tying raises (not bonuses) to performance rankings? At the end of the day people will leave if they can get paid more elsewhere. The best/only way to ensure your employees don't leave is to keep paying them at or near what they can get on the open market today. That guy may be the weakest engineer on your team, but he's still a good engineer and can do a lot better than the shitty 2% raise you've stuck him with.
Absolutely. Best experience of being in engineering thus far.

However that is still quite limited given what we learn.
Yes, if you only mediate between buyer and seller then you don't need to pay vat. However if he was to do the trading himself (buy from one person, sell to another), then that provision does not apply.
The difference is that rdiff-backup requires the exact same version on both ends.
Hmm. I see several subsidized plans offered with similar inputs: http://i.imgur.com/ZJpSGC4.png

Do you have a screenshot of what you're seeing?
I don't think you want to be replicating the management practices of major law firms, which are generously considered awful places to work. Lockstep bonuses only apply to associates, and are usually a function of the senior attorneys' inability to provide meaningful feedback and performance management, not a desire to reduce competition.

Competition at law firms is fierce. They are rife with unproductive credit seeking, because the real incentive isn't a bonus, it's promotion to equity partner, and there are only a small number of spots open at the top.

But you nail the real issue with stacked ranking: HR departments should help design and manage a performance management system, but the feedback and decisions need to be handled by managers who know the business and have direct involvement in their employees' work. I think you're over-estimating how effective this is at investment banks, where you tend to have transparent performance metrics, but awful managers. But there a lot of major companies tend to get it right.
You license them from the publishers, as LyricFind did: http://thenextweb.com/media/2012/01/30/lyricfind-gets-the-gl...

The Harry Fox agency (harryfox.com) is the industry broker for music publication licensing, virtually everything in the US can be licensed through them.
A connected world is a better world. Right?
Yes definitely, you're right. What I mean is that bad design or bad architecture can take months to fix while most editors can fix formatting automatically with a few clicks. At the same time I prefer my own projects to have very clear and consistent style.

I think the original poster (and the topic here) is using way too strong words for such an irrelevant issue. It's airbnb's project, they get have their own opinion. Their style guide won't ruin the Javascript community.

Also, the original poster seems to be on a mission of his own. He forked the project @ github, did a few modifications and changed the documentation in a way that conflicts with the original MIT license. Poisonous attacks like that are what destroy communities.

https://github.com/JacksonGariety/javascript/commit/e06e9a46...
I think this is the best summary I've heard over software vs traditional engineering to date.
I'm actually not sure how to apply that advice in real world situations. Giving negative feedback usually triggers aggression, and group reprisal, while switching to "hypotheticals" and "friends" makes it sound as if i'm talking down to them, which also triggers aggression and group reprisal. So, I normally look for the socially anonymous outlet for my opinion, like downmoding the "me too" and "thanks" comments, and then move on with my life. Because, while the comments are not hateful or disruptive, they don't add anything to a discussion.
People asking about Golang may be interested in this article, where someone considering rewriting a large python project choose a new language, where both Golang and OCaml are among the candidates.

http://roscidus.com/blog/blog/2013/06/09/choosing-a-python-r...
it fails to understand the root issue mentioned on the article it is responding to.

The original article says: everyone settled down for a crapy simulation software and implementations are terrible.

so, the conclusion of this piece "there is no way to realistic improve" is way off. Maybe he should get at least a couple years under the belt before trying becoming a pundit.
I use a similar approach, rsnapshot. What I worry about though is that it seems very wasteful when backing up a whole system. Each time the backup is happing I hear the disk churning for half an hour, and I realize it's mostly recreating hard links to files that _haven't_ changed. So I wonder which backup method would require the least amount of disk activity.
T-Mobile to sell nearly $2 billion in stock to acquire more wireless airwaves
I think you can mostly make it work for any existing ticketing system.

By `mostly work', I mean `good enough for an art project'.
Your example is spot on. Additionally, I use twitter, authors of books, authors of research papers, see who these devs follow, and numerous other ways of traversing the GitHub social graph.
well, the thing is, his version replaced all the code with type annotations. So, in some sense, he replaced a 5 line method with no code at all!
Can someone explain to me what exactly happened?

I don't really know what Jenkin is and what "git push --force" does.
The central repository is the only point that knows (with 100% certainty) which ref the branch was set to before the force push.

Each distributed node only knows the ref the branch was pointing at the last time they fetched, so their certainty on what the branch looked like before the force push is much lower.
http://www.reddit.com/r/Android/comments/1qdwbq/google_maps_...

this thread is indicating it is doing real time rerouting
Exactly what I was wondering. "What's better for this field of study? A classroom environment, or getting your hands dirty and diving into it yourself?"
Querying, and querying immediately after insertion. If you want queries after insertion (which require views), this can be slow in couch. Also, if you want to query, but don't want to add a view, wait for it to populate (causing a performance hit while it builds, plus while it is up), then remove it.

If you're doing primarily insertion with querying via id, and using views in which stale data is ok, then couch is far superior to mongo. But that's not a use case everyone has.
The Rush to Coin Virtual Money With Real Value
Et voila!

http://imgur.com/RluUCMn
For some reason I have a suspicion that Github Trending is game-able. I tweeted once about this suspect repo that had 3000+ stars and all it said was something like "Hello to all github trending viewers" or something along those lines.

Link to the author of that repo: https://github.com/mandatoryprogrammer

What remains of the repo is visible in his profile.

Anybody have a clue as to how he did it?
Mobile-First Social Networks Are Taking Over
Yes. He's still with the company. I left for various reasons.
Because they hired Microsoft managers.
Meet ART, the future of Android
They didn't absolutely need to, but the alternative would be finding a user with the latest commit in their local git for every single repository, which could be 150 different people, then getting them all to push those changes... it's a bit more involved than just getting a github admin to put the repos back the way they were.
Show HN: A small Ruby script to aggregate your Netflix "Recently Watched" data
This was my first attempt at writing a script of this nature. Let me know what you think!
What is the syntax on finding an array value matching some key? E.g. given a user with field "favFoods":[String], how do I determine that pizza is in there?
I guess it's not really about that. It's that artists (besides mainstream ones) need all they can get from any source they can get it -- they really do, just to get by.

The two sides are: artists just can't make it through with a little pay with little sources of revenue, or we don't get our lyrics, tabs, and/or the songs themselves for free. It's a difficult balance where solutions are hard to find.

It's worthwhile to basically see lyrics as poetry. Poets get by by selling poetry (well, few, in this day and age), lyricists/songwriters should also ideally be able to get by.
In the Docker issues, also look for the "easyfix" tag.

We try to set it for issues that are hopefully actionable for people with a moderate knowledge of Docker and/or Go.
> (Yes it's a bad design)

Exactly my point. This whole site strikes me as programmer hubris.
Thinking Small: Finding the Right Niche
This is a great resource. Only if they had more classes available. Oh well.
Tweeting Isn't a Bubble, It's a Bandwagon
one could always wiretap/spy on them to see if they have any type of recidivism. /(only partially sarcastic but then who watches the watchers?)
I've been thinking about this for the last few hours... and regardless of the language used, I think I'm finding the point of confusion!

isomorphic: modules that have the same abstract interface and functionality but that are written in different languages and executed in different runtimes

monomorphic: modules that have the same abstract interface and functionality and that are written in the same language and have the same runtime

heteromorphic: modules that have the same abstract interface and functionality and that are written in the same language but run in different runtimes

homomorphic: modules that have the same abstract interface and functionality but that are written in different langauges that run on the same runtime

See, the thing is... languages are compiled to runtimes, right? But they are transpiled to other languages...

There surface area of this discussion is very interesting and seems to have some interesting properties, and if you don't mind the math pun, it is truly a complex issue!

As for how to actually name these different things, I don't think I really mind... maybe isomorphic and monomorphic swap in the above definition... I've been reading some latin and greek roots to try and give them good names, but I'd love some suggestions!

For example, a function written in Scala that functions the same as a function written in JRuby and compiled to the JVM would be an example of a "homomorphism".

And a function written in JavaScript that is compiled to run in both node and the web browser is an example of "heteromorphism".

A function written in JavaScript that is compiled to run in the Ruby runtime is an example of "isomorphism".

Monomorphic would just be sort of like an identity property.

Also, I have no idea what I'm going on about, so please help me fix the language!

Maybe isomorphic IS the correct term for what is going on in the article, who knows? :)
Software could evolve too, given sufficient time. A hard-disk corruption here, a transmission error there...

Moreover, a virus could be deliberately designed to mutate, so as to evade anti-virus software. In fact, isn't this already being done since ages?
Over seems perfectly natural (to me).
I don't think the Yuppie Nuremberg Defense applies here. They would have to know what they are doing was clearly wrong for starters what makes you think the average rank and file employee would even have that kind of a big picture view?
HealthCare.Gov Enrollment 50,000 instead of projected 500,000
Not really. They handle querying and aggregation much differently.

For people coming from SQLServer/MySQL/Postgresql, the functionality differences between the NoSQL flavors is something they don't expect, and often don't explore. There are a number of heavily used NoSQL solutions because they're focused on specific use areas.
After my first bad force push (silly git push default on an unfamiliar machine) I now 'enforce' the `git push remote from_branch:to_branch` syntax on myself when force pushing, I also have adopted the habit of always accompanying any --force with a --dry-run.
they aren't going to disappear. the harshest possible outcome would be that they all end up operating from outside the USA.
Well, it's interesting, but doesn't getting rid of the wings and later the flippers mean it's a single use drone?

Also, how limited are missions that the drone can only do things in this order and not, say, start with flying, then carry out its mission on land and then escape via rivers/sea?

Also, also, the potential for reverse-engineering on anything left behind is a weak point.
That's fine for some projects, but not every project follows that flow. One example: ompanies using GitHub Enterprise internally generally don't make every regular contributor to a project have their own fork (or at least they shouldn't, as it creates needless extra overhead). In that case, having some extra granularity around denying non-fastforward pushes to some branches but not others would be a helpful addition.
There's a different approach that performs all rendering server-side and sends snippets of HTML to the browser to be woven into the existing page. I suspect that would be more natural for non-JS frameworks.
Equally shared bonus pools were fairly common in top-tier professional services firms until the late 1990s, and even when they changed, most kept fairly equal distributions of profits between partners and to associates.

However, almost all of those firms used a stack ranking system that was even more aggressive - those at the top got promoted, those in the middle got worked out over time, and those at the bottom got fired.

Shared bonus pools work when a company has an aggressive performance management culture, but this doesn't become visible as long as the company is doing well.
When things are good, everyone is getting an extra lump of cash, even if it has nothing to do with their individual performance. But when the market changes, top performers flee because they realize they can make a lot more money someplace else, and that they'll never hit their goals until the company gets rid of the stragglers at the bottom and stops settling for mediocrity among everyone else.
GoPro's Video Revolution [video]
> When I'm in Midtown or some other place where I'm "sharing the road" (that's cute) and thousands of two-ton 350 horsepower motor vehicles are bearing down on me because they're driven by people whose only priority is getting to the Midtown Tunnel or the 59th Street bridge as quickly as possible, you can be damn well sure I'll do whatever the hell I need to do in order to get a head start on these homicidal mutherfuckers, and that includes running the light if I deem it safer to do so

I'm not a regular cyclist, so maybe I'm just confused, but under what circumstances would it be safer to run a red light? "Get a head start" implies to me that they're starting to cross the intersection while cross traffic still has the right of way, which seems far more dangerous.
Jenkins is build server software. It's existence is related to the story only because it was a Jenkins developer.

'git push --force' pushes your copy of the repository to the remote, regardless of what the remote has. He basically told GitHub, "Hey here's the /real/ copy of the repository, the copy you have is totally wrong" and it overwrote all the history because his copy was a few months out of date.
- Yes. They should.
You don't have contact info in your profile so I'm leaving a comment: awesome username!
But how many of those taking non government jobs end up working on intelligence projects with the private consulting firms this work is increasingly being outsourced to?
"Either way, one of the best feelings in engineering for me is go draw a 3D rendering for a class and watch it show up as something I can hold in my hand 2 weeks later. No amount of deploying/pushing/launching in software can ever beat that, yet."

Embedded development offers this gratification.
GWT is not Java on both sides. Its Java on the server, Javascript on the client. The Java client side code compiles to Javascript...the abstraction is way greater than what OP is presenting. (JS & JS)

GWT is/was a terrible amount of overhead baggage, but had some brilliant event systems and DOM tricks for its day.
Yes, you generate HTML and send that to the browser.
xkcd on password re-use: http://xkcd.com/792/
This goes beyond cyclist / motorist behaviour. If you really prove deeply you can extract a classical attitude and behaviour seen between a semi-homogeneous majority class and its minority coutnerpart.

By that I mean, in this case we have motorists upset at cylists because they feel that cyclists in some way conflict with their beliefs / way of life (that I can drive on the road with other automobiles and not worry about cyclists or that my behaviour may harm others). I suspect though that at the heart of the matter motorists are upset because it exposes just how poor some people are when it comes to driving and how driving isnt a right nor a privlidge but a skill which requires practice and training.

I mean the same thing can be seen in other conflicts between major groups and minorities. Cars and motorcycles. Post colonial naturalised citizens vs. indigenous people. Middle class vs. Poor. Police vs. 'inner city youth'.

I mean is the issue really that cyclists might do something wrong or that cyclists expose just how bad drivers are at driving and how arrogant individuals try to blame others for their mistakes under the guise of 'being impartial'?

Im rambling now but theres a point in there somewhere.
This is a somewhat extreme overreaction to a level-headed opinion piece in the New York Times that has a linkbait headline, as is typical of journalism these days. I encourage you to read the full article and judge for yourself.

http://www.nytimes.com/2013/11/10/opinion/sunday/is-it-ok-to...
Oh. Ovewriting history magic.

One part of Git I never really liked.