skysight-inc/HackerNews huggingface dataset:
Correction: with all your software.
Unity is the most popular engine at the moment. Saying that it is the best is going a bit far. I actually think that Unity is one of the best 2D engines available. For 3D the tools are really broken for production use, and Unity is quite unresponsive about fixing them. And the renderer quality is a bit of a far cry from CryEngine or Unreal Engine, but is getting there bit by bit. Except that those two are also progressing, mostly by doing actual new research in the field.

Still, new 2D engines are welcome as Unity still has the 3D package to work with in a 2D game.
Well, isn't proper authentication a solution in and of itself? Using keys with pass phrases or requiring sudo to publish would theoretically mitigate this issue.
The article basically has two points:

Point 1) If we loosen regulations on mutual funds to allow them to behave like hedge funds (borrow more aggressively against their capital) then more of the 99% will get higher returns on their investments.

2) If we loosen regulations on medical and law professions to allow people with less training to offer more services, then more people will have better paying jobs and people will save money.

Let's address Point 1 first; most of the 99% don't have investment accounts of any kind. Most of those that do have only retirement accounts. This deregulation isn't likely to create much increase in wealth for the 99%, but it does present a great increase in risk. Allowing mutual funds to borrow more against their capital can lead to another 2008-esque meltdown, only this time instead of mortgages it will be retirement accounts that collapse. Lovely.

Now for Point 2; again it's about risk versus reward. There may indeed be services that nurse practitioners could offer, or legal technicians instead of actual lawyers, that they currently cannot offer. But it's a matter of where you draw the line, who do you trust to draw that line? And are we sure that that this isn't just a short term gain?

A large reason nurse practitioners are cheaper than doctors is that they don't need the same extremely expensive malpractice insurance that doctors do. But if they start providing more services, then they might and your cost savings go away.

And in both of these fields in particular, there's a reason you have doctors go through such thorough training before they start providing medical advice, or a lawyer does before providing legal advice; because the cost of fuck ups can be enormous. If nurse practitioners start writing prescriptions and their lack of training leads to bad mixes of medication the malpractice suit would come immediately.

Regardless, both of these suggestions are mere drops in the bucket compared to the vast gap in increased earnings between the 99% and the top 1% (or worse 0.1%), and in no way would create meaningful impacts on people's lives. Let alone addressing the root issues that really lead to the monstrous differences between worker and executive pay levels at many/most companies.
I suggest you look at using a python like language that transpiles into javascript. For example, https://github.com/kovidgoyal/rapydscript-ng which supports iterators/generators on both ES 5 and ES 6 runtimes.

Using a python like language greatly eases my pain as a primarily python developer that has to code significant amounts of javascript.
Agreed. I think it's a great coup that the truly powerful have managed to shake the narrative to the 1% rather than the 0.1% or 0.01%, thereby adding significant noise to the problem framework.
You are assuming a government is needed for the rich to get so powerful, when it is not. The rich had even greater political power under feudalism, when government was far more symbolic than real, and under weak governments (e.g. the US in the second half of the 19th century). If now significant amounts of political power are mediated through politicians who need to be persuaded, weak or nonexistent governments allow this power to be exerted directly, in pure and unmediated form.

If anything, democratic governments are able to curtail this power somewhat, though obviously not keep it in check entirely. I think that the US is indeed unique in the levels of power it affords the rich precisely because its central government is weaker than in other Western democracies. The freedom companies like Google have in the US is getting closer to direct, pre-government political power, as opposes to modern, mediated political power.
For other stories of X => Go rewrites, I started keeping a list at https://quicknotes.io/n/vzb7-rewritten-tales-of-rewriting-s
Sounds like all you need there is a compiler (people already use minifiers, right?) that would include or inline the used functions as appropriate and the cost would mainly go away? Or add in the "fetch this version from CDN" library loader code if it's a stdlib we expect to be cached and used by many js scripts.
Right... So add system/integration tests.

After all what you really care about is the behaviour of the system. It can be counter-productive to unit test pieces of legacy code because you may end up refactoring things at a higher level and breaking all your unit tests.

If it's clear that a piece of the legacy system stands on its own as a "unit" and has reasonable interfaces then by all means add unit tests to that. The biggest value though IMO in a "legacy" system is to add system level tests. Those are often easier to put in than unit tests, will catch problems involving multiple components, and will teach you about how the system is supposed to behave.
you could also have 1 library that depends on 50 different libraries, where you trust somebody to lock and update them responsibly
This is brilliant advice. This whole unit test madness needs to stop.

This post advocates:

1) unit test everything

2) complain you can't change anything without breaking a lot

