skysight-inc/HackerNews huggingface dataset:
> "Despite the importance of a shared standard, after six months of effort the Open Container Initiative (OCI) body has yet to decide whether it should or should not develop and standardize an image format. Today, the primary focus of the OCI community is creating standards for the container runtime environment, rather than the container image. Specs for container runtime features are also a worthy discussion, but we think there is a more urgent need – and a more open, industry-wide upside – for a standard container image specification."

I haven't been following the OCI at all, but could somebody shed some light as to why the runtime is the most important part to standardize? Also, any insight as to whether or not the container image format should be standardized?
> I'm not really sure why people referred for semen analysis would be a biasing factor in this when it is present in both test groups. It seems like it would be the only reasonable way to get statistical power in a study like this since if the effect is small and most people don't suffer from it there would be a much larger sample size required.

You're right, everything else being equal, that probably wouldn't be the biggest issue... Although in this specific case, it seems like a way to amplify the effect - if this study would be done on the general population, where (1) almost everybody uses mobile phones extensively, and (2) presumably, men are less likely to have poor sperm than in this focus group, the resulting effect would be diluted (as in most cases, mobile phone usage would not result in poorer sperm quality).
Just my recollections of java dev from about 2yrs ago...

Maven was complex, with too many 'concepts' for a build system. It was a revelation when I discovered dependency download and jar creation through apache ivy. Did Gradle take off?

Tomcat in turn had problems too, I recall JBoss was a little more robust, but also complex.

I also found hibernate/spring to be confounded by differences between versions - the XML config (of which there was a lot) tended to change in format quite a bit, and there was an added complexity in figuring out how to get code, and xml, or even code-from-xml to behave intuitively. It felt like a massive ORM, written in XML and annotated java...
No, they weren't going to do a public SDK, until after the huge sustained public outcry.

I understand the plan was to work with select third parties on a case by case basis, sort of akin to standalone game consoles.
to your point, imagine the bed-ridden mother of a tribesman of a remote village in Sub-Saharan Africa and you easily tack on 2 more degrees of separation (the tribesman who has infrequent contact with a nearby city and then his senior-aged mother).
One more data point: my friend is a doctor and has lived in the UK for about 9 years. She's terribly overworked and makes less than the stated amount.
A company patented the concept of making toast well after toasters were on the market. Another patented recurring payments of online service long after that was normal. Another guy modified a patent to cover podcasting after podcasting was invented and in use.

Point being, something being patented != something being invented. It just means examiners agreed with the claims of a piece of paper then turned that into a piece of intellectual property. The wins then mean courts agreed that claims in that property match some other product to some degree. Neither means someone copied someone. Whether that's true varies on a case by case basis.

I think it's telling that many defendants develop their own, "infringing" tech without ever hearing of the plantiff or their patents. Hard to copy what you don't know exists. In science, we call it independent invention but patent system makes that impossible. Plus, on software patents, what programmers have you met who comb through patent databases to solve their day-to-day problems? I've never met one.

Concluding, patents are legal pronouncements that may or may not cover inventions. Rulings on copying may be right or bullshit. Copying is usually unknowing or independent invention because nobody solves problems with patent databases in our industry. I remember running into maybe 3 or 4 worth looking at in Google search solving a problem. One was novel but others patented ideas already in products or Comp Sci literature. Well-known ideas that were foundational to product success. (sighs)
I'm working on this right now for my company. I have limited web developing experience though I've puttered around on Wordpress for about a decade and know some fundamental HTML and CSS. We're moving from Wordpress to Squarespace for both ease of theme customization (from a technically limited standpoint!) and overall more pleasing aesthetic. Our site as it stands is perfectly functional, but looks like it's from 2006, and we currently would rather not hire a web design company again and do it ourselves.
My 2013 MBA is ready to go pretty much the instant I open it up.
A newsletter subscription form doesn't count as a Show HN.

Please read https://news.ycombinator.com/showhn.html.
Interesting reading.

