skysight-inc/HackerNews huggingface dataset:
AKA stage separation.

The first stage must provide a lot of thrust to get into lower gravity, so it's quite heavy with fuel and has 9 engines. After the fuel in that stage is expended, the rocket splits in two, dropping that first stage back to earth. The top half of the rocket contains additional fuel and whatever payload the rocket is delivering (including potentially an additional stage + engine) and is powered with a single engine.

Here's an older video showing the separation:

https://www.youtube.com/watch?v=p4lOJjKGoIY#t=193 (Goto: 3:15 if the link doesn't work)

The first stage that drops off is the one that SpaceX is attempting to recapture. Historically, that stage just lands in the ocean and is either scuttled or must be extensively cleaned and retrofit in order to fly again. SpaceX figures if you leave a bit of extra fuel in the tanks, you can land it vertically at the same site it took off from, and save yourself the time and expense associated with cleaning and retrieving it.

This would be very valuable since the rocket engines are typically the most expensive components of a launch, and the first stage has 9 such engines:

http://i.imgur.com/QzrPePS.png
Yes, the result is a bit unexpected but it works much better than other "more traditional" approaches. I mean, it's really "at a glance" that I can find the strongest news.

As for the "Hyped News" name, I don't think negative is inappropriate, take "Git" for example. Instead, amount of points and comments can be at the same time an indicator of importance (mostly points) and controversy (mostly comments). In either case, the leftmost news end up being those which people are more excited about.
Google Glass head moves to Amazon
Interesting. When you say over rice, is the served rice hot enough to partially cook it? I love a raw egg over Korean style 'banfan' where rice is cooked in an iron bowl, and raw egg and beef / fish are mixed in at serving time (at the table), together with salad style vegetables.
-----------↓
up to |-----→ more than?
The CIA Released Their Style Guide, and It's Absolutely Fascinating
Yes! As someone who never intentionally hits the snooze button but does it accidentally all the time, snoozing should never hide the option to turn it off.
It's also incorrect; he says he started it about four years ago, though it was just him for a while.

> It's a "why-bother?" language rather than a "ack, no!" language.

The thing is, what is the alternative? They needed easy ObjC interoperability (all the APIs and third party libraries are in ObjC, and will be for a long time), and thus a compatible object model. That would knock out most alternatives on its own. Even if they were willing to compromise on that, and go with more heavy-weight interop, they'd basically be looking at adopting Rust, which isn't finished, or maybe D.

EDIT: On the age thing, by the way, it's also reasonably clear that Swift isn't finished. It should be usable by the time Xcode 6 goes out of beta, but ObjC isn't going anywhere anytime soon, and I expect Swift will continue to evolve for a while yet.
Twitter Usage By S&P 500 Companies
I don't think this is quite the right attitude but I still agree with the basic concept.

If you are building a high-end video game (my field), garbage collection simply makes the user experience poorer than it would be otherwise. It is not some invisible implementation factor, but in fact affects the output in the form of stuttering frame times all over the place.

Good luck trying to do a VR game with a reasonable amount of stuff on screen with a GC running (you need to be between 75-90fps times 2 eyes. And every time you miss the frame deadline in VR, it is not just that the game feels worse, but it disorients people and gives them headaches and nausea.)

Every time I pick up an Android phone and try to use it, I want to throw it out a window, because it is all stuttery and janky. I presume at least part of this is because of GC.

I think this is another occurrence of people improperly weighing obvious benefits versus hidden costs. The obvious benefit of GC is you don't have to manage your memory so much, maybe. (I say maybe because when you start saying that GC performance is not good, the answer is always thinking about memory management in some way in order to reduce load on the GC. "It's a really great car as long as you don't drive it very much.") The obvious benefit is there, but there is also a hidden cost in terms of performance and solid-feeling-ness, and that cost is really pretty large actually. The theory has always been "pretty soon now GCs will get better and this will go away", but this has never happened. I went to college in 1989-94 and used to design GC'd languages as a hobby, so I have witnessed a couple of decades of this.

