skysight-inc/HackerNews huggingface dataset:
I do not know the code; nevertheless, I disagree. The moment you allow for leap seconds, you need to visit your apps. Can they display x hours, y minutes, 60 seconds? (IIRC, 61 seconded can occur, too). You also need to consider how and how often you update your 'current number of leap seconds' store, you have to add 'across leap seconds' checks to all duration calculations, in addition to 'across DST change' checks, etc. You also will have to decide, on a per call basis, what the programmer intended with a call ('one day later' or 'same time on the next day' or 'about 24 hours later, also on the whole hour'?) oftentimes, the programmer will not even have realized that these are different options. And heaven forbid if somebody does a calculation now for a future date, and some time later a leap second is announced for some moment before that future date.

I do not think a really nice design is possible here. There just are too many idiosyncrasies in time handling.
I just checked my stock Galaxy S2, and it was almost 2 minutes out. After enabling the automatic time setting, I checked again and it was like 1.9 seconds out.

Doesn't seem to be a problem here, either.
My proposition(probably not original at all) is that we let Disney(and anyone else) extend copyright on thing it wants at an ever increasing (exponential) rate. If they have to pay they will make sure to only keep things under copyright that are still bringing them value.

Also, we need to move towards a registration based copyright system. This post doesn't need copyright protection.
DDD for Rails Developers. Part 2: Entities and Values
Personally I find the thought of humans killing humans much more scary than machines killing humans.
I'll answer my own question: a modicum of research shows that this is indeed a nonstandard practice. There must be a need for such a service, however. There probably are workplaces that benefit from coercive recruiting agreements that punish employee turnover.
My A: is my physical Blu-Ray burner, and my B: is a virtual drive.

http://i.imgur.com/rGp12.png
You are right, but an open sourced QNX would be a great thing. The best outcome i can think of: BB sells QNX SS to Google and they develop it in the open with an improved license. They could use it for all their Google X stuff.

All the robotic Startups in the future could profit from a mature open sourced real time OS.
You're right. Funnily enough, Prospect Park was where I realized I didn't like it there. I was enjoying a good run in the park with my roommate and telling her how great it was. Then I realized the only reason I was happy was that the park was completely empty: it was 10 o'clock at night and a downpour had just happened.
It seems like NYC just seems like a hub, because people are already there and don't want to move.

Very few people who decide to uproot to start their startup elsewhere actually choose NYC over SV.

Frankly, I don't see what the big deal is, lets face it, most programmers are more or less geeks, so all this talk about the better night life and clubs, dating/mingling opportunities etc probably doesn't even apply.

It's all about the person really.

Someone outgoing, will find all of those even in the middle of nowhere in Kansas. And someone with social anxiety will have problems no matter where they are.
I do not think your blog examples goes beyond REST. You just need to represent different resources. For example a "title list" or "article set".
You could (and people did) say the same thing about Nokia, though. If RIM was involved in some sort of sale to MS, staff cuts would absolutely be on the table- so actually, ditching WebKit could be convenient.
The "other thing" for us is is RPC and PUB/SUB patterns over sockjs (which wraps Websockets+fallbacks).

REST is a tool. But given an engineer a tool like a hammer and pretty soon everything will look like a nail. Sometimes you need a screwdriver when you actually have screws. Hammering them in will work but it is ugly.
Yeah but my 11% extra cost me 400% more RAM, so you probably win :)

I knew I'd seen a similar post in the past, but couldn't find it.
The writer positions the video as a sort of smoking gun, but then hedges with "as today’s legal system is more complicated than some of us can understand, the legal heads at Apple really had a shot at proving they had invented the whole ... concept".

I feel a bit pandered to. How about some more legal substance, even for us dumb tech readers?
A word on managing feature flags
I'm just discovering the lean startup methodology, and I was wondering which book (or other resource) is best for an overview of the methodology, as applied for a small startup, from a very practical point of view.