More of the same at http://tinyurl.com/p3apx37
You will never get there. It's just unrealistic. There are products that are too specialized and have no competition. There are long term contracts that prevent all sorts of efficiencies. There are parts of the supply chain that operate on timelines measured in decades.
I believe Google has made numerous pledges not to aggressively attack others with their parents the way Apple and trolls are doing it.

I think Facebook might have also done it too - wasn't there some kind of anti-trolling pact between several major software patent holders?
And that tiny slider that indicates where you are in the track. Very, very hard to move it properly. Wasn't so in the non-flat version.
I keep seeing Information Retrieval. How is it different from general search algorithm and are there grad programs famous for search? The only thing comes to mind is private information retrieval in security.
You seem to be out of date. npm 3 uses a flat directory structure, only nesting dependencies when there are two different versions.

That misinformation aside, all package managers are agnostic about how large your dependency tree is; the large trees are purely a consequence (or choice, depending on your outlook) of the community. Could you imagine a package manager telling you you're using too many or too few dependencies? If you want fewer dependencies, use fewer dependencies. npm won't get in your way.

Speaking of the community, it is primarily what people like about node and npm. Sure, there are lots of bad packages. That's a side effect of javascript being the lingua franca of the web. Everyone and their grandmother is writing npm packages, so of course there are going to be a lot of bad ones. _But there are also a lot of good ones._ npm has driven web development forward at such a fast pace, I wonder how anyone can't appreciate what it's done.

Finally, some stats: ~230,000 packages, ~3,300,000,000 package downloads last month. That is a lot of users for something fundamentally broken. I can only wish to work on such "broken" software.
General Catalyst: The Next Chapter of Our Innovation
Somewhere in the midwest?
The Steve Jobs method: hire really good people and inspire them to work to the best of their ability.

Apple UIs were better because they were doing what ESR suggested at a time when the rest of the world was smashing every new option into the right-click menu. Occasionally I'll still hear someone say, "Oh, just put that in the right-click menu." The right click menu isn't a trashbin to dump things that don't fit elsewhere. In any case, here is ESR's UI advice: http://www.catb.org/esr/writings/cups-horror.html
I wouldn't discount all the people who don't give a shit about being hip, but just want their devices to be safe and kick ass.

Apple haters seem to often have the misconception that people like Apple products for their style appeal. It's easy to think that, and not wonder if there are possibly some more important reasons.
It has been quite a journey keeping an indie online RPG going for 10 years, and we are committed to continue developing the game to ensure it survives into the future.
In the Desert
I was working the last year on a Django app. First I hated it, but slowly I started enjoying programming with it. This year I worked mantaining an app with all of this http://teropa.info/blog/2015/09/10/full-stack-redux-tutorial... This supposed to be a simple Web app but, it's a complete mess. I miss Django so much right now.
So now, whenever they have something patent-worthy, the company first sets up a new company, then file for the patent for that new tiny company.
This is a followup to https://news.ycombinator.com/item?id=10947023 (why people keep coming to one couple's house to find stolen/lost cell phones)
As far as I'm concerned this community could care less about people using idiomatic English, but we care a lot about personal rudeness in comments. Please don't do this again.

If you think a comment is bad for Hacker News, you're welcome to flag it, but not to post abusive noise.
I have always wanted to toy with this idea. I'd love to save up a nice chunk of change and build something like this.

I'd like a small house out in the middle of the country.

A bathroom with shower, a kitchen with a stove, and a single living space.

Solar panels, backup batteries, well with pump and filter, and a internet hookup (satellite/landline).