As a productive working programmer who writes a lot of code that does complicated things, I do not find the memory management to be a large part of what takes my time. If I were to pull a not-scientifically-derived number out of a hat, I would say it takes less than 2% of my time. To get a 2% improvement in productivity, but to pay for it so heavily ("well, there's a class of results that are simply impossible for me to achieve now because the GC might go off at any time"), is just a really bad tradeoff.

I am sympathetic to the idea that some paradigms of programming (functional, etc) are harder to do without GC. Exploring those ways of programming is a good reason to like GC, but given that functional programming is not really quite here yet for most classes of large and demanding problems, well, it's just a very different world from the one I need to build software in today.
You certainly can just write your html/CSS/js and upload it to your favorite static hosting provider. The command line and IT stuff are just tools in the toolbox. Some tools will help you write more sustainable code by managing your dependancies, or running your unit tests, etc. I usually don't bother to invest the time in learn a new tool until it's clear that it will solve a real problem for me.
Not the PowerPoint, but likely the copyright over parts of it. Presentations may be self-running, embed fonts, contain graphics, or simply use templates whose copyright Microsoft owns.
Interesting service. I've seen other places doing the same, and I really should brush up on my IPv6 knowledge..

As a side-note; I'm getting mixed-content warnings when accessing your website. You have the PureCSS framework included with a http link, instead of https. yui.yahooapis.com doesn't support https, so you need to host it yourself to get rid of this warning. You also have a picture hosted on imgur.com, which does support https.

Maybe consider updating your links to not include http/https and just use :// instead?
I vote for learning lisp first. Lisp is nice in that it is not married to a paradigm. Sometimes a stateful solution is the ideal. Although not part of the language, the interactive environment (slime) coupled with manipulation tools (paredit) make lisp feel like an extension of your fingertips. It's hard to describe.

