skysight-inc/HackerNews huggingface dataset:
As a single data point, I recently dropped and shattered my trusty Nexus 4 and was in a market for a new phone. I was extremely hesitant about getting a Nexus 6, exactly because I thought it was way too big. I finally bit the bullet, and I instantly loved it.

Yes, you need two hands to do most things. My thumb can't reach Android's "back" button on the 6. But what I realized was that with the Nexus 4, I also couldn't reach everything with just my thumb. "Back" was within reach, but the upper right and left weren't fully. So while yes, the 6 isn't strictly as comfortable as the 4 was, the bigger screen is a minor tradeoff I'm ultimately very happy with.

It also barely fits in my pocket, so the jury's still out as to whether that makes it more prone to slipping out while seated. I'm not sure I want jeans with deeper pockets just to accommodate my phone. But it hasn't been an issue yet.

(Now if manufacturers would just improve the process they use to make these hi-DPI screens so that the color temperature isn't splotchy. My Nexus 6 suffers from a pinkish bottom half, and apparently it's not an uncommon issue for hi-DPI smartphones and non-Retina-brand hi-DPI laptops.)
I think the difference will be the Apollo crews were expecting it and it was sustained and constant.

A launch abort isn't something that you can really brace for.
Unless you ask it, git considers file moves to be a complete deletion of the file along with the addition of the file. A good way to tell git to detect renames is to use the similarity flags: `git diff -M60% --shortstat` will consider files 60% similar to be renames.
Containerisation tool without daemons in Rust
Yes they are, I believe the descriptions are just being edited.
And how will they access internet.org without a smartphone?
Music Startups and the Passion Problem
Essential Plugins for a WordPress Website
Not helpful.

Read the original article. Read my original response.

Almost as an aside -- electricity does happen to be available a good way into the night with solar thermal.

But the big point (again) is that it's not a matter of 'solar + batteries' as the only option to burning fossil fuels.
Why? Github is using it for Atom's core.
Should I be ditching node for io?
What's the rarest snowden
The world of actual programmers is NOT filled with fake programmers. The world of people actively applying for advertised programming positions IS dominated by fake programmers. That's why FizzBuzz is an effective screen.

As to your last question, a "webdev" who doesn't understand integer modulus is a fake programmer. Is it critical? I suppose it's not if your grid is never wider than one column and you never want to alternatively style rows in a list or table.
The merger of io.js and node. They're using the same package manager which is untenable when API changes occur between the two.
I did not read that article as demonizing Russia, or, really, even Stalin.
It's skewed because they consider everything above a 5" screen a phablet. That basically includes every android flagship as a phablet, but not the iphone 6 which is 4.7"
SHUT UP AND TAKE MY MONEY

(His voice is wonderful though, so maybe KEEP TALKING AND TAKE MY MONEY.)

I would pay $199 for this in a .app bundle instantly.
Irresistible:

"That is the sorry reality of the bazaar Raymond praised in his book: a pile of old festering hacks, endlessly copied and pasted by a clueless generation of IT "professionals" who wouldn't recognize sound IT architecture if you hit them over the head with it. It is hard to believe today, but under this embarrassing mess lies the ruins of the beautiful cathedral of Unix, deservedly famous for its simplicity of design, its economy of features, and its elegance of execution. (Sic transit gloria mundi, etc.)"
This is correct, and it's a source of madness.

One more thing: Cookies are limited to 4KB total due to the HTTP/1.1 specification.
This Tech Will Have You Hiking Like You’re 18 Again
Most of it is junk find and replace stuff / formatting docs etc. [1]

Pulse [2] is just a neat github feature that gives you an overview of a project.

LOC will always be a shitty metric for anything.

[1] https://github.com/iojs/io.js/commit/56e4255382ad4d2426e0346...

[2] https://github.com/iojs/io.js/pulse
How does it work with Ruby on Rails webapps?
Exactly the same experience for me going from an htc one m7 to the iphone 6 plus. Was very skeptical, but i instantly loved it.
I don't think Hadoop has much to do with core Linux HA...
A pocket-sized synthesizer changed the way I think about music
Agree. You won't catch me dead wearing something like a pair of cargo shorts. My 5s is already pushing the limit on some pockets.

