skysight-inc/HackerNews huggingface dataset:
I'm not sure why you think I have no real architectural details. What do you know about what I know?

Regardless, I think your pedantry is based on a statement I intended to be read in a less formal fashion than you're choosing to read it. When I said that it was not a possibility for poorly-behaved apps to drain significant amounts of battery under iOS 7, I didn't mean that it was absolutely impossible under any and all circumstances including system bugs, unforeseen architectural weaknesses, or gamma ray induced bitflips. People say "Linux uses memory protection to keep processes from corrupting the memory of other processes" and we all understand that they don't mean that it's literally impossible for memory problems to ever happen.

Likewise, my point was that it is generally true that iOS 7 doesn't allow apps to wake up as often as they want. That is a design goal behind its architecture. Doubtlessly, neither its architecture nor its implementation are perfect — I'd be surprised if it were utterly impossible for an app to end up running whenever it wants in the background. But it'd be boorish to belabor that point.

The original post that has led to this discussion was saying that Android has been criticized for being designed to allow apps to run in the background arbitrarily and now iOS has been redesigned to allow that too. That's not true. And the conclusion of hypocriticalness that was drawn from this faulty premise was untrue.
Design is how it looks
I don't see any actual links between being able to run a competent government, being able to drive properly, and being inculcated to have "sit down and shut up" as your chief response to most of life.
You have a very incorrect view of homeschooling.
I was surprised that we got in and shocked that they put so much time into the article. I can't believe it makes economic sense to put so much into such a short write-up, but I guess it does for The Times.

Together my wife and I check quite a few boxes that the NY Time typically looks for. We aren't famous or all that noteworthy, but we do have an interesting story of how we met. That was the main focus of the article.
First of, Congrats on the round!