I was hoping to find that this article would talk about the prospects of building something like that, but unfortunately this article is not exactly what is in my "dream".
To help people trying to Google/understand the parent comment, it is spelled Jekyll.
Superb article, thank you. Makes me think about my resistance to a manager telling me to drop a particular piece of software or tooling in favor of something else.
There are many intercity distances for which a plane is sub-optimal but could definitely benefit from a faster terrestrial solution. This thing doesn't need to get to 30000 ft to achieve high speed. One could leave every X minutes because you don't have to fill a whole jetliner to make it cost effective.
Its funny watching the announcements of these products now.
Was going to mention the same - my standing desk has a standing-height chair that I can take breaks in without interrupting my productivity... This (along with not accepting that acclimation to standing all day would take some time to adjust) seems to be the missing piece of the puzzle for the author.
I'm happy going Apple with my tablet and Android for my phone (actually I changed again and went Windows Phone). So I still can access all those old games I had on my previous iPhone through my iPad, but I can enjoy new things and try out other phones and operating systems, and spend less money doing so.
Many programming language can build those same sites using template DSLs ala haml. PHP is like a template DSL without the host language. While PHP is in many ways mature, why start from there now?
You mean the United States consist of 200 states? ;-)

No, the embassy is no sovereign state. As your source clearly says it represents a sovereign state.

Just as Marissa Mayer is not Yahoo, but certainly represents Yahoo from time to time. And if she were ever invited back to Google for a nice cup of tea, Yahoo still wouldn't be owner of the Google's cafeteria, just because she represents Yahoo and happens to occupy a chair there.
I don't know much about search, but probably every software engineer should take some physics classes as well. Just to get used to that sort of reasoning, which is perfectly valid in a lot of circumstances.
SF foosball Tournament
[Location:]
Kennedy's Irish Pub and Curry House
1040 Columbus, San Francisco, CA 94133

- They have a huge selection of beer. Food is decent as well.
- 3 Tornado tables

[When:]
Every Thursday Night at 8:00 pm

[Entry Fees:]
FREE for all new players!

https://www.facebook.com/groups/sffoos/

Feel free to email me at lihster@gmail.com to let me know that you are planning on showing up or for more info.
Future Systems: What the Server of Tomorrow Will Look Like
>It's not really surprising that bulk surveillance is simple, in my opinion. The act of collection/surveillance itself isn't the hard part. It's doing it on a much larger scale.

Sampled netflow at 100k connections/sec is straight-forward. You won't do it with BPF, but it's straight-forward with technologies like netmap or DPDK.

Using "the web" as an example TCP session requires a 3 phase handshake (SYN -> SYN ACK -> ACK), then the client can make a request (GET / HTTP/1.0) followed by the response.

The SYN/SYN+ACK/ACK packets are 40 byte each (IP + TCP headers), plus another 18 bytes (DST, SRC, length, CRC), plus another 20 bytes of 'overhead' (preamble, SFD, IPC).

Unfortunately, minimum payload on Ethernet is 46 bytes ('octets'), so the actual on-the wire SYN/SYN+ACK/ACK exchange is 84 bytes each (includes all overhead). Even 1G Ethernet has bandwidth sufficient for 1.488 million packets per second at this size.

Even if all the frames on a 1Gbps link are 1538 bytes (includes all overhead), you still have to deal with 81,274 packets per second.

The HTTP GET request is likely between 100 and 1500 bytes (depends on headers), and, if we figure that the response fits in a 1500 byte frame, (1460 bytes of actual content, plus headers and overhead), we then have a 4 phase close (FIN/ACK from each side). These, again are minimum 84 bytes on the wire.

So the reality is that given a web server that doesn't spend too much time sending actual data (maybe several packets for the page data), it's easy to get to 100K connections per second.

However, 100K connections / sec (remember that's sampled) is 8.640 billion connections per day, and now you have a classic "big data" problem.
This Is How One Woman’s Rebellion Abolished Kerala’s Oppressive Breast Tax
Believe me, we've been hearing this too. We're super excited as well. :-)
1:45 on 10x10. i could see this as being addictive
This is what it should look like (and used to): http://i.imgur.com/jdOGdTI.png
Well, it punished them both. An ad network that can't display it's ads in places it could before is a form of direct punishment. Forcing sites for choosing ad networks that don't vet their ads well is an additional indirect punishment as well, as it may encourage those sites to choose a more discerning ad network.

