skysight-inc/HackerNews huggingface dataset:
[B]ut there are also many great UK based programmers and companies in the UK who could have developed a home-grown solution.

Would that have been more cost effective?
That did make me tie a string around my finger, but there's no particular line in the article that you should read as me referring to him.

The editorial calendar basically dictates that I have to talk about A/B testing for the time being (product launch and all), and I generally prefer to say new things rather than saying old things. I've written an awful lot about A/B testing from different angles, but have rarely said "Actually, hold up, don't do it."

I previously had, if anything, a little too much "All I have is a HammerFactory so all problems must implement INail or they will be recast until they do" going on due to my own business history. I've talked to many people who have that to varying degrees over the years.

So "Hmm, as I come to be a little more mature in my understanding of this, there's actually some times where I wouldn't reach for scalable, metrics-driven, quantitative conversion optimization as the first solution" seemed like a pretty good skeleton of a piece.
The biggest contributor to performance issues these days, from what I've seen, is synchronous code. The JVM can be blindingly fast at running your code, but when it hits a point where you make a database call or web services call that's implemented synchronously, it sits there, waiting, doing nothing. No amount of VM optimizations can increase of the speed of idling code.

This is why Node apps often out-perform Java apps despite running on a VM that's significantly slower. Node is pervasively asynchronous...it's baked into the DNA of the platform and almost all libraries follow that philosophy. And as organizations move to a micro-services architecture where one external call can result in multiple internal calls between systems, the need for reactive, asynchronous programming becomes all the more glaring.

That's where this critique, for me, fell down. It's spent too much time comparing the JVM to V8 and not enough time talking about how the applications being run were designed. Because CPUs are fast enough these days that any of the VMs will give you decent performance for workloads that aren't CPU-bound as long as you, the application designer, do the right thing. It's just that some environments, Node in particular, make it easier to do the right thing. This will get easier in Java with the introduction of lambdas in Java 8 and the inevitable asynchronous community frameworks and libraries, but right now it's still harder to write reactive applications in Java than it is in Node.
> There have been plenty of Android phones with hard keyboards but they've not sold in sufficient quantities to make it attractive.

They haven't sold because they've sucked. They had low-quality displays, crappy software, slow SoCs, and barely enough memory to be usable. The only keyboard phone left is BlackBerry, and that's not selling, well, because it's a BlackBerry.

There is a huge market for regular keyboard cellular devices. It's just that nobody's made a half-decent phone along with the keyboard.

If there is a device with a physical keyboard, a tapered, curved design, high quality components, a top-notch display, excellent build quality, the latest versions of Android, and good marketing, and you have a winner on your hands.

It's just that idiotic OEMs like HTC and Samsung would rather follow the fruity status quo than break from the norm. Only BlackBerry seems to have any balls today. Shame they're practically dead in the consumer sector.
Here's a thought. Remember that whole parallel construction thing everybody was freaking out about?

The NSA passes the FBI a tip. The FBI needs to get this tip admitted into evidence, so they claim they overheard it on the phone. One snag: the target's cell phone was turned off when the conversation took place. Solution: a magic bug that can listen even when it's turned off.
do you know about Picturelife?
I'm not sure why you are conflating a watermark with DRM in the first place, or how you could possibly think this has anything to do with 'RIAA-type people'.

I'm honestly not sure what to even say to you because you aren't making any sense.
General comments:

-Only a fraction of cases have comments, but your search function pulls up all of them. It would be nice to filter for annotated cases.

-The home page should have some categories that people can browse through, instead of just showing recent comments. For example, it could show common use cases like IP agreements or freelancer contracts.
Alberta leads North America in economic freedom
This is a great initiative but as long as these images aren't reasonably tagged they'll remain undiscovered.
Fine for me. Get the latest version of Chrome (it includes some anti-aliasing differences). Maybe just restart your browser if update is already downloaded.
Regarding the shameless product plug: Quay looks like a very cool product. Love the history and diff views. Glad to see pricing mimics Github model "pay for private, but public is free and unlimited". Awesome!

