skysight-inc/HackerNews huggingface dataset:
I definitely agree. If only a single cryptographer would have been part of the equation, no one would have had a reason to write “Bit shifting isn't encryption” . Looking at my comment again again, I guess it was simply too short to be understood as a cinical “read it with a smile” kind of thing. Just to be sure no one gets me wrong: I surely did not want to hype any of the bad guys, nor make fun of the victims… the innocent Turkish citizens involved. Yet, I can’t help to shake my head that a Turkish governmental agency was stupid enough to use a near to “xor-by-one” snakeoil crypto thingy instead of well-vetted and security proven cryptographic algorithms and protocols. If they would have, there wouldn’t be a problem – just a blob of encrypted data. Which is why I said: “cryptographers 1 – Idiots 0”… which was merely meant to be interpreted as “roll your own crypto, eat your own poison – no cryptographer would have stepped into the stupid pitfall of using home-brew toys instead of well-vetted algos & protocols”. Hope that somewhat is able to explain what I meant with my comment. If my cynical comment was misunderstood due to its minimalism – my bad. Downvotes correctly punished me accordingly for my comment being too short to be understood upon first glimpse – next time, I’ll be sure to be clearer.
100% agreed. This is the reason I personally find YAML to be a great config alternative to JSON due to their ease of converting between the two
I feel that everybody should just be on as many lists as possible be default, and the cost of jet / air transportation would be covered by government or insurance.

With transplant cost and post op care costing well into 6 figure, a $2 - $10 grand in charter jet cost should just be absorbed.
OK this is creepy, but it's even creepier when e.g. Progressive Insurance use their Snapshot® device to do the same thing without telling anyone.
I counter with some pop science:

http://www.inc.com/john-boitnott/social-media-addiction-the-...

http://ericadhawan.com/social-media-hurts-productivity/

http://www.nytimes.com/2016/03/06/upshot/silicon-valley-has-...

As well as some economic studies:

http://marginalrevolution.com/marginalrevolution/2016/03/the...

http://marginalrevolution.com/marginalrevolution/2016/03/pro...

http://marginalrevolution.com/marginalrevolution/2016/03/how...

Someone had better teach these techies some basic finance, accounting and economics at some point. Right now when someone posts something to Facebook it's basically a dead end for further economic potential. Compare this to how the finances of the book trade worked in the 19th century and it appears as if we're headed backwards. I blame a certain kind of arrogance in Silicon Valley for thinking that "information just has to be free now"... if anyone opened up their history books they'd realize that the printing press made the distribution costs of information comparatively cheaper than the Internet. People used to make copies by hand! Then it took us a few hundred years to fully invent intellectual property as a response to the issues created by cheap copies.

All that's happened as a result of the Internet is that we now have even cheaper copiers, but there's still a cost. Facebook's operation costs are in the billions of dollars a year. That's hardly "free information". Everyone needs to realize that Clay Shirkey and CmdrTaco were full of shit so we can move on with our lives.

It's about time that some adults with some conservative tendencies as well as a functional and practical understanding of the Internet stepped in and showed these techies a thing or to about how the world really works when they're not just spending daddy VC's money.
I've always done two-phase migrations.

Phase 1: Upgrade schema for new code. Migrate initial data from old schema to new schema.

[Deploy: New code starts taking requests, writing to new schema. Old code is drained from the pool of handlers, continues to write to the old schema. Once old code is drained from the pool and the new code is validated by production traffic, run Phase 2.]

Phase 2: Catch-up migration of old data to new schema. Drop old schema.

I used Liquibase for migrations - change-sets can be tagged with contexts[1] and when you run the migration you can specify contextual information that each change-set can target (e. g. development AND pre-deployment). The principal tags I used were pre-deployment and post-deployment (which map to Phase 1 and Phase 2 above).

Schema migrations were a little harder to write but it meant that we could migrate live without impact to customers.

[1]: http://www.liquibase.org/documentation/contexts.html
We can live with many different lines drawn through the gray area, as long as we clearly separate the clear cut cases.