> This seems like one of those trends thats driven by the manufacturers

Yep. People don't know what they want until Steve Jobs tells them what they want. Too bad he's gone.
I find it a little hilarious that the article says that by ending Patch Tuesday it would "shame Google". My first thought was how all the wailing around Project Zero releasing exploits strictly at 90 days instead of waiting for Patch Tuesday would now ring hollow. Sadly the article doesn't discuss that controversy.

Disclaimer: I work at Google, but I'm not involved with security or Project Zero.
If there wasn't a new cool kid on the block every month making last month's cool kid look like a douche, it just wouldn't be JavaScript.
Eyepiece observing with MagAO
Witness-the-economic-impetus
> In other words, bigger screens are simply trendy, and are therefore not here to stay.

Or it's not and your 'seems','maybe','would' and conditionals are just that :).
12 Ways to Define Abundance That Will Reinforce Your Mindset
I wonder if articles are being written so as not to scare off hyperlinked visitors. People are perhaps turned off by large paragraphs and want to be able to zoom in on some keywords which can be skimmed around.
6" would be too high but i agree that 5" is too low because any android flagship is 5" today.
panel at rsa https://www.youtube.com/watch?v=qzK9Mj2V6BA
I'm mostly concerned with using APIs that are only available in io.js. Doing so means I can't share my modules in any reliable way since io.js and node both use npm and I certainly wouldn't create multiple versions of my modules. This leaves me developing using only node APIs at which point io.js is nice for experimentation but I'm not sure about doing serious work for it until it's strictly an application (no module sharing, etc).

Really the biggest sticking point for me is using npm between the two. Node not supporting ES6 is also an issue as you can't write your code using ES6 unless you want to only support io.js or you want to transpile (ugh).
What features are you looking for?
> Oh right! I guess that explains why C# wants to add all the features Scala shipped with since 5 years ago.

It ships them in a usable state, documented in an accessible way without patronizing language and useless neologisms.
Twilio raises $100M; is now worth over $1B, report says
The real world partitions land and water by treating values below a certain threshold as ocean. That's not the problem.

There are tons of good terrain generators. Try Google. VistaPro, from the 1980s, is the classic.[1]

So far, nobody has built a procedural city generator good enough to generate a detailed city at ground level. This is one of the better ones, but the result comes out looking like a modern prison.[2]

[1] https://en.wikipedia.org/wiki/VistaPro
[2] http://orphancity.tumblr.com/
Oryx Design Lab: High Quality Royalty Free Game Sprites
Very exciting! It's great to see ES6 slowly rolling out as well. I've been using it with babeljs and it's been a blast.
(thumbs up!)
Joyent used to have the license on the top of virtually EVERY file in the repo for node. Someone removed all but one (6430 deletions) https://github.com/iojs/io.js/pull/311/files

I can imagine this makes up for a portion of it.
No machine learning? Really?

It seems like for every problem out there - at least some tiny bit can be solved by machine learning.

General pattern recognition (identifying peaks, predicting disk outages, etc) at the minimum seems like a requirement that will show up in the next few years.
There's a bunch of pieces. The tutorial is Beethoven's Moonlight Sonata.
So, node.js is more stable and therefore more suitable for production?
A handful of reasons (disclaimer: painting with very wide brush here, in the hope that you get the strategic picture)

* The desktop market is fragmented. Pick your poison: walled garden with crappy devtools, OSS fanatics who will not pay for software in a million years; or warezing pirates. Note that whichever you choose, your app will still end up on torrent sites ~2 days after release anyways.

* The cross-OS development tools' end results are usually sub-pair, even compared with javascript.

* Desktop usage is, and has been stagnating for a while now; while mobile usage is growing at an incredible rate. Mobile native market is also highly fragmented.

* The lowest common denominator across all of these markets is the web: develop it once using responsive design, run it on everything for at least the next decade, or so.