On one hand it's unfortunate that the site is being punished, on the other hand maybe they deserve some responsibility for not being more selective. I'm not sure.
Airbus glider set to fly to the edge of space in record breaking 90,000ft test
It was just a few hours before the BBC published the leak.
The "asshole" in this case is JWZ, [randomly?] switching on the Referer header. Apparently he has a hard-on for HN; he's not the only one, but I won't be linking to his site again. (Although, is that really "obscene"? It doesn't do anything for me?) Try this instead, since Stanford are unlikely to engage in such shenanigans:

https://web.stanford.edu/class/cs240/old/sp2014/readings/wor...

It's funny, my original comment had the links in plaintext so copying-and-pasting was required and Referer wasn't involved. I changed that on request. b^)
Which means rent is still transferring money from the poor to the rich. If you have a mortgage, you're hopefully building up equity

Have you seen what percentage of your mortgage payment is equity early on? You're lucky if it's 5%. The rest is interest that goes to the "rich".

Not sure I see much difference between owning and renting when it comes to who gets the money.
I remember the time OS X didn't even have to restart for an update. Gone are those days.
Actually, it does, if you're using a chunk of your wind time power to pump water up a mountain for hydro storage generators, as happens here. it's almost always windy off the UK coast - most wind power is concentrated off north Wales, which is no coincidence, as snowdonia has several large capacity pumped storage systems.
Congratulations to CoreOS and the rkt team. I've been waiting for this to really dig into rkt, as I am a big fan of how CoreOS has been approaching this project, and eager for a container system that is not Docker.
Powerful allies are tasty.
The US has an even dumber version:

5) Nepotism. If you are related to or sleeping with a citizen, you have a very good chance at getting in.
Amazing idea. It will save so many people form mal-links but even sophisticated users from trying to figure out which is the real "download" button
We've banned this account for repeatedly violating the HN guidelines despite repeated requests not to do that.
> The bad part of this is the disappearance of WYSIWYG editors for HTML. You weren't supposed to write this stuff by hand.

It really doesn't matter what you were "supposed" to do with HTML. It's become something entirely different than what was originally intended.

When Tim Berners-Lee was at CERN he really just needed a way to link research papers to one another when, for instance, one cited another. His creation of the 'Web' referred to a web of mostly static documents. Nothing like the interactive applications we have today.

The fact that no WYSIWYG editor can keep up with the latest front-end application design trends is no surprise. (Would you expect a WYSIWYG editor for your iOS app?)
I've been waiting for Fabric to make the migration to Python 3. Fortunately I no longer use Python that much (I jumped on the hype train to Go and I've been very satisfied with it) so I no longer need Fabric nowadays.
I have. You'd think that sports team fanbase membership would not work at the scale it does. But I guess it serves as a means of establishing common ground quickly.

Though, since we're all humans, you'd think we have enough common ground with each other anyway, what with death, taxes, relationship problems, etc.
Everywhere else works better

> There are long term contracts that prevent all sorts of efficiencies.

Yeah, then those who signed those contracts will be less efficient, and maybe go bankrupt. That happens in several cases, not limited to healthcare
Ooh, good question... I just started using Steam for a PC port, and its killer feature is the way it only syncs the changes for each build. So I can fix a bug, upload an update, and get it in players' hands within minutes. I'd really like to see that on Google Play too.

In Play you currently have to split your app into "expansion files" if it's above the maximum APK size, upload each file in full, and then it takes hours to actually push the update out to users.
I'm surprised this isn't more discussed in the comments. It's a major element to consider when you're selling your business. He correctly identified it after all, as a potential deal breaker.

You're selling something, so in an acquisition you will have to represent and warranty what you actually own and you're selling. This sounds simple on its face, but technology isn't nearly so well-defined and legally sorted as, for example real estate.