Regarding complexity in Docker: So here's the thing, people wanted npm, but they got git. How can we bridge the gap between a easy to use, out of your way package manager and a fully featured DVCS experience? I love the idea of merging them, but IMO, need to make the semantic model more accessible. Specifically, need to ensure concepts are properly orthogonal, not overloaded, and unambiguously defined. Might be too late to scrub this aspect though.

Some other general problems are things like checksums, fingerprints, image signing, etc. How to verify the validity of an image?
Would you share some of the "pretty obvious" examples?

Not everyone is a genius and the fact that I can't figure it out, actually makes me feel insulted by your comment. The tone is just obnoxious!
Color Tiger dev here - actually with our version and root access you can install a recompiled version of AppOps with a few extended features as well - rebranded as AppOps X
That link doesn't actually bypass the paywall.
Ah, ok this makes more sense, thanks for explaining. I can see why this would be troublesome.
I prefer to see it as a way to improve UX by learning what the confusions/unknown features are.
It appears you are either trolling or simply don't know what are you talking about. Either way there is nothing to be gained from this discussion for either of us.
Here is the thing I made: http://www.youtube.com/watch?v=XUbOQjEiI9A

As a Ready file: https://reaction-diffusion.googlecode.com/svn/trunk/Ready/Pa...
Your 'How it Works' video doesn't really make clear that its two browsing panes.

Also, just a personal quibble, I dislike people who use the "Or better" When they mean 'or newer' when referring to an OS.
Not to nitpick but artificial selection in plants started a lot earlier than Mendel[1].
http://en.wikipedia.org/wiki/History_of_agriculture#Developm...
I have done this before, I've done experiments where I meticulously monitored all HTTP requests sent and I could've sworn I saw questionable activity. Doing it now I get results that seem similar to your description.

I don't know what to say, other than that experience has taught me to always be on the skeptical side of things when we're talking about Facebook.
I had to plug that link into a Google search to get it to work.
Forget Academia. Startups Are the Future of Knowledge
Why doesn't anybody exploit the never ending stream of Windows zero days to install blanket ad blockers on every machine possible?
"It fosters Anti-Patterns like 'Dependency Injection' that give you the illusion of modularity but instead create dependencies within the application ('Dependency Injection' needs to be taken literally)."

What? Any system with separated modules is going to have dependencies. At least with DI, classes are written to a interface and different versions easily be swapped in and out.
Is there a limit to the number of orders you can place? Instead of filling a single box over capacity why wouldn't I place two different orders instead?
> OOP actually doesn't model the real world well at all. It seems to on the surface, but it completely ignores time.

This is important, and something almost everybody ignores.

Get an OO codebase, and try to implement a time-dependent feature, like snapshots, or even a simple undo. The abstractions fall apart.
Does this mean one can use Dart instead of javascript ?
> Unfortunately, what we know about epistemology is contained largely in the work of the philosopher Karl Popper and is almost universally underrated and misunderstood (even — or perhaps especially — by philosophers). For example, it is still taken for granted by almost every authority that knowledge consists of justified, true beliefs

-------------------

The Gettier problem has been well known in Philosophy since the 60s. Probably the most famous example would be barn-façades, first showing up in the mid 70s. It's taught in undergraduate courses. It's the second bullet point on the Standford Encyclopedia of Philosophy's Epistemology article.

-------------------

> How could I have ‘extrapolated’ that there would be such a sharp departure from an unbroken pattern of experiences, and that a never-yet-observed process (the 17,000-year interval) would follow?

-------------------

One rather assumes your experience with numbers has included 20 following 19 before and you extrapolated the rules from that and similar experiences with assigning numbers to things. You were, after all, previously told that it's how years worked - and doubtless you've lived through at least one year changing.