* People have been voting for this platform with their wallets for a while now; specifically by being unable to pirate web apps.

* The stakeholders in selling AWS are: developers (for whom command line & APIs are the critical part), and business decision makers (who are looking for easy leverage). Neither target group is particularly interested in desktop apps.

* Specifically regarding to their propriatory tech (eg dynamoDB), developing a third-party desktop tool for it is a high-risk-no-reward endavour: you either get traction, in which case Amazon will gladly oblige with an app of their own; or it won't, in which case you're out with $lots$.

Joel Spolsky put it best: "Filling little gaps in another company's product lineup is snatching nickels from the path of an oncoming steam roller." ( http://www.joelonsoftware.com/items/2009/06/10c.html )
Blasphemy?
Teespring (YC W13) Is Hiring a DevOps Lead in SF
Working on the DevOps Team...
The DevOps team focuses on creating high quality automation and deployment systems with scalability and reliability at the core. We have multiple engineering sites: USA - SF, KY, RI, UK - London, India.

The DevOps team creates continuity between all locations and boosts the efficiency of our operations. We operate in an Agile methodology with continuous integration.

What is the job?
We need someone to take our DevOps organization worldwide this year. This means building a migration plan for moving from Heroku to AWS, redundancy for key systems, DB health optimization and scaling, a business continuity/disaster recovery plan, EU Data compliance, 5 minute code deploys/rollbacks, and add support for isolated engineering environments (Docker/Vagrant) to start.

What do we target?
Someone to lead others with the ability to get their hands dirty as an individual contributor. Operating in a technology environment with strong scripting (Ruby, Python, Bash), 100+ Linux Servers, Cloud Hosting (AWS), Configuration Management Tools (Chef, Puppet, OpsWorks), Postgres and MySQL, and ROR web app frameworks.

We want people with the ability to bring new ideas to help drive innovation. Our employee philosophy: IDEAS - Innovative, Deliver, Empower, Authentic, Scrappy.

What do we offer?
- Working with talented, collaborative, and entrepreneurial teams
- Medical, dental and vision insurance for you, your family, or pet
- Liberal paid time off and 9 paid holidays
- Generous stock options
- Free catered lunch and dinner daily
- Fully stocked kitchen with drinks, snacks, and bar
- Training, career development, and meet up hosting
- Commuter benefits
- Office yoga
- Fun SOMA office with easy access to Muni, Bart, and Caltrain
- Apple computers and Thunderbolt monitors
- Social activities, office happy hours, live music, game room, and endless free t-shirts!

Email your resume to ashley.hearn@teespring.com to learn more.
Such a bummer. The only people who deserve to die like this are the writers of web hijackers and viruses, multiple times.

This guy was someone who promoted time at home to be part of the kids growing up, something most dads miss out on, still.
Congrats to the io.js team! I know there's lots going on in the node vs. io.js world/debate/comparison/everything, but regardless it's so great to see a team working on an OSS project so well.
The EIP Laser Turntable plays records without touching them
It's a dumb category. There's a continuum of screen sizes. Picking a cutoff is just silly.
Lol. No, it doesn't ship them at all yet. Why are you acting so butt-hurt?
Paytm is finally turning the mobile wallet dream into reality – in India
That's actually fairly mild, as these things go.

The Apollo lunar missions experienced max G forces of 6.5-7.2g during reentry. (The Earth orbital missions only went to about 3.3g.) See: http://history.nasa.gov/SP-368/s2ch5.htm

Alan Shepard freaking flew Mercury 3 by hand during a 11.6g reentry.

Ejections seats are 12-14g or worse.

Of course, max G is only part of the equation; duration is the other. You can handle really high forces if they aren't for long. Given the short duration and lack of need to keep the occupants awake they could go a lot harder. I'm actually a little surprised it's so gentle.
"Native Advertisement"
From my own experience and from talking to my friends, people with a 6+ seem to be happy with it, and people with the 6/5/5s keep trying to convince me that it is too big and that they couldn't get used to it. It's a bit of an odd phenomenon overall, but I'm pretty interested in how cell-phone sizing plays out over the next couple years.
>If processing power increases, it increases for all players.

I'm not sure I follow. If processing the block-chain is cheap enough that everybody can do it, I see no reason to depend entirely on centralized mines. The little guy can still participate, and there's bound to be more little guys than big guys, especially if bitcoin clients do a bit of mining themselves.

Sure, it's profitable and large-scale operations will probably arise, but that's distinct from centralization, per se.
I graduated 10 years ago and never used calculus, differential equations, linear algebra, or physics in my job.

I'm not saying this to say they aren't useful. But does anyone find them generally useful for their job? If so, what for? I'd like to know what I'm missing here, if anything. I don't want to go through a refresher just to forget it in another couple of years.
Maybe. Undergraduate biology typically sticks to the same set of model systems (Krebs Cycle, for example) even across different courses (microbiology, biochemistry, etc.) in order to reveal deeper levels of complexity within some focused context. You never really get all the edge cases at once though.

I think what most biology undergraduate programs need to add - and many have - is the equivalent of a "Programming Languages" course which adds a 'state of the diversity of the field' dimension to the usual micro-/macro- dimensions. CS (speaking very generally here) tends to either drill down into low level computation or up into high level abstraction, and Bio tends to drill down into sub-cellular/molecular or up into social/behavioral/evolutionary. In CS, a course in programming languages tends to offer a nice survey of the diverse extents of the field, and a similar survey of all of life's vast biodiversity would be a welcome addition to the undergraduate curriculum, imho.
Excuse the unintentional typo pun! And the missed 's' on 'ranges'. And the double 'though' in the edit. For the first two at least I can blame low batteries in my wireless keyboard...
Housing.com CEO Calls Investors 'Intellectually Incapable'
I couldn't believe that the Waldstein Sonata (first movement) was an option! I've listened to that piece I don't know how many times by so many different pianists (favorites are Wilhelm Kempff and John O'Conor) but I'm not a pianist and could never dream of climbing that mountain. And I tried it and of course made a dire mess of it but it was still SO MUCH FUN!
Everyone aboard will be strapped down in a nice flight couch. It probably won't be pleasant, but will be easily survivable--which sitting on an exploding rocket, the alternative, would not be.
Personally I would wait but you can certainly use io.js as you do node. I commented elsewhere in this thread about my whys so I won't be annoying and repeat them here but if you want to experiment or need some bleeding edge performance in some of the areas that io.js is faster (the newer V8 isn't faster in all situations) go for it otherwise I'd stick with node for now.
Why wouldn't node.js have more contributions? It's the official product and backed by a neutral company (Joyent).