Start Small Stay Small was very close, but it did not espouse much Customer Development.

As you point out, it's not Eric Ries book. I suspect it's not Steve Blank's Manual, as it's more of a reference. Maybe the Manual has a brief overview as well ? I mean, to use it as a reference, you first need to understand the method and what to look out for.
FWIW: Amazon's Micro instances will burst to saturate unused CPU cycles on the host machine up to a hard-capped limit before being choked to death by the hypervisor.

Had he run the Blitz test for 10 mins or more you would see the spike in traffic up, beyond what you think a Micro should sustain, and then it plummet to near 0 for a disturbingly long period of time[1].

If you are unlucky enough to have a Micro on a host that is fairly saturated, the performance you get is untenable.

Micro's are not "smaller than" Smalls -- they are a different type of monetization production from AWS allowing you to pay cheaply for little bursts of underutilized hardware.

There is no way (none... not possible, zero) that a Micro would be able to provide the bandwidth and CPU power to host a realistic site doing 10 million hits a day even if everything was straight from RAM.

Read through the EC2 forums for any length of time and you'll frequently find people coming in with reports of their machines "stopping" or "crashing, and totally inaccessible" for minutes at a time with a 100% ST ratio; every time it is a Micro that has been hammer for a bit either through benchmarking or use before the hypervisor puts it in a full nelson and brings it down to the point that SSH connections to the host cannot even be maintained.

-- I would also point out that not only is the CPU time allocated in bursts for a Micro, but the bandwidth is prioritized behind every other instance type (unless you were using a CDN, this would make hosting a typical wordpress site sluggish at best from a Micro -- and again, doing 10 mil hits a day... not going to happen in reality) -- yes you can offload all your graphical assets to a CDN, but now this article is about a $15/mo server and a $4217/mo CDN bill which is a very different article.

Additionally, if you need to use EBS at all in here, the story gets even worse with Micro's (even using something like RDS which requires network I/O in addition to hosting site content is all going to collapse on itself within the first 5 mins of the site's life with traffic like that).

All that said, the tips in the article are great. I only mean to clarify expectations with the use of Micro's. A whole swarm of them grinding through a work queue in random order is great; using them as the backbone of your web presence will have pain points. (Yes you can put 20-50 of them behind an ELB, but at that point why not run a handful of Mediums or a few Larges).

Anyone with a Blitz.io account, please feel free to setup this exact configuration and run the benchmark for 1hr with the same load to verify the meltdown.

[UPDATE] Ewan, I am not knocking your article, I wouldn't expect most people to be familiar with the ins and outs of every cloud provider. The tips and techniques are great regardless of the actual performance on a Micro (and applies to anyone trying to scale WordPress). Just wanted to clarify for anyone getting excited that they can now run their Fortune 500 website on a single AWS Micro that there are nasty surprises lurking just under the surface.

[1] http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/co...
What? Of course there are. That is not what I meant. If you choose to use a full Free Software stack, you'll have to face some inconveniences: fewer hardware choices, different or unavailable software and codecs, etc.

Easy examples: if you choose to run a completely free system most of the videos on the web today are unavailable to you (even counting the few YouTube converted to WebM), as are essentially all games on any platform. Also, you cannot have a smartphone (I think even OpenMoko needs a binary blob). These are inconveniences.

RMS thinks freedom has higher value than having the ability to choose whatever hardware you want, so he picked the only laptop available with free firmware.
You could do it effectively if you could create some massive dendritic type structure with a huge surface area of flat panels to absorb CO2 directly from the atmosphere. Since the CO2 concentration is so low you would need vast areas of these CO2 farms and so you would have to put some effort into making them look artistically pleasant to avoid public opposition.

The construction costs would be incredible, the only solution would be some sort of von-Neumann type nano-machines that could manufacture copies of themselves and gradually 'seed' the system over a large landmass.