(Eg for free speech, America and Germany draw very different lines, but most people would be fine in either place free speech wise.)
I used to live in pittsburgh. I wish I still did but I have to live here in the Bay for work. Other than the work environment, unless you're a millionaire, this place sucks compared to pittsburgh: takes an hour to get anywhere, insane cost-of-living and sanctimonious locals who openly loathe "the tech elite" while they sit in their million-dollar ranch houses.
Celsense, Rorus, and PieceMaker are three that come to mind. There are especially a lot of biotech startups. Not as many of the consumer-web type startups that are more commonly seen on HN though.
Implicitly, that person is. But what that comment really says is, "if my government tells me they need my taxes so that we shall kill instead of being killed, that is a decision I am prepared to support."

Anyone who pays US taxes and doesn't do their utmost to stop these murders implicitly holds this belief, in my eyes.
Not hundreds of billions, but GS received $12.9 billion as part of the AIG bailout. AIG had basically written insurance policies it couldn't pay, so the government stepped in.
Meh, this is just MSN all over again. This seems to be some kind of weird cycle the Internet goes through, I'm sure eventually an open protocol will thrive...we're just not there yet.
Austin isn't even close to finishing its growth. It's currently "burroughing" out with me SoDoSoPa style mini-downtowns like The Domain and Mueller due to the awful traffic situation.

There's an issue with getting huge money still, but you can live cheap in the burbs and bootstrap to your heart's content.

If the REAL tech / hardware industry doesn't have a collapse, there will be no stopping the growth.
This is the first project I've read about that produces a visceral reaction in me: a project I'd love to see develop, but which I probably won't live to see the results of.

I'm 43 now. Let's be optimistic and say this technology is proven in the next 5 years. Then a craft is built and launched in the next 5 years. Then there's 20 years of travel, and 5 more years before the images come back. If it all worked out perfectly, that's 35 years from now, and I'll be 78 if I'm still around. What's more likely is that a strategy for sending probes to nearby stars will be clarified in the next few decades, and I might live to see the first interstellar probes launched. I will die happy that we're reaching out, but sad to not know more about what's out there.

Every year, the lasers would blast streams of probes towards new star systems. Before long, there would be probes en route to every star within ten light years. As the search radius expanded outward, data return times would lengthen to decades. But the delay might produce a lovely effect. As the centuries wore on, an expanding sphere of the universe would slowly reveal itself, in vivid detail, as waves of images returned from the stars.

I'm happy to know the universe in much greater detail than what I learned when I was a young kid. I'm also happy that others may live in a time when probes from generations before will be beaming back their first transmissions.
The target audience for the code I write is not the compiler but my coworkers and the gals and guys who will maintain the stuff after I leave a project.

So I prefer to choose a language where I can nicely express the intent of what I code. Java is a good compromise, because it's easy to follow (even if it's quite verbose and mainly stuck in the world of nouns).

C++ is hard for that. It's an extremely complex language that got extended over the years and it takes a quite long time to master, for example compared to Java.

Yes I know, C++ is more "capable" than Java but it's not efficient in the hours-spend-per-solved-problem way of things.

Yes I know, there are you C++ whiz kids out there who are insanely fast using the language. But I experienced teams using it, and in a team C++ does not scale well. Adding more and more features to it makes it a cool language, but not one which I like to use in my day job.

And I'm not sure what I'd use it for. I use Java for the day-to-day boring "enterprise" world, twiddle around with dynamic languages for the hobby (yay to the recurrence of lisp!) and for close to the hardware stuff I'd use plain C - which is a not so bad language at all. And it's hard to beat speed-wise, writing C++ that keeps up with C is possible but not trivial.