-------------------

> Even in the hard sciences, these guesses have no foundations and don’t need justification. Why? Because genuine knowledge, though by definition it does contain truth, almost always contains error as well. So it is not ‘true’ in the sense studied in mathematics and logic. Thinking consists of criticising and correcting partially true guesses with the intention of locating and eliminating the errors and misconceptions in them, not generating or justifying extrapolations from sense data.

-------------------

Be that as it may, some guesses are better than others. Generally the guesses that are based on more data. You lock someone in a room for 19 years, don't talk to them beyond the basic social interaction required for them to develop language, and then ask them to guess what an atom bomb is, they're not going to get very far. Even guessing what an atom is, or a bomb they'd be hopelessly out of the context of their experience.

Guesses, in so far as they're meaningful, have foundations. Those foundations limit what you can guess about and have any practical chance of refining towards truth with more evidence. You can't start off knowing nothing and then go to nuclear weapons in one step. You have to make smaller guesses, based on what you know.

And much though the author you might criticise Bayesian probability, this is bound up in the idea that probability is based on dividing the search space between the explanations we can come up with for a thing and then weighting it with evidence.
In my case, I'm speaking of a reaction to Spring and Struts. I personally use Grails on my recent projects, which is as close to batteries-included as it gets, but I occasionally have problems with square peg round hole problems, and fighting against a framework is more painful than a library.

