skysight-inc/HackerNews huggingface dataset:
Jody Sherman, Ecomom Founder, Passed Away at 47
I've experienced this crystal clarity a few times in my life. Once, lying with my dog in the yard as a teenager, and another time driving over a hill and seeing a beautiful sunset. I experienced an almost overwhelming joy and love of life.

I am not a religious person but I think these are known as "Peak Experiences". [0]

I also experience "ASMR" [1] and maybe these things are related.

[0] http://en.wikipedia.org/wiki/Peak_experience

[1] http://en.wikipedia.org/wiki/Autonomous_sensory_meridian_res...
great news for customers....
How is this Apple's fault though?

Macs transitioned to x86 in 2005, with Apple repeatedly warning developers to GTFO of any PPC code they have ASAP. MS Office 2008 released years later still containing PPC binaries, and support from the OS was finally yanked in 2011, six years after the switchover.

This seems pretty reasonable. What is unreasonable is that MSFT continued shipping deprecated code as the newest and greatest, long after any reasonable update cycle.

To be fair to Microsoft, they weren't the only ones. App developers were warned for years since OSX's first release that Carbon was a transitional API that would be deprecated in favor of Cocoa. This was in 2001. Adobe steadfastly refused to update, and in 2007 Apple stripped 64-bit support from Carbon-based apps as a beating stick to get major developers like Adobe moving. It worked.

From everything I've seen developing both OSX and iOS apps, Apple gives plenty of notice between deprecating functionality and actual removal of binary support (from the above examples, six years).

Compare with my days developing Windows software, where developers knew well that Microsoft had zero teeth behind API deprecations, and will shamelessly keep using it for eternity, making future backwards compatibility efforts ever more painful - you will find code written in 2008 that uses functionality deprecated in the late 90s!
Thanks for your feedbacks! And you're right about needing a favicon soon, it's among the top items on my todo for design at the moment.

If all else fails though, I'm glad that I might have a career as a children's author! But really, thanks for your kind words about the illustrations and story-telling. They mean a lot to those countless drafts of redesigns and rewrites.

I especially like your idea of publishing a book version as a companion to the web. If the app grows big enough, I may very well do that!
I got a green card through the diversity visa program. The process itself really wasn't that complicated. Sure, a lot of forms to fill out and the overall process took about 1 year, but I never was at a point where simple internet research didn't answer my questions.
User testing at startups
Because he's been mucking around with core storage volumes and drive bay extenders to the point that certain of his internal drives look like they're on an external bus to the OS.

Apple optimizes for the common case, which he's way outside.
Promises do 2 things:

1) Give the illusion that control has been returned to the caller. It hasn't, but it kinda looks like it. This is soothing for people who don't really like JavaScript all that much.

2) Provide a structured way of dealing with callback-oriented code. You don't have to think about in a function whether the callback should be that last parameter, the only parameter. You don't have to think about whether it should include an errback or if the error should instead be the first parameter of the callback. You just do it the way the promises library describes, so the interface is predictable.

#1 is of no concern to me. #2 I feel pretty meh about. A consistent interface is nice, but I don't lose sleep over a library using callbacks in a slightly different way than I like, I just write an extra function or two to wrap it into the way I like and move on with my life. I don't have a problem with Promises per se, I just don't want a library I'm using to pick a winner and tact on an extra few k.

Doesn't look like ES6 is going to pick a promises winner, so I probably will largely ignore it until ES7.
Conflicting priorities. Different World views and life goals.
Doubt it. Problem exists in ST2 as well. I have a ~200MB ETL file I've been working with recently...takes ST2 around 20 seconds to open it.
A first look at Sublime Text 3
The most interesting part of this move is what it says about their relations with EC2 customers. Most cloud encoders that ET will compte with, run on EC2.
There is a fork of CoffeeScript called IcedCoffeeScript that adds something similar:
http://maxtaco.github.com/coffee-script/
not at all, one of the reasons I love HN is because you replied. same reason I love Quora.
Jon- How does this effect your relationship with EC2?
Three of the replies so far have assumed an anti-immigrant dog whistle was sounded. I'm not of the same opinion. If you can get to Chicago, as an illegal you basically have the same life as a legal, except you need to live cleaner than your average citizen so as not to get deported. Job, no problem, nobody cares if you're an illegal, employers actually like it. Car? Now no problem. Own land? Sure. Medical care? Not any worse than a citizen.