Haskell the language is powered by the tears of the gods. But it may not have the world class tooling you get with lisp.
It seems to me that swift is about as good as the other trending languages around (rust, go) as well as the nicer older languages (c# and um...) which is plenty nice. It's not going to convert erlang, haskell, or ocaml users. Now if apple does open source it down the road it could be truly wonderful. C#'s success cross platform, thanks to mono, has been largely despite microsoft.
Well, precisely. But there are a number of existing languages that would also be better than objective-c. And they had the benefit of pre-existing.

Like with C#, a language "officially sanctioned language for the ... ecosystem" is not going to be a radical experiment, it will reflect proven wins.

So it seems that apple made the decision that the benefits of rolling their own take on the current state of the art outweighed the costs associated with rolling their own.
Now hook this up to your A/B test variations on a few components...
Relevant paper: Queues are databases, Jim Gray

http://research.microsoft.com/pubs/69641/tr-95-56.pdf
THE BASIC HEALTHCARE TRANSACTION
Yup, Wired is still trying to generate hype for languages they don't understand.
Thanks for the explanation. what would the impact be if they had a different seed, would the maze be really drastically different? Or could it look more like the 2 mazes in the original post, with only a few walls different and mostly identical?
Seneca on Gathering Ideas And Combinatorial Creativity
Swift is a neat looking language. I haven't gotten to play with it yet, but I have read Apple's "The Swift Programming Language" cover to cover and I come away with a few concerns.

My biggest issue with Swift is that there often seem to be too many ways to do things. I'm fine with having options, but when there are literally 4 or 5 different ways to accomplish the same things it's going to require development shops to come up with rigid standards about how to do things. Many shops aren't going to know that this will be an issue until later, when trying to integrate the work of different developers / teams on a large project.

The upside of this level of flexibility is that it allows you to quickly port code from nearly any language into Swift since it supports the features of almost every modern language. The downside, of course, comes when starting a new project: you have a lot of decisions to make about how functions will be called, objects instantiated and referenced, etc. If you don't make those decisions up-front, peoples' preferences will take over and you'll get a lot of spaghetti code. I'm not looking forward to starting a project in Swift, that's for sure.

From a technical perspective, I have no complaints: Swift is flexible and powerful without being weighed down by the kludges that Objective-C forced you into. But I definitely see small dev shops having a big advantage with Swift in the beginning: it'll simply take the big guys too long to get their act together.
Why you should think of a passive UX for your next app
I wonder if the original uses a word closer to "mark" than "label"? As it stands, it kind of reminds me more of the end of "Do Androids Dream of Electric Sheep (Blade Runner)" by Dick -- where Deckard finds what he thinks is a wild animal, only to turn it over and discover it's branded and is an artefact after all...
Why you should stop taking people's money
Launch webcast: https://www.youtube.com/watch?v=lbHnSu-DLR4
No a has the value [1,2,3] still in that scenario. Copy on assign semantics is for constants and mutable variables.

Just tested in the playground:

var a = [1,2,3]
var b = a
a == b // true
a === b // true
b[0] = 10
a // [1,2,3]
b // [10,2,3]
b[0] = 1
a == b // true
a === b // false
a // [1,2,3]
b // [1,2,3]
Blue Bottle Coffee - http://www.bluebottlecoffee.com - Bay Area (remote OK)

You’ll be helping our growing digital team build amazing experiences for lovers of coffee around the world. We craft easy-to-use tools that allow our guests to shop for coffee and merchandise online, learn about brewing coffee at home, and share their coffee-drinking experiences with friends and followers. We also build powerful automated tools that magically help our production teams deliver fresh-roasted coffee to the right person, at the right time.
We use the following technologies to make these experiences real:

● Ruby and Rails (latest versions)

● HTML, CSS, and Javascript

● Postgres

● Memcached, Redis, Resque

● Heroku, Cloudinary

Our digital product team is small and thirsty for meaningful collaboration. On a daily basis, you’ll get the chance to work with world-class engineers, designers, and product managers. We build and push new features with confidence using automated testing frameworks to verify our changes and release to production daily.

You’ll have a chance to encounter some or all of the following fun things: online consumer eCommerce experiences, automated tools for manufacturing / production / roasting, recurring billing systems, email marketing, analytics, tools for our quality control team, retail point of sale systems, and mobile applications for iOS and Android.

More details / apply here:

http://www.proven.com/jobs/view/13979
There is also the component of being sad and not knowing why, while you work on what you think is interesting and important.

I remember reading how Feynman was unhappy with his work and then chose a seemingly useless but fun and interesting problem to solve - the physics of plate wobbling (If I remember correctly, the relation between the wobble rate and spin rate of a plate that has been tossed into the air).

His colleagues were a bit confused as to why he would do this, but he had fun and his love for physics was rekindled.

Some years later the mathematics he derived would be used when the first satellites where launched and wobbled as they spun, the wobbling not being desirable. Not bad for useless and fun work!
So, it's like mongrel2, but a bit worse: AMQP is centralized, unlike ZeroMQ.
This is cool, but the naming is unfortunate as Polyglot is already a somewhat popular library for doing internationalization in Javascript: https://github.com/airbnb/polyglot.js
OS X is slow, I already knew that and have experienced it first hand.

What is more interesting is the performance boost with Linux 3.16 instead of the stock Ubuntu 14.04 Linux kernel. Can anyone explain why this is the case?
That's not a valid comparison for generated mazes, is it? Unless the algorithm was really just choosing randomly, some edges are far more likely to occur than others.
I was thinking why RabbitMQ and not ZeroMQ? just for my knowledge
Public Records Request: CIA Cafeteria Complaints
Virtual Panel: Real-world JavaScript MVC Frameworks
Help the Honest Politician Crash the Most Expensive Senate Race of All Time
I thought of Polyglot by AirBnB when I first saw this post, https://github.com/airbnb/polyglot.js
Garbage collection is quite similar to view maintenance in databases (or more specifically reason maintenance / truth maintenance). Especially the fact that they found a least fix-point formulation of the problem hints at strong similarity with computing and maintaining fixpoints in deductive databases - that is computing and maintaining materialized views from some base facts and rules (a distinction that does not need to be made; base facts can be seen as special kinds of rules).

In view maintenance, there are various counting algorithms known since around 30 years - for example the PF (Propagate and Filter) algorithm, or DRed (derive-rederive) algorithm. One difference is that in garbage collection you always have the whole graph: edges and vertices, while in view maintenance you typically have only the vertices. That gives rise to the "proof traces" method of view/reason maintenance where you build up the whole graph and keep the edges even though they are useful only for maintenance (or for explanation).

The distinction of tracing garbage collection vs. reference counting garbage collection could be also seen as sort of analogous to the difference between forward chaining and backward chaining in datalog or rule systems in general.

It seems like another case where bigger awareness of results from different but related fields could help to bear fruit much faster. This paper in particular seems like something that could have been inspired by the old view maintenance research. Maybe there still are some opportunities left for transferring results from one of the fields to the other.
I think they actually added a wall and made it harder.
I'm currently putting together a data recorder for an academic experiment. It requires: GPS, Camera, Environmental data, inclinometer, and a few other odd bits. I could build up a custom system, but that is a big NRE expense for something that less than ten of will probably ever be produced. I could also use a "better" but less common developer board, but that path has its own problems. The experimenter could have stuck with a COTS solution, but the reason that I'm working on it now is the inconvenience and poor quality of the current implementation (lots of COTS stuff bodged together). Currently, they are using a lot of COTS stuff, and then putting the data together in batches. Even though it is a somewhat automated process, it remains slow, labor-intensive, tedious, fragile, etc. When I am done, I get to hand off an integrated, fully automated system that is flexible, built with easily replaceable parts, and best of all; due to the abundance of freely shared examples and documents, a grad student, or even an ambitious undergrad can take over and manage or even customize the system. Also, the rPi based system is much cheaper than the current system.

So, there is one pretty good use for an rPi.
I'd still buy a BeagleBoard Black instead. Better processor. Better GPIO options.
Show HN: Free, Dropbox based Visio style SaaS
The article's title is "Why I don't eat on Mondays" not "Why you shouldn't eat on Mondays". Also, intermittent fasting I fairly well researched and known for its benefits, so it's far from being a "weird advice".
We're currently offering 32bit and 64bit varieties of the following: CentOS 6, Debian 7, Ubuntu 12.04, Ubuntu 14.04. If there is a custom template you desire we can probably provide it, just PM us or drop a ticket.
+1. I will merrily skip any submission with a sensationalistic headline, together with those that read like "Why you need to stop doing X, and do Y instead". I don't know how everybody else feels about this, but I'm sick of stupid headlines on HN.

I understand they help to sell, but I decided to cut down dramatically on the amount of time I spend reading about shit some random guy on the Internet thinks I absolutely need to {stop,begin,avoid} doing, and this rule of thumb helps quite a bit.

Sad to say, I guess that the vast majority of the stuff we read won't make our life appreciably better.

That being said, one might sure find entertainment value in a certain kind of submissions.
> With Google Go, there was no real incentive to use it

I don't like the comparisons to Go in this article. I'm an iOS developer who has dabbled in Go, and I'd actually argue the opposite.

For me, there is little reason to immediately switch to Swift. I can still use ObjC, and in fact, I'd expect problems when switching to Swift.

Go, however, had many incentives to learn. Easier deployment, speed, concurrency, etc.

As usual, Wired has over simplified the argument
ah gotcha. did a ctrl-F for theft and stole, forgot to try the present tense.
I'd make your same observation. Like the parent, I'm proud of my imperative code and never used to consider memory management a particularly onerous task. I was brought up on it y'know, just a part of writing good code.

But then I started Lisp in earnest, found GC useful (necessary!) there, and more recently have gone functional with Clojure. Couldn't do without GC now.

One of these days perhaps we'll have concurrent collectors a la Azul, running on a specialized core/MMU on some multiprocessor SoC, and GC will fade into the background and nobody will care so much about performance.

Hey, I can dream.
"1. Acceptor

"2. Message queue

"3. Responder"

So, a SOA?
I love that LLVM is relegated to "the basis of swift."

Also a $100 entry ticket to a beta IDE/compiler might hinder said adoption.
>"How to spot the fake answers put there to fool you" == "how to see when an answer isn't even in the ballpark". That's a useful skill. That "context clues" thing suggests teaching students how to solve the problem in front of them, not the easy problem their mind wants to substitute for it[1].
From what this guy describes, "test prep" sounds like "educating students".

OK, sure, it does sound like educating students, IF you accept that teaching people to spot inconsistencies and trap questions in a ritualized multiple choice test is a skill that transfers to other situations. Unfortunately this is really not the case at all. It's an education in how to navigate specific public-school bureaucracy. It doesn't even teach people to navigate other shitty bureaucracies.
Happen to know of any that accept the rPi camera, or an equivalent camera?
The first models of -21 had no radar, daytime/clear air only fighters. Someone's pulling your leg.

Edited to add in later years the soviets added one of the worst aerial radars ever flown (by the USSR anyway). Roughly the same performance as a modern marine radar. Think "Lowrance 3G level" performance. That outputs about 10 watts RF. (More like 20 watts DC in, and ancient microwave equipment was legendarily inefficient, so..)

Also the ground support vehicle runs the whole machine when the engine is off for ground maint, preflight, etc, and the max continuous is like 200 amps for the -21 ground support... so at 28 volts that's about 5 KW max for an entire aircraft.

Another way to look at it is tenth of a megawatt class TV stations were never surrounded by piles of dead birds. To shoot one outta the sky would take maybe 100 times the power.

So you're talking 10 megawatts out, minimum, given ancient RF gear that would require at least 100 megawatts power input... thats 100,000 horsepower or so. Also the waveguide feeding the antenna would arc over at those power levels, whoops.

This is why nobody uses beam weapons.
> But there are a number of existing languages that would also be better than objective-c.

Which ones, exactly, would be better for Apple's purposes?
I'm not sure which you mean by "original", but in the KrazyDad version you can go in a nearly straight line from the start point to the end point, but in the Kraft version, you have to take a spiral path through more than 360 degrees around the circle. Even if they started with the KrazyDad version, that's a pretty interesting change.
Beyond the great advice, I'm struck by the supreme kindness and humanity on display in this letter--it is itself great advice on how to treat others, all the more poignant coming from a man with many other wonderful opportunities competing for his time and attention.
Xcode 6 is free, now: http://arstechnica.com/apple/2014/07/apple-launches-new-swif...
All Sapphire iPhone 6?
As the poster is also the author, the title should be	"Show HN: Impact of the New Show HN Section on Show HN Submissions"
Buying a domain may be overkill for most projects. Simply using a subdomain somewhere (such as a projectname.github.io or projectname.readthedocs.com) is likely sufficient.

By far the greatest determinant of success for a project are productive and engaged developer and user communities, and open lines of communication between these groups (where they are different).

Which communications channels are most important for your project(s) is something that can't be reduced to simple advice, and will change over time in any case. Try one at a time, invest more into the ones that have the most engagement, and smooth the speed-bumps wherever you can.
Isn't the latest Xcode beta available to anyone, developer account or no?

https://developer.apple.com/swift/resources/
You didn't have a DOS manual?
Well, we where talking about flying with a random person from internet ;) I'd think that one would want to check that someone had flown before and that this person is 'in good standing' in our society.

As to 'ivy league or big company', its an answer to the question: "will I be comfortable sharing a ride with, say, a random Stanford student or with Google/whatewher employee?". The answer is yes. Simply because I understand where these people are coming from and this is already good enough a connection.
Thanks!

Fixed all of the external content warnings, thanks for spotting that.