And if I'd have to look forward I'd check out rust or go or even look at some really mindbending stuff like erlang. Parallelism can't be evaded in the modern world and using a language tailored to that is a great thing. (Yea, I'm sure there also is a C++ library implementing the actor model).
Most car accidents are caused by human drivers, but purely technical solutions have still drastically reduced death rates.
Fortunately for them they received more than twice this amount as part of the AIG bailout.
Would you help me compile a list of interesting software companies in Pittsburgh? (I'm seeking to relocate there from SF but am having a hard time sourcing an attractive employer)

* DuoLingo

* Google

* Oculus (Facebook)

* ShowClix
People have to learn how to harvest power from fusion before.
It actually should not.

People using a password manager might not ever know their password. Funny things happen with password managers where history is missing, changes don't save, keystrokes break things. We can't penalize users who use them.

It's unfortunately a really messy area.

Source: was a password manager in a past life
It's an argument that gets made over and over again:

Paris: density 55,673/mi^2

SF: density 17,246/mi^2

(source: wikipedia)
Music Fans. The vast majority of people will never give Indie bands a listen and have the listening pallet of a 6 year old.

Seems harsh to blame people for their personal tastes. Maybe the product is wrong or the genre limited. Surely blaming discoverability and the like is fairer? Beyond discoverability, I think repetition is very important which is where labels and links to radio/etc are useful.
Meh. I don't use semicolons at all in JavaScript, except in for loops. I've never once had a bug from it.

I'll stick to caring about he myriad issues that actually cause quality problems for me rather than worry about obscure theoretical bugs.
The transition away from cloud-init and YAML is really quite odd to me. Nobody enjoys editing JSON files. Forgetting commas, no multi-line strings, no comments, escaping characters in strings, etc. Just reading the documentation of ignition should be enough to illustrate the pain it is to manage multiline content for unit files in an JSON string.

But why abandon the cloud-init format in general? Again, why would somebody want to learn a new configuration syntax. Using CoreOS already requires you to know and use systemd units (most other distros this really isn't required knowledge), so that adds two steps to users learning/using CoreOS.
Golang's compiler was originally written in C++, so people are actively avoiding your advice.
I'm mainly just talking about the density -- many more people fit into less space than in San Francisco. And its both an option for us to build up, and build in -- we could close down some of our wider car-oriented streets and build walking/biking oriented roads.
Lots of nascent demand for pro photo services. Culture is becoming visual on an unprecedented scale. Two quick queries:

1. How quickly do you think you could scale this globally? Customer requests a shoot on a volcano in Greenland for example ;)

2. Why not provide a full service solution? That is not just the photographer, but for a fashion brand shoot for example, all the models, hair, makeup, location, catering, legal clearances and the other 100 things I am not anticipating ;)
> people in the US still perceived Pittsburgh as a bad place

They still do.

I'm originally from the area and when I mention this everyone thinks I come from either a Deliverance-like backwoods or a bombed-out Detroit-style factory town.

No one takes me seriously when I call it The Paris of Appalachia.
Well. Here's the real question. When a natural disaster coupled with a human engineering disaster causes massive loss of life, destruction of property, and land rendered dangerous and uninhabitable, why is it that blame concentrates exclusively on nuclear power compared to other alternatives?

Coal power causes millions of deaths a year. It causes hazardous living conditions in some of the most populous cities in the world. The coal power industry depends on mining which endangers the lives of miners, with many deaths every year, and wrecks the environment. There are huge swaths of land that are barren and uninhabitable. There are giant piles of mine tailings and giant lakes of sludge scattered around the world. Nobody lives on that land, nobody can because it's contaminated and dangerous. There are places in the US where the risk of dying due to the effects of coal power are 4x higher than the national average murder rate. And there are places around the world where it's much, much worse.

The difference between nuclear power and other sources of power or other engineer works is mostly that the hazards of nuclear power are still seen as unusual and frightening, whereas we've simply grown comfortable with those of other forms of power.
> suitable for prototyping like Python or Javascript than Rust, and then port it over to Rust

In all my years, every time someone prototypes, it either never gets used, or it does, its successful and then it never gets rewritten because there's no time for technical debt.