Just like Sun does to Java, Microsoft does to C#, Google does to Golang. It's beneficial.

Joyent is a company of merit that stays out of politics. Integrity trumps popularity, sure it it can ruffle feathers time to time. Why not just enjoy the support and let things coast?

Edit: If anyone has proof otherwise, I'd like to see it. Name one time Joyent ever made a mistake in their open source stewardship.
I am really happy that, with industrial Engineering background and thanks to all the resources I have been able to find online (stackoverflow and blogs like this), I have been able to follow all of these steps independently to be a programmer.

The things I'm still missing (and trying to improve) have to do with managing servers and parallelism. This is highly advisable but maybe too daunting in such a list for sharing with a beginner...
Mercury escape tower used when booster loses control, 1961.[1] Unmanned launch with a dummy.

[1] https://www.youtube.com/watch?v=Vp9BnBDKa0s
> the solution to the PD

Dyson truly proposes a great solution lying in PD. That is a huge oversight for game theorists when they let an outsider do that.

However, it's not the ultimate solution. It's an extremely interesting aspect (a strategy, a style of play) of the PD that game theorists somehow have never seen and articulated in maths.

For the evolutionary fitness of the extortioner solution that Dyson discovers:

Evolution of extortion in Iterated Prisoner’s Dilemma games
http://www.pnas.org/content/110/17/6913.abstract
Lots of food for thought. A more practical approach is this list/listing tool: http://userium.com because that has stuff translated to practical terms.
Nice explanation of what's going on. I've always thought there was an opportunity for much more of this kind of thing during the previous launches--explaining the process to those of us who really have no idea.
>You won't catch me dead wearing something like a pair of cargo shorts....