Liquid fuel would be easily tapped from the trunk of these structures - although persuading people to consume a high colorific value syrup type liquid produced by bacteria on their pancakes could be tricky (unless they were Canadian)
Why blindly following meta tags is a bad idea.
what? no one is blowing this out of proportion at all... no one has said some CEO knowingly went to Apple's Xcode website and stole the logo for profit. this however does illustrate perfectly how stupid the SOPA/ACTA brand of infringement enforcement is. no one was making any of the claims you said they were making, they just commented its hypocritical for NBC to be supporting strict enforcement with website takedowns and fines when they casually infringe themselves...

I really dislike posts like this that go all sanctimonious and apologetic when no one is making the outlandish attacks that you claim they are making
Ok, but what is RESTful thinking?

The way i think about REST is this: here is my stateful application, how can i make it available over HTTP/REST. So i start identifying resources. Most of them are easy - they map to your domains models. But some of the operations on some of the resources are quite important to my application (eg: ordering products, making a payment etc), so i consider creating separate resources for them.

It looks like you are referring to modeling your stateful application when you talk about RESTful thinking.
> the simplest things, like a better user experience

A better user experience is simple for users but requires non-trivial levels of design expertise, direction and buy-in from leadership. It's not at all surprising to me that in a heavily corporate environment with two CEOs, this would be an impossible needle to thread.
I'd start with Nail it, Then Scale It.

Specifically for customer development, I'd check out The Entrepreneur's Guide to Customer Development: A cheat sheet to The Four Steps to the Epiphany.
People have a huge capacity to adapt. For single people the flexibility is even more. I'd say, even if you go to Cicely, Alaska you'll get used to it and like it.

Now, if you would like to innovate, and be part of something big, your chances of realizing those are very slim if you live outside the big magnets. SV, New York, Boston are fine but the opportunities diminish very fast as the density of tech companies gets smaller. There are interesting exceptions though. For instance the Raleigh-Durham area has a good combination of schools (fresh talent), and tech companies. If you are at that point in your life that you need to choose where you will pick a home, think carefully, and do your research.
On the plus side for Facebook, they only care if you get reported by another user. They don't seem to be running any sort of automated "fake name" detector.

On the minus side, some people on Facebook use reporting as a form of trolling, and it appears to be fairly easy to get people kicked off of Facebook with enough flagging persistence. For friends of mine who run a religious ministry, basically everything they post gets flagged, and they regularly get kicked off the site for a few days at a time. They've finally gotten it under control after several long phone conversations with FB support.
> But it's just a tool, and if you can't grok that, you're probably a tool as well.

Unnecessary. All tools have a learning curve, a conceptual slope leading to the sweet spot. Being low on the curve does not make one a tool.
It seems to me the confusion is over what OpenStreetMap wants to control and what copyright allows them to control.

The 'shortcomings' of CC-BY-SA noted in your first link seem to boil down to use cases involving chunks of data that simply do not qualify for copyright. Thus, by definition, no copyright license could behave any differently than any other in determining what can and can't be done with those chunks of data.

A Terms of Use agreement (and enforcement) could do more, but the particular copyright license is simply moot.
I wouldn't worry, if there really is a market for those things you listed somebody else will step up to fill the gap. Especially with enterprise customers who rarely go un-served for very long.
Animating Game Menus and Screen Transitions in HTML5 for Developers
It's particularly annoying that the counter re-runs from zero just by refreshing the page -- and yet shows the same final count each time. Is it even actually dynamic, does the counter increment in real time if there's a new share while you're on the page?
But then your issue is not with "agile" or "scrum", it's about how people abuse the notion of agile or scrum. It's the same with every other tool, programming language or process. They get abused by people pushing their agenda.