The article provides some interesting numbers to chew on:
- 150,000 users
- 15,000 business (let's call them customers)
- $50,000 in monthly revenue
- 6 lines average per customer.

Impressive numbers to backup traction! But they also tell the story of the freemium model very well.

Sendhub website lists cheapest paid plan at $25/month/line. This means that at most, they have 2,000 paid lines (based on $50k monthly revenue) and in the neighborhood of 400 paid customers.

These are still very good numbers and nothing to frown upon, but if you compare that to the massive adoption of the free accounts (150k users), it's very telling of how difficult it is to convert people from free to paid.
"There is no one-size-fits-all in this case."

Exactly that!
> the rewrite was scraped at about 80% completed.

Which rewrites were scrapped? All of the iframe rewrites or just the last feature rewrite? Was the result considered a (partial) success or a failure?
Ah, I hadn't realized you literally meant the ability to shut up as opposed to the general lifestyle of regimented obedience normally signaled by the words "sit down and shut up".
Hey Brian, of the partnerships you mentioned, or any others, what is a good example of a deal that killed it for both parties? Any 1+1 = 10 kind of deals come to mind?
Wait, that logo thing already finished?
a) I've been too busy.
b) Yahoo need a better marketing department, I didn't hear about it after day 1.
As a South Korean living abroad, I am regularly asked about North Korea by curious foreigners despite having no special expertise on the subject besides having followed the news all my life by the virtue of being from the south of the DMZ. One of the most difficult things to convey, even to fellow South Koreans, is the fact that North Korea is as complex as any human society. For most people, North Korea is the very definition of the Great Unknown, and we tend to imagine such things as monoliths (it is incredible for instance how many outsiders seem to picture Africa as one giant mass of starvation, disease, and war, and are astonished to see anything that doesn't fit the preconception like bustling modern cities with a thriving middle class).

It is easy to describe the lack of freedoms, cult of personality, massive prison camps, the songbun caste system and total lack of civil society in North Korea, leaving the curious foreigner shaking her head at the bizarreness and monstrosity of it all. But it is also easy to forget that this is a society inhabited by flesh and blood humans, not ruthless robots and their abstract oppressed victims. We don't get to see much of this side of course. But in some ways in the last decade or so North Korea has been creeping towards something close to normalcy, albeit far from ideal—corrupt officials, flourishing black markets, extreme disparities in wealth, and even cross-border trade with China. Nothing to portend a Soviet-style collapse of course, but even the slightest increase in openness is something we should welcome.
I'll do my best, but it's a bit hard to explain.

Basically channels are yet-another synchronization paradigm like locking or shared memory, some people like it some don't. Channels are an implementation of Hoare's CSP [0].

Channels can be passed around, the same could be said about Lua coroutines. But with channels you get more flexibility:

- you can "block" on many channels at once using the "chanalt" statement. You can "resume" only one lua coroutine at a time.

- channels they can buffer messages (ie: channels can queue several values)

- many coroutines may "send" a value to a channel at the same time, many coroutines may try to "listen" (receive) a value at the same time.

- finally you can pass a channel over a channel

I find channels, as opposed to many other synchronization paradigms, to be composable and generally nice in use.

It's a "better" alternative to synchronization locking and mutable data. But in Lua, of course, there aren't multiple threads so why synchronization is useful? In the same way that coroutines are useful - they allow you to decompose a program into set of smaller programs. The example given by Russ Cox is the Eratosthenes sieve. You can read about it [1] or watch him talking about it [2], finally my implementation following his talk [3].

[0] https://en.wikipedia.org/wiki/Communicating_sequential_proce...

[1] http://swtch.com/~rsc/thread/

[2] http://www.youtube.com/watch?feature=player_detailpage&v=hB0...

[3] https://github.com/majek/lua-channels/blob/master/sieve.lua
I'm an ex-architect -- or, more accurately, a recovering architect: it's like an addiction in that way -- and I have to say that you really do know what you are talking about here. My sympathies!

(Although I'm far from enthralled by this building, I have to say that it actually looks better than I expected it to based on the utterly fugly renderings from a while ago. I can't imagine how it got through planning consent based on those.)
Just curious, how come you don't have a minimum font size set up?

I never run into this problem due to having done so, but I see a lot of people complaining about it...
I should have known better than to get drawn into this discussion. You're right that no one in this thread specifically stated that these are brand new ideas, but you can't argue that people are stating that it was bad in Android but good in iOS. It all comes back to the user choice vs walled garden argument. There's the Android way of doing it, and the Apple way of doing it. You say it's a significant difference; the difference is simply in Apple not letting people do something they could do in Android. The parts that overlap are almost exactly the same. Think of how many people believe that the iPod was the first MP3 player, the iPhone was the first smartphone, and the iPad was the first tablet. Do you think that's by mistake, or because Apple really wants people to think that? How often on HN do I hear people making the claim that Apple beat Microsoft to the tablet and smartphone game? [1]

"On Android can't the app just run forever and decide on its own how often to poll the servers? This is a different thing. The OS decides when to schedule things if the app supports it. What may have been true years ago isn't necessarily an issue anymore."

vs

"When a competitor does it and Apple says they won't, it's the worst thing in the world. Once the competitor proves its worth and Apple does it, it's now the best thing ever"

Sure I'm using hyperbole, but I think I adequately summed up the argument. xutopia implied that Android's battery life suffered from having background jobs running, and that this was a bad thing. Since Apple is only letting the jobs run at predefined intervals and all at the same time to save battery life, this is a good thing. That is exactly "it was bad when Android was doing it, and it's good when iOS is doing it". I accept that perhaps he didn't know how Android's background scheduler works, but that still says to me "background tasks are a bad thing except when Apple does it."

You're also conveniently ignoring that I called out just about everyone who had responded at that point, not just xutopia. xutopia's comment was the least offensive of all of them, and I certainly understand his argument. Apple is doing it in one of the many correct ways. It's not, however, significantly different from how Android recommends developers accomplish the same task. The only difference is, on Android this is discretionary and on iOS this is enforced. Neither of these are bad things.

[1] https://news.ycombinator.com/item?id=6264617

This is a discussion I participated in not that long ago where people were legitimately stating that Windows Mobile and Windows tablets don't count because the iPhone and Android phones look different and have faster processors. I just gave up.
The board of logos looks like something you'd expect if you went to 99designs and posted: "Billion dollar company needs new logo; winner gets $125! Must use one color, be tiny as hell, wording only, no art. Winner will be selected after 30 days of voting by end users. Please, no imagination; we do not want to scare Grandma away from her 'google'."
So I guess the question now is, has this changed much since 2009?
Based on personal experience, I found that paying for the setup, tuning and 24/7 maintenance of a dedicated is way more expensive than using those service.

But I'm one of those crazy people who considers their time and that worth something.

Excuse the snark, but these arguments just keep repeating themselves. There's a reason they're called "services". It's like saying "it's cheaper to slaughter your own cow than to eat at a restaurant".
Fighting against a censorship machine (Google Blog)
How long does that weekly charge take?
And that is where the line divides. Android users are like you... they don't want to pay for software and go for cheaper hardware when they can.
FTC settles with Trendnet after 'hundreds' of home security cameras were hacked
The correct answer is to target both as 3.3 is significantly better than 2.3.

And 2.3 was 2.6 in January so for a really bad back of the envelope calculation we can guess 2.3 will be 1.0 sometime before 2017.
time to meet with VoltDB.
A PLT Redex model of Rust, almost
Google really doesn't want to have to automatically censor search results. European courts might make them do it.

(Full disclosure, my wife wrote this blog post.)
As a designer, this whole process is degrading, frustrating and reminiscent of the worst clients I've had throughout my career. I'm not sure if they are trying to make it look like they want to appease the people, but if I were working in-house over there, watching all of these awful designs roll out would just crush me and make me question what they think my worth is. I'm hoping the whole thing turns out to be a joke.
Thanks a lot for the reply, one of my favorite things about HN is getting questions answered by the authors of the tool in question. After reading more, your decision to not post those benchmarks is a smart one. I get where you're coming from with regards to it being hard to make a performance comparison to protobufs, it makes sense now. If/when I need to reach for some serialization I'll certainly try out Cap'n Proto.
It's not a question of denial. The argument being put forth is that the tech sector is sexist/racist/whatever-ist, and that therefore anyone who works/is connected with, the tech sector is by association then a sexist/racist/whatever-ist. I reject that assertion. By that same logic everyone over in Syria is a mass murderer, after all, they all live in Syria, and other people who live in Syria are killing lots of people, therefore all Syrians are guilty of murder.

On a related note I don't necessarily even agree with the basic premise of the argument. I'm not entirely convinced that the tech sector is sexist/racist/whatever anymore than the rest of society is. Rather I think the lower representation if women in tech is a symptom of the wider cultural problem and not something that can be laid solely at the feet of the tech industry.
Think Distributed: Causality [video]
Educators tend to be big on calculus because it correlates with college success [1].

Independent of the studies (there are more) I think that stats is very underserved in society. Nurses should know statistics. Knowing joint %s and Bayesian stats are useful in treatment and diagnosis. Much of health care is moving from doctors to nurses, and it's important for them. Stats are also important for people making investments. And buying lottery tickets. And buying a house. And making judgements in daily living.

[1] http://www.ppic.org/content/pubs/report/R_701JBR.pdf
I think this is great for both Uber and the NFL. This is good PR for both, brings additional legitimacy to Uber and highlights the NFL's efforts to address this issue (at the end of the day maybe save some careers if not lives).

However, if the NFL was truly serious they would contractually require all players to install breathalyzer car starters (if you don't know search it) in their vehicles. Is that extreme? No, not in light of all the other contractual obligations NFL players/professional athletes already agree. One example is UFC fighters contracts include provisions in which they agree not to drive motorcycles.
I would say that the iPad is not a tablet because it doesn't have a x86 processor nor does it run Windows Tablet Edition. The iPad is a larger smartphone, and the iPad Mini is a smaller larger cell phone.

I hope I don't sound ridiculous because someone miscategorized the iPad in the same category as Windows XP Tablet Edition.
That is the part that does not make sense, it does not seem like it would take little to any editorial effort to just reprint the book. Page numbers changing from 33 to 53 as in the OP's case make it seem effort was made but not followed through on.
My mother is a retired teacher. My sister is currently a teacher. They also have issues with teacher's unions. We are in an urban school district.
His implementation uses libtask

No. I just implement libtask/channel.c in Lua.

It does not provide parallelism. Parallelism is important.

I'm doing it in pure Lua. Lua doesn't use multiple OS threads. Doing channels _across_ Lua contexts would be an interesting thing.
Before adding new features, can you make it so my Safari, when one page gets stuck, doesn't need to force-reload all pages? Because that's just weird.
Is there any way you could find it at a library?
This seems like a useful feature. Any chance of an open standards process bringing this kind of functionality to browsers with more market share?
AOL is still around, and my sister still has, and uses (infrequently)and aol.com address. Though she would prefer I communicated via facebook.
Is there any recourse for her? Because I have done this times too many, i join hangouts and then delete the G+ afterwards. I will be terrified if curated music playlists get removed from my YouTube channel.
> VCs all have iPhones.

Fred Wilson would beg to differ (at least until a few weeks ago, and even then, his reasons for switching are not what you might think).

Seriously, no (good) VC is going to decline to invest just because you're Android-first instead of iOS-first, if that's a decision that actually makes sense for your target market.
In a sense I have to admit that I'm envious! I would love to dedicate a lot more time to educating my kids. (I give an hour a day to it now.) Unfortunately I couldn't pay the rent doing it.
But why release a version that has performance issues even on two year old hardware without optimizing it first. The new google maps is slow to the point of unusability on my two year old hardware. I can live with the rest of the UX changes, but not with the magnitude of the slowdown.
I really like the Idea
EBay app for Galaxy Gear Smartwatch [PDF]
Just to give a bit of counterpoint, here are some trade-offs that Capn Proto makes compared with protobufs. (Full disclosure: I work at Google and know Kenton from his time here; I have my own protobuf library that I've worked on for several years). I'm sure Kenton will correct me if I get anything wrong. :)

Capn Proto's key design characteristic is to use the same encoding on-the-wire as in-memory. Protobufs have a wire format that looks something like:

[field number 3][value for field 3]
[field number 7][value for field 7]
etc.

The fieldnum/value pairs can come in any order, and may define as many or as few of the declared fields as are present. This serialization format doesn't work for in-memory usage because for general programming you need O(1) access to each value, so protobufs have a "parse" step that unpacks this into a C++ class where each field has its own member.

Protobufs are heavily optimized so this parsing is fast, but it's still a very noticeable cost in high-volume systems. So Capn Proto defines its wire format such that it also has O(1) access to arbitrary fields. This makes it suitable as an in-memory format also.

While this avoids a parsing step, it also means that your wire format has to preserve the empty spaces for fields that aren't present. So to get the "infinitely faster" advantage, you have to accept this cost. For dense messages, this can actually be smaller than the comparable protobuf because you don't have to encode the field numbers. But for very sparse messages, this can be arbitrarily larger.

As Kenton points out on http://kentonv.github.io/capnproto/encoding.html , lots of zeros compress really well, so even sparse messages can become really small by compressing them. To do this you lose "infinitely faster", but according to Kenton this is still faster than protobufs.

In both cases though, the tight coupling between the (uncompressed) wire format and the in-memory format imposes certain things on your application with regards to memory management and the mutation patterns the struct will allow. For example, it appears that the in-memory format was not sufficiently flexible for Python to wrap it directly, so the Python extension does in fact have a parse step.

Other cases where you could need a parse/serialize step anyway: if you want to put the wire data into a specialized container like a map or set (or your own custom data classes), or if the supported built-in mutation patterns are not flexible enough for you (for example, the Capn Proto "List" type appears to have limitations on how and when a list can grow in size).

It's very cool work, but I don't believe it obsoletes Protocol Buffers. I'm actually interested in making the two interoperate, along with JSON -- these key/value technologies are so similar in concept and usage that I think it's unfortunate they don't interoperate better.
Icons for Hadoop
Because who doesn't need icons? Stencils for Omnigraffle and Visio.
How to get an amazing website for $99/mo.
So we've been dealing with the consulting cash flow roller coaster for some time now and decided generating more recurring revenue was probably a smart move.

One idea we had (thanks to advice/guidance from the likes of Brennan Dunn, Nathan Barry, Amy Hoy, and Patrick Mackenzie) was consulting as a service. We realized there were many business owners out there who struggled with the various template sites (Wordpress, Wix, Web.com) but didn't have thousands to spend on custom development.

So we created a simple $99/month package which included everything clients needed (design, updates, and hosting) via Squarespace. The price point seems to be working well so far and clients get a quasi-custom site built without having to deal with anything tech related which they love.

Curious what everyone thinks of the concept (good and bad)?
Don't Be The Guy In The Pool With A Shirt On
But wasn't a lot of money wasted on all those other years? Or are you suggesting that you need to waste that money for each classroom teacher to reach 1 or 2 a year? (And eventually everyone gets caught)
While I entirely agree with your lead in, your last bit is very "where the puck was" thinking.

Two years ago the Play store yielded 1/10th the revenue of the App Store, by common metrics. One year ago it was 1/4. The most recent stat is 1/2 -- still months old. Do you see where this is going?

The #1 source of revenue for many games and other media on the App Store is via gifted iTunes cards. This is a mechanism that is only now finding its way to Android.
So what? People have been doing that for centuries using almanacs. And with computers that sort of thing becomes stupidly simple. IIRC that functionality is even built in to Google Sketchup.
It didn't sound like he was holding it up as representative to me. Just that he wanted to acknowledge that both ends exists.
Cassandra counters once were implemented as a blazing-fast vector-clock patch [1,2] that did not involve read-before-write on update. The biggest (IMO) downside is that it did not support decrements. So Cassandra tech leadership decided [2] to implement counters as "read, increment, write." However, that came with two major downsides: 1) counter updates were now no longer replayable--so if you experience an update timeout on the Cassandra side under heavy load or due to a lengthy compaction or some network fluke, you just can't replay it. You need to hope that it has made it over. Counters run on hope. But you can decrement them now. 2) read-before-write can severely limit performance in the case of a large number of counter writes (as the workload becomes much more read-intensive, unlike regular blazing-fast Cassandra writes).

1 - https://issues.apache.org/jira/browse/CASSANDRA-580
2 - https://issues.apache.org/jira/browse/CASSANDRA-1072

However, in many many a use case for counters, you just don't need to decrement. And if you need to decrement, you can often get away with two counters, that you subtract from each other. So that's a shame, as restricting the use case for counters to be monotonically increasing would've been just the right trade-off for many users.
Label sues Spotify over playlists
Libraries usually keep Indian editions of the book. I haven't checked for TAOCP but that was atleast the case with Kernighan and Ritchie.
Safari in Mavericks is process-per-tab so that will be fixed.
Hi, any chance you'll submit a rockspec to LuaRocks?
For me, it would cheapen the experience if I didn't trust what I was reading.
I've been on HN for a while (lurking), never seen a downvote button but here people referencing them on occasion. Why do I not see downvote buttons? Or is this some inside joke?