>People don't know what they want until Steve Jobs tells them what they want.

What if Steve had told you you want cargo shorts?
Interesting that the list includes "not being a lone wolf" and that goes on to state you should be capable of doing pretty much everything necessary to complete a project on your own. If you're capable of working well in a team you don't need to be able to do all the things in this list. You can hand off things to people who are better at those things. That's a good skill to have. That makes you very employable.
Prior discussion: https://news.ycombinator.com/item?id=9484049

(Different URL, but same text.)
I wish they would have better explored "2. People Have Limitations" via mental models and not been biased by "(as humans are 90% visual creatures)." Designing for and separating visuals from content can strengthen not only the user experience, but make accessibility elegant, instead of simply possible.
I know tons of smart people have already thought about this, but I still wonder if it would make more sense to collect almost all of the buttons at the bottom of a phone's interface.

Maybe swiping to go back makes this point moot.
This is absolutely hilarious, really worth a read.
The documentation I can find[0] seems to imply that XHTML is still required for embedding SVG into an HTML document.

[0] https://developer.mozilla.org/en-US/docs/SVG_In_HTML_Introdu...
Oddly, you didn't gain any space by going from 5" to 5.5" since the iPhone 6 Plus only has a 1080p screen. (Statistically, that's what you likely had on the Android phone since most 5" Android phones have 1080p displays). I'd be curious if you find a 5.5" 1080p screen more productive than a 5" 1080p screen. I'm using a 5" 1080p screen now and upgrading to a 2,560 x 1,440 6" display (Nexus 6) primarily for better web browsing on the go.
Sure, but they're not there yet, and probably won't be for decades and several more generations of designs. And a much higher flight rate: remember, this is an industry where no system has more than 1000 flights, and most don't have 100, and all those are with vehicles that were destroyed in the process.

In the meantime, having an abort system is probably a good idea. And besides, it's a customer requirement. And you know how customers are.
Given you're looking at using S3, is there a particular reason you aren't using DynamoDB? Or even RDS?
Delivery Hero buys Turkish food ordering website Yemeksepeti for $589M
I really like Joel and the team @ Buffer. They are a really nice group of people - always looking to help.

Also their company culture is awesome - the transparency they have related to how they work, success, failures or even the salaries is like nothing I have ever seen in a company.

Great job Joel and the team!
For the first 10 years of my job, I never used them. In my current job (working on hydrologically modelling software), every now and then I wish I could remember highschool maths.
A good team member plays to his strengths, but a wide breadth of ability is still valuable. It means you can understand what your teammates are doing. It's not requisite and sometimes is unreasonable to expect in multi-domain projects, but that doesn't mean it isn't valuable.

Similar to philosophies on management. A good manager does little hands-on work himself, but he will generally make for a better manager if he could hypothetically fill the shoes of each of his reports. Not that he should ever actually do that, but it means he understands what they are doing.
That's just simply not correct - scientific endeavour and the scientific method is an ongoing prospect. You never actually solve anything, instead you refine the parameters in which a given solution is deemed correct.

Newton "solved" the equations of gravity, Einstein "solved" them too, and now quantum mechanics is "solving" them yet again. None are wrong, but also none of them make the problem solved.

The idea of a "solved problem" in science is a dangerous one IMHO.
diego, thanks so much for raft! i'm a student in the brown class you shout out, and i can testify as to its relative simplicity and the clarity with which you guys communicate the ins and outs.

i have a question for you, though. why is raft not concerned with byzantine failure? the focus on byzantine fault tolerance from the paxos family of algos (and a lot of the literature/educationally material on distributed consensus) makes me feel like it's important, but your approach suggests it perhaps isn't. do you think this focus is a side-effect of the ubiquity of paxos which is disproportionately concerned with this due to its roots in academia?