3) complain that the program doesn't work even when the unit tests say "it should".

Well that's pretty much the expected result, isn't it ? Of course unit tests break if you change a method, even if the resulting program works better. And a built program doesn't work if all unit tests pass ? Well that's just not what a unit test tests ... so of course it doesn't.

An alternative tactic could be:

1) understand the problem domain. Writing an administrative system ? You should be a better accountant than the worst accountant that works in that department. If a feature request comes in, and you can't answer "why do they want this", it's time to spend some time in their team.

2) get an integration test. Something that emulates the software doing what it's meant to do at a large scale with as many real components as possible. E.g. an administration system should just be asked to run an administration, and have the result checked. The result should be checked in the sense that it should match what the accounting handbook says it should say, NOT if the code worked as expected.

You should try to do realistic things. E.g. have the test read the production database, and then enter the first 50000 customers into the test in a random order, constantly doing things like getting a customer balance in between. Insert 10 test customers and see how their accounts evolve and if this matches business rules. Check if the total system still balances out to zero at every point. Have it load the system, demanding it performs at a minimal acceptable level.

3) change things.

4) find out what breaks on a functional level. Get a report that when adding the current customer list one at a time to the software, 5 weren't in the database after entering them. Fix.

5) Run the integration test again. It passes.

6) Confidently go to your boss and declare this software will work. You can say that, because you just have demonstrated that it works.

Some bad programmers hate this, because it finds problems unit tests won't ever find, and won't tell you where the problem is. They don't help programmers that don't understand what the program is doing. They don't directly report why things are happening. They won't let developers get away with "I just changed the part I understand", and don't let them mark the bug as fixed after that. Entering a new customer takes 50s after your field addition change ? Integration tests will find this, and create an easily debuggable situation. Integration tests will catch that code that is multiple directories and modules apart, maybe even separated by an RPC won't cooperate. Integration tests, in short, tell you that the program does what it's built to do.
I hope to get a card for the ODROID and run some of these tests again... Should've ordered it with my initial purchase so I don't have to spend another $7 on shipping!

Judging by the built-in eMMC on the Orange Pi, it's a substantial I/O boost, at least 4-8x faster than even the best microSD card.
That list can easily be made longer. Off of the top of my head I know that there are many more projects which have switch languages to Go. What they say most of the time is (from the article):

Since our transition to Golang we haven’t looked back. ... we’ve begun the process of modularizing our code base and spinning up microservices to handle specific roles in our system.
Blind fish that crawls on land holds clues to evolution
1st thought: next Skype

2nd thought: 4 cameras and some space required

3rd thought: command-w
Stephen Fry's argument against the Catholic church
The. Democratic. Party. Is. Moving. Left.

WTF?

Nixon was more liberal than Clinton. Maybe even Sanders. He was also a paranoid criminal, but hey ;)
Similar problems exist in most package management systems. registries that have a manual review process mitigate this danger, but there's still always a risk of malicious code getting into the world.