I've seen organizations that started calling their lack of planning "scrum" because that sounded better than saying "d'oh we just make up our mind on what to do every couple of days." But that's not scrum or agile and it's not the fault of people applying or promoting proper agile techniques.
http://en.wikipedia.org/wiki/Michael_Scott_%28The_Office%29
Agreed - if Samsung cloned this grey, bulbous plastic tablet along with its screen printed label, I don't think Apple would care at all. It's the fact that they're copying the exact combination of flat glass front, curved metal back, black plastic buttons, visible camera, etc. etc. that they think is a problem.

There's no prior art for an industrial design like the iPhone 4 or the iPad, and other manufacturers than Samsung, e.g. Motorola, HTC & Nokia, seem to have no problem creating alternative designs.

It's easy to mistake Samsung phones and tablets in public for their Apple equivalents, and that's what Apple thinks is wrong.

Whether we think outright cloning of designs should be wrong or right is a separate question from judging whether or not that's what Samsung are doing.
I'm having some serious Déjà vu on HN recently. This came up a while back I'm sure.

http://mashable.com/2009/08/22/knight-ridder-tablet/

http://www.dailymail.co.uk/sciencetech/article-1381528/Knigh...

I can't find an article, but I'm sure this had already been in court. Or maybe I'm going senile at 32.

Also, I have a niggling feeling that Apple had a part in this video. But I could just be making that up.
Conditional upon every book a publisher invests in being successful, yes, this would be okay. But you need to provide enough runway for publishers to earn enough profit on their successes to offset the losses. Otherwise you're reducing the returns on being a book publisher and implicitly discouraging publishing.
I think he's talking about himself, not dumb readers.
POST /orders/42?pay=1

POST was always about actions, not just resources.
Correct. It's conceivable that you could find a secondary source in their reading list that links to a primary source, but in practice going through their list of sources would be much slower than just doing the search yourself, meaning that site has zero utility in practice. (Assuming you care about the information you're getting being true, if you're writing a middle school paper about penguins then it probably gives you enough plausible deniability for having done the work, but for anything else there isn't much point.)
"Unfortunately for Samsung while elements of the iPad design shows up the Galaxy pad is a lot closer to the iPad than any of the other designs. For design patents to be meaningful they must prevent such overt imitation and force competitors to do more than copy good design."

I don't think that would matter if the design it self is generic - not an innovation (as in this case) and hence the patent it self can be considered as invalid.
"with ARC you don't actually have to do anything as a developer"

* With the caveat: if you're using blocks, you need to be careful about unintentional circular retains, and sometimes take extra steps to avoid them.
I'm surprised that it took this long for that video to show up as evidence. The only thing it does not demonstrate is the use of gestures which is integral to the usefulness of this generation's tablets.

I've always felt that the basic form factor patents Apple has would not ultimately hold up, and it would be insane for them to try and enforce them. But it still does not excuse the fact that Samsung tries to confuse the public that their product is pretty much an iPad/iPhone. They do this through marketing, packaging, peripherals, software and UI design.

I don't like the patent system the way it exists, and I think most of Apple's 'key' mobile patents are ridiculous, but I equally can't stand a company like Samsung that comes in and says we're just going to commoditize a great product by cloning it and selling it for cheap. I think this is where Apple's emotion comes in and the 'sue everyone' mentality takes over.
Will Apple Become the Next Sony?
Look people. We all know that SOPA sucked. Personally I called my congressman and suggested the following amendment to SOPA:

When the dept of justice (or whoever is tasked with prosecuting these sites) finds a site, they contact it and issue a invitation to participate in domestic proceedings, and the invitation is good for a certain period (30 days for example). During this time, the site can respond, realize the problem, maybe make amends or reach a settlement. If they do not respond within the time period, then they are considered in default, and US financial institutions, search engines etc. could be compelled block them. However, at any time they can start legal proceedings within the US, and try to get reinstated, until the statute of limitations runs out (a few years).

This would have introduced the proper concepts of due process (inviting them to participate and offer them an opportunity to resolve the matter before taking drastic measures), jurisdiction (only US financial companies would be compelled to stop dealing with them, and possibly search engines, etc.) And IMHO it would be a good compromise.