Now I prototype in the language I plan to use long term, but what that means is stubbing out sections, or putting in todos if there are spots that can be better. The prototype should be able to scale into your real application, otherwise your just building something that will haunt you.
Pandora is actually the site that was borne out of the music DNA project.
So how exactly does launchdarkly help with feature flags becoming a junk drawer/tech debt? I can see how the intuitive ui would help in general, but what I was really expecting to see was:

* A way to manage dependent feature flags, because god knows once those non-technical(and technical) users have switches they can throw, they're going to ask for/build features that are dependent on each other in subtle ways

* A distinction between a true feature flag and what I call a "release" flag, ie, a feature that's not yet fully built, but that will not be optional once fully built and released, so its flag goes away at some point.

Also, btw, do you have an API for the flag creation itself, not its use, ie a addFlag()/removeFlag() API?
And what exactly happens with reflected laser?
Hah, guilty as charged. I take it you're also an ex-kuron?
I wish they had more interesting data sets.
I dunno man, I can't say any of this reads as encouraging: https://en.wikipedia.org/wiki/LGBT_rights_in_Texas
> you can simply NOT tell your old employer that you got a new job.

You also have to avoid:

1) Telling your old co-workers

2) Mentioning or updating anything on social media. Even if you're not "friends" with old co-workers on e.g. Facebook, that information could still be leaked.

3) Giving any sort of talk where your employment might be leaked

4) Being at an industry event where your employment might be leaked

5) Being named on the company site, and thus your name showing up on a simple google search.

If your old employer is vindictive (which could be one reason you left), there are lots and lots of ways for them to find out where their former employee went to.

Being subtle will probably only keep your employment status hidden with the sorts of employers who aren't really making broad non-compete clauses to begin with (i.e. employers who don't care).
The Lost 1984 Video: Young Steve Jobs Introduces the Macintosh
I am assuming the facebook app doesn't use this?
A silly question for the insiders: what does "teal with cameras" mean?
Journal of Web Semantics: 25th Anniversary Special Virtual Issue
2-3 years? Try 10 or 15 or more. Any serious code stick around for a long time.
Appeal to emotion actually.
Yeah, serious +1 to this. I'm amazed by the usage of ioutil.ReadAll in popular Go libraries and tools.
1000% = 10 days per year
Recently went to a one-day festival at a winery. All sorts of genres represented by very capable musicians across the day and evening. Every act played original music except one guy (Max Savage) who, though usually playing his own stuff, covered all of Paul Simon's Graceland.

The crowd was biggest and most engaged for Max Savage. After hearing 10ish songs that I knew back to front, the next act of originals felt very flat, despite being the more well known artist.

It made me very keen to hear Max cover other full albums, even a festival of nothing but interesting covers. Not cheesy covers, but cross-genre tweaks, etc. I'd pay to attend that gig sooner than I would an event of purely originals that I didn't really know.
D is a better language than C++.
Thanks for the clarification.

These pages make it clear how it works and it seems reasonable:

https://help.backblaze.com/hc/en-us/articles/217665398-Backi...

https://help.backblaze.com/hc/en-us/articles/217664898-What-...
They also received $12.9 billion from the government as part of the AIG bailout, more than any other entity.
Capitalism is people working hard to set up tolls so they don't have to work hard anymore while people who actually like working and creating things of value day after day get 20-99% of the value of their work skimmed off the top.
I haven't. I will ask around to see if any of them have time.
That's a big "yeah but".

You can't rate limit the io. That's huge and the percona tool and LHM offer ways to keep io under control. Along with that you have to pay attention to the live schema update matrix in the docs; many things will upgrade with out locking but require copying the table and this will blast your IO.

In addition even with the tools some changes require exclusive table locks. It needs it for a short period of time but if it can't get it because of a long running transaction , queue of transactions, and etc it can block everything up.
These people are obviously very passionate about their project, and they're moving forward on something they want to do. If you're so passionate about those projects you mentioned, start making them happen!