The insight is I'm quite certain I could not walk north into Canada and do the same.

Simply read what he wrote dispassionately without hearing imaginary dog whistles and its basically literally correct, there is little point in legal immigration for many people.

Now if that's good or bad, is where the psuedo-political sloganeering begins.
Agreed. The guidelines (http://thelist.io/guidelines) are nice too:

The List is not for:

Social media news

Traditional news

Funny images

Angry rants

Advice animals

Linkbait
> My opinion is based on that flow chart.

That chart is a serious oversimplification of the actual process. Even knowing which steps to take and which forms to fill out -- among many with similar, obtusely worded instructions -- takes much more effort than following a flow chart.

It's even more complicated because the feedback loop is vague and it _very_ slow. If you fill out a form wrong, or don't include the correct supplemental materials -- which, again, are described in a language which somewhat resembles, but really isn't, regular English -- then (1) you will be waiting weeks or months to find out, (2) a mistake could result in outright rejection, and (3) if you're not rejected, then any explanation of deficiency you may get will be, again, vague and bureaucratic.

My opinion is based on my own experience with the short paths on that chart: I married a non-American. I can only imagine what it's like for those on the other routes.
Looks more like Notepad with font face attribute.

data:text/html, <html contenteditable style='font-family: monospace'>
Travel and green card are different things. The issue is that welfare state is fundamentally incompatible with free immigration (you can't tax American rich enough to keep 7 billion people on American standards of living, and even if you could, it wouldn't work politically). So travel, beyond terrorism concerns and so on, is not much of a problem. My passport, for example, allows me to travel all Europe and most of the Americas without ever asking any visas. Immigration though is a different matter.
There's an extreme amount of magic going under the hood when you do this- from http://msdn.microsoft.com/en-us/library/vstudio/hh156528.asp... :

| "An await expression does not block the thread on which it is executing. Instead, it causes the compiler to sign up the rest of the async method as a continuation on the awaited task. Control then returns to the caller of the async method. When the task completes, it invokes its continuation, and execution of the async method resumes where it left off."

The implementation detail is that your caller's state needs to somehow be re-asserted when the asynchronous wait finishes evaluating- anyone mildly versed in computer hardware knows that to, in most situations (some green threading environments aside) be a very onerous scary intensive thing, speak nothing of the tasks of capturing and storing the continuation, which likely is fairly deep in a call stack somewhere.

It's great magic, it's certainly putting a lot of magic programmers like to use at their fingertips. But be advised that it is somewhat scary, handing out magic wands like candy to newcomers and telling them it's OK and good.
Funnily, I was just doing some comparison shopping between different promise libraries as well.

Besides avoiding highly nested code, and handling certain types of errors better, I've found that they also provide an optional progress callback, in addition to the success and error callbacks in then(). This is highly useful in reporting the progress of a long running process, to help give the user some update or stream the results as it's being completed. That cuts down on both the actual and perceived response time.

In normal callback-style, it's awkward to have two callbacks, one for success/err, and one for progress. In addition, it's not the canonical form for node.js, so we often skip doing it.

As for between the different libs, I've found that Q has one of the better APIs, but it's also the slowest.
https://github.com/kriskowal/q/issues/153

But that's because it uses Object.freeze(), which the js V8 penalizes with a slowdown, when iterating over it.
http://stackoverflow.com/questions/8435080/any-performance-b...
C# rewrites that function for you. Iced CoffeeScript exists largely for this reason: http://maxtaco.github.com/coffee-script/
The thing is that any imperative programmers who have composed SQL subqueries have have been doing this kind of thinking for years whether they realise it or not. The only substantial difference is that the data is in the process' memory as maps and lists as opposed to relational tables in the db. You end up with exactly the same kind of patterns of composition in the code.
Show HN: an Amsterdam Metro map in git commits
> I'm not sure why you bring up Classic, Carbon, or PowerPC.

Because it's not true that Apple doesn't emphasize backwards compatibility. I also pointed out that once those technologies outlived their usefulness, they were no longer supported, and that there is indeed less backwards compatibility than Windows.

By the way, Office 2008 ran on Intel Macs. You're thinking of Office 2004, which was PowerPC only and ran for 7 years before OS X Lion dropped Rosetta.
For what it's worth, this is exactly how Parse's .NET SDK works. Promises in JavaScript go a long way toward improving the experience of async development, but I thoroughly agree that language-level support for this type of construct is immensely helpful.
Minification is not enough, you need tree shaking
> Mac OS is a bit too much of a (my personal opinion remember) toy for serious work other than writing, photoshop or any other artsy productivity

I've read a few comments that say the same but I've never understood why. What serious work do you do that OS X isn't good enough for or what does it not do well?
I felt this way about Ultra-Edit32 for a long time on Windows. I bought in college, and I believe it had a "... and future upgrades are automatically free" clause. It made me have a LOT of faith that this would be a useful and awesome product, and I was a happy user for many years. (In a sense, I bought it twice, as I asked my employer to buy it for me later.)

As a prospective user of Sublime Text (3, now), it's interesting to think about how I would feel had I bought ST2 a year ago, and now felt compelled to upgrade. The price is semi-negligible, in terms of how much one pays for a quality tool -- it's a fraction of the price of Komodo IDE or PyCharm, for example -- but the hassle is still annoying.

As Silhouette points out, it really makes one wonder about how long "support" (bugfixes, etc) will last for the current version. I think one of the more interesting questions to arise from this thread has been what the difference is (or should be?) between a point release (vN.5) and version N+1.
Numbers are always trustworthy if they're accurate. You just need to right context to interpret them in. These numbers are straight from Google Analytics, and you are correct that one was a direct link and the other was via TC. I say this in the article.

This is a real world scenario. Many people ask how much traffic we got from being on TechCrunch. This is just data, take it as you want. I do my best to explain the main caveats, including the one you pointed out. There are many.
Very cool.

I like this guys implementation too. https://gist.github.com/4666256

Perhaps an implementation with vim bindings support? :D
The Horrible Designs of an Apple TV Clone
Personally I'm more interested in the concept of typing gibberish to clear your mind. What particular kind of gibberish? Doggerel verse? Blind keyboard mashing?
Testing controllers outside of a Rails application with RSpec
Apple licensed Rosetta on a per-install basis from Transitive Corp.

Then, IBM bought Transitive and discontinued the PPC->Intel translation engine.

Apple did not have the option to continue shipping Rosetta, because IBM axed the team that would have had to update it for Lion.
I'm in about the same boat, only it's been more like 3-4 years. Newegg is about to get more business from me.
Context: http://techcrunch.com/2012/08/28/talented-shirley-hornstein/
To be sure, it looks like a first alpha. Maybe they hired a new JS person over the holidays and this is their first deliverable.
WalletKit Hustles Its Way Into 500 Startups
Just add class 'ie' to the html tags.
An analogy I like for the "language support" part is Python generators. All you need to do to turn a regular function into an async one is put the `yield` keyword where appropriate. Promises, are less worse then continuation passing style but they still require you to rewrite all your code using the promise library instead of reusing existing language constructs.

If you want to carry the analogy even further generators can also implement coroutine patterns, if you use yield as an expression (for communication) and yield from to do nested generators.
The Ever Shrinking World of Mobile/Local
Apple’s App Store Is A Double-edged Sword
I wish I could do the London tube but it’s cyclic. Even for Amsterdam, route 50 was a bit of a kludge as you’ll see in the tree.

Here’s an image with tag/branch names for the lines: http://i.imgur.com/vXhLYry.png
I would take job postings on AngelList with a grain of salt. We're keeping an eye there quite a bit recently, and it seems there are strategic reasons (as in make it look like you are doing well to investors) to be posting jobs on a site like AngelList more than the practical ones. I'd say the equity numbers are probably closer to reality than the salaries (I'd be shocked if you as a developer got more than 3% at any company that is beyond seed round). Of course early-mid stage startups aren't going to just flat out offer lots of money, they are trying to make their runway last as long as possible.
Not to start drama, but that's a bit sexist, isn't it? Can't she just be 'stronger than any person you know'? There's nothing inherently 'manly' about being a strong independent person.
"I'm not upset that you lied to me, I'm upset that from now on I can't believe you." - Friedrich Nietzsche
In fact, if you add the `%s` variable inside the HTML tag:

data:text/html, <html contenteditable>%s

This way, you can enter:

note [tab] "foo bar baz" [enter]

And whatever you enter as the search query ends up in the note to start with.

Edit: Just saw the other response to this comment saying basically the same thing. Nevermind.
http://www.habbit.me

It's a gamified app for building your ideal future self with habits!

It was just launched yesterday on HN so, for the first day of my first startup, I'm happy with getting over 60 users signed up already. Not sure how to tell what's good traction or not though.
Your casual ambivalence for #1 makes me think you don't appreciate the greatest value of promises: that they are values, objects.

Returning control to the caller is half the story. Along with returning control- which indeed is what is happening, no illusion, if the promise is triggering a non-blocking routine- the promise itself is returned: that object is what makes promises great.

We have no other object for an execution or process in JavaScript: a promise, the value it returns, is an object. Objects can be used and talked about inside JS. If there is no object, there's nothing to compute about. A promise is a first class execution that we can compute about.
And yet, front page has the story of Mark Zuckerberg's hoodie. :)
If you're not into CoffeeScript take a look at TameJS (http://tamejs.org/).
Sounds to me more like they are making a comment about the dichotomy between masculinity and gender. Seems a reasonable observation to make.
>That’s getting pretty ridiculous...but because of the way promise chaining works, the code can now be much flatter.

In what way is the indented code ridiculous, and why is flatter better?

Conceptually, you still have to think of the callbacks operating the same way in order to properly understand the code. Flattening it out and changing the shape so that it isn't nested doesn't really help change what is going on. Maybe I'm missing the bigger picture.
Beware of fake Windows 8 Activators - The Hacker News
I find the drop-in-advertising rates the most interesting item. I don't follow this closely, is revenue-per-click actually dropping?
Exactly, this is great, the design is impressive, and the engaging story at the start engages you emotionally :) as dcolgan says.

I'll add my "wow" to the list. Based on the responses, you definitely hit the right chord. AND it's a problem worth solving.
Huh? That's besides the point.

My point is that just because it's commercial software doesn't mean it should be closed source. If it was open source it could be 'easier to steal', but I bet most people seriously using it would still buy it. Anybody that took the time to patch the source would never have bought it anyway - so there is nothing lost.

I'm not sure why I'm getting down voted. For a bunch of open source evangelists that's pretty hypocritical.
I wish I was still using MySQL in order to use Sequel Pro. It would be perfect with Sqlite and Postgresql support.
The Customer Data Grid: a sales-oriented segmentation
http://www.urbandictionary.com/define.php?term=pizdets
They attempt to address the L-1A & B visa path on the right side where they ask "Working on H1, L1, etc".

Admittedly, the chart doesn't include the extra step of having to qualify for an L-1. At least for the L-1A, you'd need to have worked for a subsidiary for 1 year before being granted the visa.

The good news is that once you have the L1, then you can follow the EB1 or EB2 paths on the far left hand side.
Watching Triumph of the Nerds with my Dad in the mid-ninties is one of my fondest memories, and played no small part inspiring me to study computer science and subsequently get involved with starting companies.

Accidental Empires (the book), remains full of detailed insights into the emergence of Silicon Valley and startup culture. The fact the show was set in the mid ninties may make it seem a tad dated by today's standard, but it was fascinating to watch Cringely talk with Bill Gates, Steve Jobs, John Sculley, folks from IBM, Xerox, and more.

As a 15 year old watching on a sofa from 6,000 miles away, I was incredibly inspired by the tales of dedication to product creation and hyper growth. It's a part of what inspired me to move to the Bay Area years later.

I look forward to re-reading the annotated version of Accidental Empires and hope Bob continues to write (and interview!) for many years to come.
You can wrap your callback functions and handle errors all in one spot. Example:

var slice = Array.prototype.slice;

function errHandler(callback) {
return function(err) {
if(err) {
// Error handling code here.
} else {
callback(slice.call(arguments, 1));
}
};
}
I have mixed feelings about this announcement. On the one hand, I really enjoyed Triumph of the Nerds. On the other, Cringely came off as a self-oriented, egotistical guy (I remember the scene where he threatened the TV crew with a piece of bat when his plane build project wasn't going well) with few unique insights and little depth.

Now that I think about it, these two facts are in line with his announcement. What he brought to the scene was to act as a tech interpreter for the baby boomers. The novelty has worn off and he's tapped out. This seems very similar to what happened to Dvorak, and what happens to a lot of bloggers: he exhausted his material and the world passed him by.
The apply link is to thelist.dev/apply
In contrast, see http://gridvid.me
Be forewarned: the comparative study uses old copies of the Android (2.3!) and Windows Phone (7) SDKs, so this study is probably of limited use.
I don't want to stake this girl up, but honestly, she should produce something that anyone cares about or shut up and go away.

There's qualified people out there she basically stole from. Stole jobs that should have been theirs, stole attention that could have been directed to something legitimate...

You don't get to apologize for stuff like this and have anyone care, you only get to overcome it. So until she has something to show us, I'd prefer not see her around.
I went with a TC article for the specific reason of getting an HN post out of it.

This led to waiting an extra week or two to launch, was generally a hassle, etc. And our article hit in the afternoon on the west coast, vs. at a reasonable hour on the east coast.

In the future I'd probably just post directly to HN. Getting to pick the time of the HN post is probably worth more than the incremental value of TC. TC might be worthwhile for funding announcements, but I'd never use it for a product announcement.
Chirpify turns replies and comments into cash.
http://webcache.googleusercontent.com/search?q=cache:www.smi...

Google text cache
Actually, Office 2008 ran on Intel Macs. It was Office 2004 that was PowerPC only, which as you state was supported for several years.
Some ideas that are ubiquitous within functional programming are certainly on the rise, for example:

- functions as first-class entities in programming languages, and consequences like higher-order functions and partial evaluation;

- a common set of basic data structures (set, sequence, dictionary, tree, etc.) and generalised operations for manipulating and combining them (map, filter, reduce, intersection, union, zip, convert a tree to a sequence breadth-first or depth-first, etc.);

- a more declarative programming style, writing specifications rather than instructions;

- a programming style that emphasizes the data flow more than the control flow.

I see these as distinct, though certainly not independent, concepts.

I’m not sure whether functional programming itself is really on the rise, not to the extent of becoming a common approach in the mainstream programming world any time soon. I don’t think we’ve figured out how to cope with effectful systems and the real world having a time dimension very well yet. (I don’t think we’ve figured it out very well in imperative programming yet either, but the weakness is less damaging there because there is an implicit time dimension whether you want it or not.)
It's only available for something like ten countries, though. :/
We are working towards something similar at CPUsage....
You might want to do some kind of emotional connection before "donating" paying (1), and review the studies on "pay what you wish".

I can't find the best one I saw (which I believe said to set a default price), but I found these others:

http://www.freakonomics.com/2010/07/20/how-to-maximize-pay-w...

this one is long, but has a section on "pay what you wish" midway through.

http://conversionxl.com/pricing-experiments-you-might-not-kn...

(1) I mean something like saying: "you accomplished X goal this month !!!". Probably someone else has more specific advice :) , I've never tried pay-as-you wish myself, but seen lots of previous advice here!