Finally, here is why it would work: it takes a while from a site to grow from an insignificant pirate hub (where people can download movies, etc.) to something that lots of people in the US know. Remember, the problem is only that US citizens are downloading pirated US movies & shows (which cost a lot to make) from abroad. Once lots of people in the US know how to get to it using domain X or method X, then the entertainment industry can take notice. By that time, the site has been operating for a while (probably over a year). What is another 30 days at this point. The due process should take place. The entertainment industry is presumably going after big fish, not fly by night file hosters. So there is no reason to shoot first and ask questions later.

I am probably going to get downvoted because I am talking about SOPA and saying it could work using some sort of compromise. But I try to be open minded. Those who know me know I criticize copyright, but I don't think our society is ready for a completely wikipedia-like approach to art. I have thought about the issue and in practical terms, copyright is actually quite useful as it enforces copyleft. And in fact, using copyright and copyleft, we have a competition of content creation by open groups and by proprietary interests. Which is good for society. Patents in software, on the other hand, should be abolished :)
The real short answer seems to be: encryption is done client-side by Javascript.

I'd worry about the extra attack vectors because of that - man in the middle, snooping browser extensions, etc (or even just strong-arming them into silently changing their javascript do no encryption)

To his credit, he writes about this as well:

> On a trust scale, is it better to use PGP or PrivateSky if you want to be 100% sure that no one can see your data? Answer: There is no question that [...] a system such as PGP is better [...]

> There is only one problem. PGP and the current state of the art are too damn hard for the general population at large to use. [...]
If your startup sells to other startups, it is very important.
If you lack a skill and need help with something, it is very important.
If you are looking to be funded by a startup incubator or something similar, it is somewhat important.
Otherwise, find an idea and start building.
To me the bigger problem is that after a short period of time any successful work would be fair game for large corporations to exploit without compensation to the creator. So they just wait it out instead of dealing with the creator.
I've always liked http://placekitten.com/
The New Yorker digital assets are a completely technically suboptimal solution. Obviously in life other non-technical issues can take precedence.

The New Yorker online edition (archives.newyorker.com) consists of a javascript interface that displays 760x556 jpegs for browsing. Now we get to the good part: if you click on a page to zoom, it brings up a 1228x900 png overlaid on a 1228x900 jpg. The png is the high frequency information (abrupt black and white transitions) and the jpg is the low frequency information (large swathes of colour). I’m confident the data is processed by DjVu to perform this image separation (if you dive the image urls ‘djvu’ is one of the directory names). The hilarious part is that they OCR their images and this text is in the html. Even more fun is that there is a separate 1613x1181 jpg when you print from the online edition but as we know jpg is totally inappropriate for black and white text.

So to summarize the data is already passed through a DjVu toolchain to generate a djvu file but they render all of these ridiculous image sizes in various formats to fit their terrible viewer.

I don’t have an iPad so I can’t confirm but I’m pretty sure the Kindle New Yorker app runs on the same Adobe AIR platform. For the Kindle, each issue clocks in at around 100 MB and consists of a 1024x600 png for each page (I assume the iPad images are 1024x768) and a whole bunch of other HTML/XML assets. I’m running this on an android phone and the issues are stored under “/mnt/sdcard/The New Yorker/.library/The New Yorker/” so the data structure is pretty transparent.

Harper’s is much more sane: they serve gifs or pdfs. From the pdf properties it’s obvious it’s direct output from QuarkExpress.
Python objects, types, classes, and instances – a glossary
These are non-OTA updates, so I'm not sure that analysis holds. Note that the Verizon CDMA Galaxy Nexus ("toro") is in a similar position, but that JBQ promised an image would be coming soon.

I think a stronger case can be made that Google lacks an architecture like the desktop distros have where they can update packages independently. Why should, e.g., UI improvements to the shell or bug fixes to the settings app be held back by driver validation for an LTE modem?