The problem with the framework is that we run into a steep hill when we must diverge off the path. A good framework gives a great story. Unit tests, integration tests, consistent layers, convenient and powerful ways to access the database without writing a giant SQL generator (if x return "and b.id = c.id" else return "b.name = "%" + name + "%")...

But then, you hit the use case that the framework didn't consider. And suddenly, you either need to extend the framework (never pleasant) or go outside the framework for one portion, which means building all of the tools from the ground up.

Or, more often, ignore testing, hack in the best way you know how, and hope nothing breaks.

The library approach means that you have to build the integration pieces yourself. This is painful, but it means that when you reach a new use case, it isn't as large a jump to keep going.

Each has tradeoffs. There are times when each is superior. Someone like Bob Martin would suggest that you build your system independent of frameworks and treat the web as a client/compatibility layer, and that you build your system of small composable parts so that the framework/library question is a minor one. (This has its own tradeoff with an abhorrent amount of plumbing code that comes along.)

It all comes back to the problem at hand and how we judge the tradeoffs, like most engineering problems.
If your parent's post ruffled your snark-feathers, your sensibilities may be... overly sensitive.
Aside from Garry almost always being the one YC Partner we could guarantee would show up at every drink up during our batch of YC I always enjoyed his straight to the point feedback and awesome design opinions on our product.

It's an honor well deserved. Congrats Garry!
Yes but they have a strategy to address that:

> We plan to launch a crowdsourcing application at the beginning of next year, to help describe what the images portray. Our intention is to use this data to train automated classifiers that will run against the whole of the content. The data from this will be as openly licensed as is sensible (given the nature of crowdsourcing) and the code, as always, will be under an open licence.
NSA review to leave spying programs largely unchanged, reports say
I like how simple it is but support for albums and account support should come as well.. unless your goal is to remain completely simple.
Well that's easy then. What says we have to feed everyone?
> Jeff Hammerbacher is founder and Chief Scientist of Cloudera, Assistant Professor at the Icahn School of Medicine at Mount Sinai, and Director at Sage Bionetworks. Formerly an Entrepreneur in Residence at Accel Partners. Before Accel, [Jeff] conceived, built, and led the Data team at Facebook.

Well, he could start by not working for institutions whose entire business is predicated on making people click ads.
The first few lines in the article mention that the bulk of the work was done by Microsoft in digitizing the photos.
Not yet. And even were Dart ratified, the answer would still be the same as it is today: you can use Dart if you cross-compile it to JavaScript, or if you only care at all about Chrome users. Both are fine, but they mean that, for you, Dart is either just another compiles-to-JS language, and therefore not special simply from having ECMA status; or that you might as well also feel comfortable using PNaCl.
Don't count on it. There are many software developers out there with knowledge of NLP algorithms, statistics, symbolic systems, etc. who aren't employed by Googles, Facebooks, Ciscos and Twitters. They're bored out of their minds and waiting for a challenge.

As time progresses, SEO companies will adapt. I contributed hundreds of thousands of pages of web spam prior to the Panda modifications. If I were still working at the company I did it for, and there were proper incentive, I would definitely be able to get around Panda.

It took me about 10 hours to build a cute little tool, and after about 3 months of using it judiciously, we were able to push many sites up to number one for some very competitive terms. The search engines might be ahead now, but there are thousands of intelligent programmers out there trying to pick the black box apart. No black box stands unbroken forever.
Fear? No, I don't think so. I think there are a lot of people who are eager for business models that don't include having your data sold, or being advertised to.

Adoption of adblock isn't something that is happening too fast to respond to, and it is a good thing, I believe, because it should create some innovation on the monetization side. Ad revenue isn't the only game in town, and I think consumers are receptive to other models that give them more control.
>The expression problem is much safer solved using virtual classes (using traits and type members) in scala than with case matching.

Why do you think this? I prefer having an open trait that's only inherited by ADTs.

I can get non-exhaustive match warnings and I still 'solve' the expression problem by matching on a superset of my partial functions (that do the matching).
Visualize Chrome JavaScript CPU profiles using KCacheGrind
That works, but it isn't obvious to the user.
Very Cool. Can I have your email address?
Would really prefer java over php and JavaScript.

Closure, python, c#, f# over Java. But I quite like the java ecosystem. There's normally library for anything.
A lot of the quality of a mattress comes in how long it lasts, so the jury is still out on that.

Nevertheless kudos to these guys for building something high quality with low overhead!
Yeah it's basically a modification of a pelton wheel, sort of adapted for higher flow and lower pressure. Technically a turgo wheel IS a pelton wheel, but they serve sort of separate purposes.
Ok, thanks, I did not realize that. Still, it illustrates the fact that it is bad design if it is not intuitive to use. I interviewed multiple people and none knew how to dismiss it. Design should be easy to use and understand. I agree with @stevekinney
Well , Amazon does make a profit on every purchase. It's just that they think it is wise for the time-being to invest it in opportunities which will yield better value in the foreseeable future and I find nothing wrong with that.
Of course there are. It's called "Whole Foods Market".

The sad humor is the real profit is to be had when you can sell people nickle-a-pound wheat, and make them think it's premium product.
>> I'm not a TCP expert, but apparently the closing initiator (the client in our case) should wait for acknowledgement from the other side of the connection before dying off, see Wikipedia link above. So, I set process.exit() to run as a callback on the close event of the client object.

This highlights one of the problems with node. You can be doing the simplest thing and find yourself needing to deal with low-level details of TCP to make it work properly. Now that node has shown what's possible, I think there's an opportunity to do it better with fewer pain points.
I'm of the mindset that developing a home-grown/in-house solution when there are time-tested & proven solutions out there is generally a mistake unless you're trying to innovate and offer it to the public. I worked at a place where the devs thought apache2, django, rails, etc. were too slow so they made their own web-server re-implementing the whole HTTP 1.1 protocol from scratch....
Did Google autocomplete ruin this man's life?
Given them a license is necessary so they can display the images, but Google using the license to help sell competitor's products because Google does not want the burden of procuring their own photographs is pretty scummy.
Here's two links to the same story, as they cite the WSJ (and I can't get past their paywall)

http://www.theverge.com/2013/12/13/5208312/sprint-reportedly...