Don't sit around complaining about people who are "doing" stuff because they're not doing the stuff you want them to be doing. Get out there and do the stuff yourself!
YAML is good for simple configs. As the article says, JSON is much easier to programmatically generate than non-standard YAML. You still can store files in YAML, but compose and convert them into JSON in user data.
Hopefully this helps (correct me if I'm wrong, I'm still learning about neural nets):

Think of the whole neural net as a function:

input * weight = output

At each iteration, we feed in the input to the neural net. Then the neural net compares what output it gets to the correct output.

For example, input1 is 5, and the correct output for input1 should have been 2. But the neural net got 3 as the output. So it then decreases the weights slightly so it would get 2.75 next time it has input of 5. Repeat thousands of times. That's the basic idea for machine learning and neural networks.

The algorithm it uses to figure out how much to decrease the weights is called "backpropagation" which uses gradient descent. To explain gradient descent, as as a roller coaster track. Imagine the roller coaster starts off on a random location on the track. Then gravity takes the roller coaster down the track until it ends up on a low point between two hills and stays there. This is the new location of the roller coaster. This new location is nice because it has the lowest energy the roller coaster could find, so it stays there. (We use derivatives to figure out the slope of a curve, which then gives us the direction where the curve goes downhill).

In neural networks, the roller coaster curve is the "cost function", which basically calculates the amount of difference between the neural net's output and the actual correct output it should have got. The initial weight is the roller coaster's initial position. The new weight is the roller coaster's final position, at the bottom of the cost function curve. This new position thus gives us the lowest cost.

Note that there may be even lower valleys, but when we roll the rollercoaster it stops at its nearest low valley. This is why we randomize the weights at the beginning - to put the roller coaster near possibly even lower valleys.
I wonder how they intend for the probe to actually communicate back to earth. Flying by Jupiter... The data downlink feed from New Horizons was about 38 kilobits per second. After the Pluto flyby... it was down to 2 kilobits per second and has been decreasing the further away it gets.

Perhaps it could be done with laser? Having said that, I'd think the beams focus would be quite wide by the time it reaches earth. It would have to be both perfectly formed and aimed with absolute accuracy. (I don't work with lasers and may be off on this, so take this paragraph on principle rather than factual).

Maybe with some form of quantum entanglement? Current forms of usable quantum communication still require mediums like fiber optics as far as I understand. Ex: http://www.nature.com/news/quantum-communications-leap-out-o...

And how to keep this iphone sized device powered?
Previously, IFTTT: https://news.ycombinator.com/item?id=11379475
I really wanted to use Rust for numerical/scientific computing tasks, but it's kind of miserable for it. I didn't get hung up on the ownership things that all of the Rust zealots talk about (although I think explicit lifetimes are needlessly complicated). I got hung up trying to implement simple things like complex numbers and matrices in a way that was generic and usable. I'm sure some Rust fanboy will argue that Rust has operator overloading through traits, so I'll challenge anyone to make a workable implementation such that zA and 2.0B works in the following generics:

let z = Complex<f64>::new(1.0, 2.0);
let A = Matrix<f64>::ident(10, 10);
let B : Matrix<Complex<f64>> = z*A;
let C : Matrix<Complex<f64>> = 2.0*B;

If Rust can't do scalar multiplication or real to complex conversions, it's really not usable for what Eigen or Numpy can do. Try defining the Mul trait generically for those multiplication operators, and you'll see what I mean.

(yes, I know there are some syntax errors in the type declarations above - It's my opinion Rust got that wrong too...)

Supposedly this kind of thing will eventually be possible with the recent "specialization" changes, but I haven't seen anything that allows operators to work as above...

ps: Last I looked, there was fledgling support for SIMD on the horizon... LLVM supports that, so it could happen.
"Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is..."

A lot of it comes down to things just being far apart. We're used to the surface of the earth - a 2D surface, but space is 3D. There's orders of several orders of magnitude more room and not a lot of objects in it.

Secondly, the orbits of these objects are tracked and in a database. It's a pretty easy task to check if your planned launch path comes near anything.