Having said this, we'd like to make exploits such as those discussed in #319816 as difficult as possible. We're exploring supporting new authentication strategies: such as 2-factor authentication, SAML, and asymmetric key based authentication (some of these features are already available in our Enterprise product, but haven't made it to the public registry yet). npm's official response has more details on this subject:

http://blog.npmjs.org/post/141702881055/package-install-scri...
Absolutely, but also as barrkel points out, talking about income rather than wealth, which is much more important - referencing Piketty while purposely failing to address his actual thesis, which was almost wholly about wealth rather than income: r > g
That's because it isn't. It is taxed better in nominal terms because it ignores inflation. If you bought a stock for $100 and sold it for $110 in a year, in nominal terms you made 10%. But $110 in a year isn't worth as much as last year, and in real terms you probably made 8%.

There is a reason that short term capital gains are taxed exactly the same as income.

In the 2015 top tax bracket of 39.6%, capital gains is taxed at 23.8%. That's a 40% discount, which (unsurprisingly) is long term equity capital appreciation minus long term CPI trends.

This discount should be extended to all forms of savings and investment income too (e.g. interest and bonds), but that's another topic.
> since our single written source code is often executed on different environments and browsers

That's still a lot easier than writing portable C has to support variations in environment, compiler (w/ varying interpretations of the C standard over several decades), linker, make/build tools, CPU architecture and byte-sex (big-endian vs little-endian vs middle-endian), pointer sizes and alignment rules, integer sizes and alignment rules, incomplete and occasionally broken "standard" headers, and many more inconsistencies.

And that's just for a simple system daemon or command-line tool. If you want a GUI, that's another giant mess for potability.

> it's silly that we web developers should spend time to recreating basic wheels

Of course. There are many solutions to that problem that don't require builds that depend on network resources controlled by 3rd parties.

> JavaScript language itself is fundamentally flawed and the core APIs is a mess

While that's debatable (worse platforms exist), it also misses the entire point. Nobody is saying that sharing the code for left-pad is a bad idea. Wrap it up properly into an extended-standard-library and distribute it with node/etc.

What is conspicuously missing is any discussion at all about the costs of depending on 3rd party libraries. Adding a network, 3rd-party dependency to your build or deploy process is a huge risk that at the very least needs to be justified.

Note that I'm not saying that using 3rd party libraries is bad; I'm saying it has a cost paid in additional risk. You can decide if that cost is a fair exchange for the benefits you gain from the library. Just remember that humans are terrible at evaluating risk, so it might be a good idea to limit how much risk you take on.
Learning how to write good code takes much longer than just writing crappy code.
It would scare you to know that OnStar can be remotely activated without the driver knowing, wouldn't it?
I agree, it's a work in progress.

If you have more links, I'll be happy to add them.

I have a much longer list of companies that use Go (https://quicknotes.io/n/1XB0-companies-using-go) but it's harder to find descriptions of rewrites than find out who's using Go.
Part of the argument here is that the top 1% has access to investment classes that have high yields and and which are not available to the remaining 99%.

There is one obvious, government mandated reason that the 99% don't have access to high-yielding investments such as hedge funds: Investors in these funds are required to be accredited investors. This means they must be already wealthy by law. For example, while researching I've found a hedge fund that makes small business loans and yields 11% with no risk to capital. But in order to invest, one must be accredited, which means they have $1,000,000 of net worth outside of their home equity, or, have earned at least $200,000 household income in each of the last 2 years, or, have earned at least $300,000 last year. So by law, the 99% (I am using that term somewhat loosely here) is not legally permitted to take advantage of high-yielding opportunities.

Thanks to the Web and Internet tech in general, opportunities are becoming available. For a $2,500 minimum, any investor can put money into peer lending and earn >10%.

But I believe what really separates the 1% from the 99% is financial knowledge more than anything else. It's actually a pretty involved effort for the majority of the population to become wealthy. Involved in that there is a lot that needs to be understood about earning, budgeting, saving and investing. That knowledge then needs to be applied for the long term (decades), and then one must hope that there is no divorce, illness or major college bills that can derail a well-run effort.
What book would you recommend to learn Origami?
I like ES6 myself! Though ES5 rates as only tolerable to me; I hope the standards committee manages to phase out more of the cruft over time via some kind of 'use strict'.
> You are assuming a government is needed, when it is not.

What do you propose as an alternative. We have to somehow prevent Atlanta from pumping away all of Alabama's water no (yes, its a strawman. treat it as such).
How is it superior? Simple.

How do I systematically make sure that I have the latest version of every stackoverflow code snippet? If it's a new post, it may not have all the edge cases fixed yet. So now I have to check back on each of the X number of snippets I've copied.

In the npm approach, I can easily tell if there's a new version. For prod, I can lock to a specific version, but in my test environment, I can use ^ to get newer versions and test those before I put them in production.

If the edge case of new version of a package breaks my code, I've learned that I'm missing a unit test. Plus, the question isn't whether this bad thing might happen on occasion, the question is whether this approach is, on balance, superior to cutting and pasting random code snippets into my code. I think the downside of the npm approach is less than the downside of the copypasting from stackoverflow approach.

And every moderately useful npm package I've looked at has very good to great documenation.
> capital appreciation itself, and how it is taxed much more favourably than labour.

This is very much on purpose. Capital is extremely mobile and not part of a market transaction, while most labor is immobile and constrained as a market transaction.

It is easy to take tax from a labor market transaction, and this tax is borne just as much by the capital employing the labor as by the labor itself. Taking tax from capital appreciation is far more difficult - if you put your capital tax too high, the capital just moves to a different market with better dynamics.

Of course if you go overboard with your labor regulation and tax, then other labor markets are able to out compete your own labor market, and that is even worse.

Basically: you don't have free reign to decide on these labor and capital taxes and regulations. Any policy change you make is going to have consequences. You can't just say "OK, we will just double capital tax! Money for all!" and not face extreme changes in your entire base.

I'm in South Africa and watching this unfold as the socialist government continues to raise capital taxes each year, and now faces enormous foreign capital flight and lack of investment in the economy, destroying GDP growth and pushing the more vulnerable parts of the population out of jobs and into extreme debt and poverty. Believe me, you don't want that in USA just to get rid of some mythical '1% problem' that hurts your sensitivities.
Taxi companies were using GPS-enabled electronic dispatch systems that were designed before people carried internet-connected mobile computers. They work fairly well, but became obsolete.
My new mirror for Debian
Oh, sorry. I meant the exact opposite. Government is not needed for the rich the get so powerful. I thought that was clear.
I really, really like my LG G watch R. Looks pretty much like a regular watch (I've had many people comment that they didn't even realize it was a smartwatch) I've had it for a year and a few months and worn it in the shower, swimming, etc and almost no signs of wear. It's does what I need plenty fast and gets out of the way the rest of the time. If you're in the market for a watch check it out (or the newer Urbane).
I do not think the US is unique, indeed I would say that all modern western countries suffer the same problem.

The elites were closet supporters of fascism until they weren't. Then we had this anomalous period from the end of WW2 until the early 1970s when the Keyensians were dominant and governments pursued full employment economies via fiscal policy. The elites really can't abide sharing with labour, and capitalised on the early 1970s inflation/oil shock to promote their essentially neo-feudalist policies in the guise of neoliberalism/monetarism. The narrative of how all this came to pass is largely forgotten by mainstream economics, but there is an excellent series of posts, if dense at Bill Mitchell's blog[1] that cover this, and is much better than my crude paraphrasing.

The logical end-point for rentiers is feudalism. Without communism as a viable alternate force, I think they are seeing how low that floor can go.

[1] http://bilbo.economicoutlook.net/blog/?p=32776 Part 10, 11 and 12 are particularly relevant
well, computers do not stop a microsecond upon any name. They consider them in digits anyway. What fails in certain cases is logic of the executed programme, and by no means its a program failure. It was management failure to ensure edge cases have proper workarounds.

I still suffer when LLOYDS online bank cannot accept my long name in certain forms, stripping the last 3 chars.

During my US time, I met no systems capable of storing and displaying Eastern European diakritical chars.
No, this is not on purpose. It's simply a fact of tax being measured in nominal dollars, when capital appreciation is really denominated in real terms (i.e. after inflation).
The Dead Sea effect (2008)
Others like Apple actually deliver their products, and they work exactly like advertised. Microsoft is well known for announcing and promising products/vapourware years in advance. Like the HoloLens Minecraft demonstration at E3 2015. What a betray to the public eye it was. HoloLens has for technical reasons a very narrow field of view, the 3D content is only visible in a small area of the view, and cannot deliver the high hopes that were faked in the E3 demo. In the end it's just another augmented reality glass in prototype stage that at the moment fails to deliver and general public would be very unhappy with it. To prevent negative reviews of their demo unit Microsoft of course selected the audience carefully, so you will find just a few objective articles that mention the current problems like the incredible small field of view. But don't fall for the PR hype, they have a lot of money to spend, without trying it out yourself.

What people also always forget, because they fail to mention it, is the high amount preparation to set such a demonstration up. You need a 3D laser scan of the room and all objects, everything has to be static and shouldn't be moved. Than you need several high precision tracking devices connected to a central computer. The augmented reality glass ("HoloLens") needs to be connected via cable as well, otherwise you get those ugly video lags (seen in the clip). And you will see even the girl often just half of the body if you are standing next to her, because the glass shows only in a small area in the center the 3D augmented graphics as overlay (semi-transparent), and around that area you see your normal view through the glass without the 3D. So it's very annoying that you have to turn your head the whole time to directly point it towards where you want to focus, otherwise you see nothing of relevancy in 3D at all. It's bigger problem than with virtual reality glasses that show a dark background around the visible area (if at all). So this technology isn't new, but to get it ready beside very rough prototypes that are of little use for general public, it will take another 3-5 years, that's for sure.
The analysis is broken by the focus on the top 1%. They should be looking at the top 0.1%, or smaller.

It's absurd to put together hedge fund managers making $30 million a year with the established doctor who works two blocks from your house making $250k. These are entirely different phenomena.

You can see it by the section where they realize, shockingly, that the most common workplace among the 1% is the doctor's office. Well, duh. That's what makes it so clear that the 1% is much too broad of a target.

When people (innumerately) rage against the 1%, they're not thinking of real estate agents and local doctors and lawyers and dentists and university or hospital administrators. But that's who the 1% is.
Add new voice commands to Cortana
You should definitely check out Jenkins Job Builder - http://docs.openstack.org/infra/jenkins-job-builder/. It lets you store job configs as nice yaml files which can be checked in to version control. It's what openstack uses to manage jobs for the many many openstack projects. I've been using for a year or so at work and highly recommend it.