http://www.usatoday.com/story/money/business/2013/12/13/spri...
The question here isn't what makes sense logically, but what makes sense to the claims department at PayPal/eBay. They won't listen to you explain how the blockchain works, they'll ask for a shipping tracking number, and when you can't provide one, they'll say "we don't offer seller protection on virtual goods".
Hopefully it fails like the AT&T + T-Mobile acquisition!

Having 3 major carriers in the US instead of 4 is bad for rates. T-Mobile has been the first to introduce a few awesome service products (free int'l roaming data, unlimited data @ LTE speed, free data service for tablets).

When the last sale failed T-Mobile got a $3b breakup fee, maybe think they can do it again!
Flush with cash, Oculus plans ambitious new VR headset
For the record, it would be a bad idea to sell Bitcoin when Paypal is involved. Way too easy for the buyer to dispute the transaction, and Paypal typically sides with the buyer in these cases.
> "(by the way, GOG should pay you a commission for talking me into it)"

Haha, I wish, though GOG provides a service I'm thankful exists so I'm happy giving them a little boost every now and then when appropriate. They've always been good when I've had an issue with a game. I once changed my mind on a game I wanted and decided on getting something else (had not played or downloaded it yet). After dropping them an email, they were happy to switch it out for something else without an issue. Doing the same on Steam would have been like "pulling teeth" with their no refunds policy. I know they also have a new policy that if you can't get something to work and they can't either, they also refund you the money. I'm curious to if that applies to games run under WINE as well (I'm guessing it likely would with as flexible as they are).

I used to have lots of classic games from the mid to late 90s and early 00s. I lost most unfortunately when my parents interpreted me leaving them at home when I moved out as no longer wanting them period. Since the advent of GOG, I've rebuilt most of my collection by waiting for them to go on sale.

As far as prices for older games on there, they tend to stay pretty static for sale/non-sale prices I've noticed. Doubt it will go cheaper anytime soon. Even if it did, to me, a couple of bucks doesn't carry the "buyer's remorse" that spending 50 dollars on a game from Steam carries when it happens to go on sale the day after you get it.
The image of the farmer as a simple, non-tech person is pretty pathetic. The current generation of farmers are pretty sophisticated.

Many members of the current generation of farmers even have college degrees just as serious & relevant to their field as any other science.
Dropwizard is a bit heavy by Node standards. The health checks, in the NPM-style system, would be its own package. The configuration class would be its own package. Resources would be their own package. Liquibase or Freemarker wouldn't be built in, nor would JDBI.

I think of Dropwizard much like express for node, and most of the "cool kids" in the node community think that that's just too much for a single library.

I like Dropwizard, don't get me wrong, but it isn't quite a micro-framework by other standards.
Mini-hydro would be something in the megawatt range or so. Typical hydro plants are ten megawatt plus, up to 10 gigawatts.
>I don't think it will be best for consumers or the industry

Now again, do you think this because you don't like and/or use facebook, or do you have data to back this up?
Glenn Greenwald Interview
Safari on Mac stores credentials from previous session in plaintext
I really like the concept, but I found it extremely frustrating to draw and undraw the squares.
The IT Department Is Dead. Long Live the IT Department
They'd definitely pay if you stated it nicely. ("I would love to help you in removing these links, but my developers are occupied. If you want to expedite the removal, it will be $X per link.")

I get many requests a month to remove spam links that get through our filters. I've debated charging them for it, because I know in most cases the people asking me to remove them are the same people who had them placed there. I haven't charged anyone yet, and I don't think I'm going to.

I do take my time when removing them (lowest priority), and I don't remove the links where the requester cites some legal consequences if I don't comply. Those stay up forever.
"So why did it say that? I have no idea, but you can ignore it." - because it is "uploaded" from the CLI tool to the daemon. See http://docs.docker.io/en/latest/use/builder/#usage
The current theories of physics do not even begin to offer an explanation for "subjective experience"/consciousness, which definitely has everything to do with the brain.
"I don't know for certain that this has never happened..."