In software, even if you are 100% certain you can transfer all of the code and there are no potential content copyright issues or latent prior agreements by yourself or other sellers, current/former employees who think they own something, etc, you still have at a minimum, a hard-to-quantify "Sword of Damocles" in the form of thousands of potential patent claims hanging over you, trolls or not, it doesn't matter in a sale. As in business itself, the bigger the money involved, the more visible you become to potential claims.

A publicly-traded buyer is likely to be less flexible on terms, but in any case you as a seller have also to consider that in a sale, you're most likely going to be forced to shift liability from your corporation to yourself personally. If you're prudent, as this seller was, you realize this creates a time period increased personal risk, despite your increased assets. Keeping this period as short as possible and limiting its scope and magnitude is your objective.

A few limitations I can vouch for making it past public company scrutinity are 1. any dispute costing less than $X are not your responsibility. 2. a maximum liability limitation equal to the purchase price in cash / shares (in case share prices drops) 3. a time limit of two years or less. 4. escrow of a portion of the purchase consideration (shares and/or cash) as a warranty cap for the duration of the warranty, perhaps with release/reduction over time. The tax treatment of this arrangement would have to be considered carefully.

Finally, it's worth noting that insurance for an acquisition deal may be available from big name insurers, likely for some low single-digit percentage of the deal value. However, their legal department will undoubtedly be more sophisticated in this area than your counsel, so at its worst insurance gives you little more than a contract with an insurance company over which to sue, likely at great cost.

Overall, as lawyers always say, "it depends." Unless the deal and/or your resources are immense, likely it is a problem with no risk-free solution. If you're young and have nothing to lose, risk is an easier choice. For everyone else, all you can do is optimize based on present knowledge.
People compare it to what's currently available, because if it's not any better there's no reason for customers to use it, which means there's no continued revenue stream to fund developing something better.

The Wright Flyer was far cheaper than the Hyperloop will be to develop, and airplanes had uses beyond just transporting people (namely military, which meant government-subsidized development).
At this point we should probably agree to disagree on some of these finer points.

But I do think that you are tending to blame agile for what really sounds like poor management. Management wants to see what progress is being made, so they use burndown graphs. Development, as you point out goes through spurts, except for the most basic tasks. So to management it can look like there is no progress being made.

What I'm trying to point out is that trying to divide the problems into as small of a set of isolated
components as possible may help get to a solution. But that doesn't say your wrong. It might take months of time to find that solution, the problem is you need to explain to someone over that time what you're doing, otherwise the money and project will be cut. This is where it can be good to try things out and show what you've learned over that time, this is important for managing up.
I can only conclude that the people sending such letters had only previously used GTK+ apps on Windows or something.
Location: London, England

Remote: Yes

Willing to relocate: Yes

Technologies: Common Lisp, Bitcoin

Résumé/CV: http://hn201512.no-ip.org:8080/sentient?resource=resume.pdf

Email: as on CV
Its the eternal battle between leanness and bureaucracy, the later always stealthy infiltrating to unfold its corrupting influence. Then its up to the mature developer to pick the proper technologies for the job based not on fads but on real project needs and wise criteria.
Not everything coming from SPAs is bad; reactive programming is awesome when you implement it in your own lean way with small friendly libraries like ractive, blaze, etc.
I've never understood why Polanski is still in Europe. I get why Poland and France won't extradite him, but all the other European countries he set foot into. Including my own.
I read that as sarcasm, it's making fun of the idea of writing a story about limited adoption after such a short time (and given the mentioned hurdles to switching), not actually mocking the 98.8%.
It's not purely that simple. Ideally, the farm owners are trying to hit the price point at the intersection of the supply and demand curves. If the demand curve was perfectly inelastic your explanation would be sufficient, but most consumers are going to balk when a carton of strawberries reaches a certain level, and therefore the market is putting downward pressure on the price due to demand.