skysight-inc/HackerNews huggingface dataset:
Well, first, he's a got ton of really interesting and crazy experiences, and translates into it practical knowledge... second, he goes on writing tears every now and then and cranks out a lot of quality content, then gets quieter for a while.

I actually dislike him on a personal level and think he's a jerk, and disagree with many of his philosophical stances, but despite that it's hard not to respect the guy and his writings and desire to give back / share his knowledge.
The space elevator to the lunar surface that 'could be built today'
> Even if it were possible to make money under this model, it would be much less than the big media companies are making now. Why would they switch?

Well, they're not making money from these people anyway, why not find a way to monetize them? You don't cease your current distribution practices, you are merely creating an alternate way to monetize those people who you viewed as "stealing" in the first place.
Webapp idea: cross-reference an iTunes library with mp3s available via torrent (or ed2k/kad) of similar quality.
Wow, who do you know? My niece cost double that, as I recall.
They're obvious features now because we can actually use two objects (our fingers) to interact with the screen at once. Pinch to zoom wasn't at all obvious when everything only could be touched once (PDA's) or not touched at all.

It seems only obvious to pinch to zoom something, but we could not have done that until a full touch interface.
Gist Archive:Github gists archive
The tricky aspect here is that most people believe that taste, and the 'quality' of artistic work, is mostly a subjective matter, but when they make criticism of art they treat their views as objective truth. Thus when you criticise a friend's work, or vice versa, the temptation is to think of it as "(Your|their) work sucks!" instead of "Oh well, (I|you) didn't like it, maybe someone else will."

Semmelweiss, on the other hand, had no subjective matter. He had the statistics showing that as soon as doctors started washing their hands, infant mortality went way down. It was just the doctors' pride which made them think he was accusing them of regularly killing newborn babies.

Of course there is bad art which everyone agrees is terrible, and telling people that truth is hard. In the end, though, it's better to be honest because it's probable that your friend would respond with a determination to do better next time. The trick is to be tactful.
Find out how the cloud is changing Europe
> Even this remains to be seen. I don't think vanilla Android is going to be affected very much.

You're obviously not familiar with the lawsuit on universal search. [1] Apple forced Samsung to remove a feature from its phone. Even from the stock Android Galaxy Nexus, which is much different from the iPhone. This lawsuit is already affecting consumers today. My tablet was just updated yesterday and had universal search removed. Meaning Apple already directly made my device worse.

[1] http://www.digitaltrends.com/mobile/galaxy-s3-loses-universa...
By the sounds of things, these are temporary satellites not supposed to last for very long, so the long-term aspects of radiation damage might not be such an issue.
Really good stuff. I'll try to take it to heart.

Thanks for sharing :)

Small gripe: 30em-wide text is pretty tough (for me, at least) to read on a high-res display
"sending a message" and "being 100% fair" are mutually exclusive. "Sending a message" is explicitly overpunishing a transgression so that news gets around about the harshness of the penalty.
I really wish I could read this but the text is 0.1px big. ;-)

Seriously though, great article.
If you didn't comment on the writing as a whole then I'd say your lack of enthuasism spoke volumes
I'm an RDF kool-aid drinker, but removing friction for adding somewhat structured content is always OK for me. I'd rather have a standard way of converting from the business.txt format to RDF than not have the data at all.
Oh look, another flawed comparison that doesn't take into account the realities of digital distribution.
I'm not saying it's better. I'm saying that it's less painful than many Americans believe, and that if installing the OS yourself with a microSD card became necessary in order to work around the patent system, then it could very well become a reality.
Analog is far more energy-efficient than digital, though, because digital is really analog with huge gaps inserted to make the 1s and 0s detectable and not look too much like 0.5s.

So there is a theoretical possibility that the efficiency benefits could outweigh the complexity liabilities.
I have to say thanks for writing this; I am starting to try and pick up Clojure at the moment, and it's always nice to see lots of different and interesting examples (see: recent 'Caves of Clojure' series that was on here)
I can't state for sure what is the legal status of UKNova. However, they have worked with copyright holders to ensure that they are not infringing. Most of the content is free to air British TV shows, that in many cases can be downloaded for free from within the UK. UKNova helps make this content available outside the country.

Their policy is to take down any content that is available commercially. IE: once the box set comes out, you can no longer share it. Other specific content cannot be shared even if there is no non-commercial source. It is easy to get banned from the service, so users are very compliant.

There are a lot of expatriate Brits who will miss the service, not to mention fans of British TV everywhere.
"Take the patent system away, and all Apple has is a nice market share, a fat war chest and it's own ability to produce interesting products."

Also the fact that Apple is the most valuable company in the world.
Would you mind explaining the hidden complexity in it? The claims certainly seem obvious and trivial to me as well.
> You can't run GPLed software on iOS.

This is 100% not true. GPL v1 and v2 are fine and v3 has some questions that most people avoid by sticking to v2 of the license. There are, however, GPL v3 licensed apps in the Apple App Store which you can find if you only looked.
Getting The Right Fireworks For The Occasion
Yep, "Perfect" is the worst enemy of "done". Users don't view source before they open their wallet.
Don't write bad code, but don't avoid writing code, as it will be never be perfect.
I found your post on Twitter and found it pretty useful, mostly because I'm reading the same book as you are(Clojure Programming) and was having some difficulty groking this program. Your post really helped.

There is a typo in line 8, I think it should have been (range h).
This reminds me the best running advice I ever received. In a comment when asked how to run fast, a very accomplished ultra runner replied, "If you want to run fast, run fast."
A similar resume to the late Steve Jobs
100% accuracy does not exist in real-world systems. 99.99999% accuracy might be good enough, though.
Your link doesn't cover anything about why/how blue LEDs are used.
For an obituary for Leonardo I'd use a portrait of Leonardo.

I'll add a bit more nuance to that - people don't always read every word of a newspaper article. That's fine, it's why the inverted pyramid [0] model is used. If there's a big headline (Neil Armstrong Dies) and a single photo (the one of Buzz Aldrin) and the fact it's not a photo of Armstrong is in a little caption, it's going to contribute to the misconception that the photo of Aldrin is actually a photo of Armstrong.

Contributing to misconceptions is bad and should be avoided. Luckily this is easy - just use the photo of Armstrong in the lunar lander.

On the other hand, it's unlikely anyone would mistake Leonardo and the woman in the Mona Lisa so it wouldn't seem so bad to me!

[0] http://en.wikipedia.org/wiki/Inverted_pyramid
"IAP only works if you nag or tell each user about it by locking them out of what they want."

This is hard for most developers to understand: you have to create a pain point as costly as the IAP upgrade for the users, or else they won't upgrade.

The cost of free should be in lack of necessary features, or in annoying notifications. Either way, paid or free, the user should be paying, or else you won't make any money.
Where does you library go when you change devices? Aren't tunes licensed to a particular device? Which would make it different from Kindle for instance, where your license is in the cloud, and content accessible from any authenticated device.
Similar to why pure declarative programming is less popular than imperative. It's far less efficient to maintain all that unchanging state, except in special cases where optimizations are applied. And it's often easier to describe what you want in a procedural way.
Do I just fail at reading, or do these benchmarks lack any context?

The question I want answered is how these chipsets compare with other offerings. The context I would like to see is the same tests run on low/mid/high-end AMD and nVidia parts using both the open-source and proprietary drivers.
Really? At least in the circles I run in (bay area startups) Apple is perceived as the company everyone blatantly copies.
Except when you want to change behavior in the future, e.g. adding a check to the getter or doing more than simply setting a value in the setter.

If you started out with getters/setters in the first place, you can do this without changing the API and ABI.
Nice, I also like this one:
"You begin running as fast as you can, and then gradually increase your speed." (sounds better in Hebrew, taken from the cult movie "Operation Grandma")
For me, it was because of bad mobile webkit support.
StringBuilders are verbose, but they do make a measurable difference in your code.

The problem with no using them is that then you need to be sure your code is never called by something else that runs it in a loop.

A fair while ago (JDK 1.5 had just been released, so I was still looking at StringBuffer) I did some analysis on the bytecode generated by concatenation.

There is a pretty significant difference:

http://nicklothian.com/blog/2005/06/09/on-java-string-concat...
Great point Natsu. I agree and have edited my post accordingly.
Do you think this style would extend nicely to a larger 2d game? I've been trying to think more functionally when making games, but it seems like games are really just one great big ball of state.

I've seen a bunch of examples of cellular automata and, for some reason, Asteroids - but nothing "bigger". Does anyone know any nicely-written larger projects (I'd love to see a platform game) around?
Well, as the story points out, there's no great data, but DistroWatch's numbers are as close as we've got to a constant check on what distros are getting attention and which ones aren't.
I guess this is true for many activities, not all. If my to do list app has bugs, the worst that could happen is some users will get annoyed and leave. If my medical equipment software has bugs, people might seriously get injured or even die. In the first case, just start and get it done makes a lot of sense. In the second case it doesn't.

Nice article and nice advice though.
I still don't see a reason for manual linebreaks here, which would mostly be useful for things like poems etc, where you explicitely need to mandate a certain structure. For everything else paragraphs seem a better solution, especially compared to pervasive use for <br /><br /> to simulate post-paragraph spacing.
The cost of privacy in javascript
AMD engineering another Opteron-like leap
Fair question. If you are an engineer or a startup person, its possible that you don't have insight into the dynamics of corporate BigCos. There is a lot of potential for under-the-radar turf wars. This creates potential conflicts of interest (http://en.wikipedia.org/wiki/Principal%E2%80%93agent_problem). This is not every case, but this is a real problem. This leads to the ultimate circle-jerk scenario. "What's in it for the party that puts the cash on the table?" The answer is often the same - hiding failure. Where the agents collude to enrich themselves at the expense of their professional/fiduciary duties. Of course, "in reality" there is enough plausible deniability to let things run their course. There's no real business, so no one will know they overpaid (for 2-4years) The M&A bankers earn their fees, The M&A exec at Big-Co gets his promotion, etc. No harm no-foul, its "on the house". Heck, the VC and the CEO get to put "Exit" on their resume. But yeah. Not really.

Non-Acquihire datapoints:

BBC NEWS | Business | News Corp in $580m internet buy

News Corporation Sells MySpace for $35 Million -

Microsoft Wraps Up $6B aQuantive Buy

Microsoft Writing Down $6.2 Billion Over AQuantive Deal

In the "Aquihire" case, the prices are just lower. This may be hiding failure of the Purchaser to lead, innovate, or hire efficiently (HR/culture failure) or to execute on a product launch (internal team failure). Sometimes, its "better" to just patch over that with a "bolt-on", and pretend to protect the career of a "B" player at BigCo. Again, in an Aquihire there is no actual business (ie, measureable profits) so the valuation is just a game of wave a finger in the air. Because of the delayed/opaque consequnces (ie, the 2-4 year period before anyone figures it out), its more subject to manipulation than any normal (ie, cash-flow positive) transaction.

So, to summarize. Not every acquihire is bad/evil. Sometimes, its a good, fair deal for all. But, by its very nature, the acquihire "process" is opaque and subject to manipulation. Furhtermore, its riddled with potential conflicts of interest. For these reasons, one must not be Naive when thinking about these matters.
if that public API is intended to expose data at the field level

> That doesn't make a lot of sense. An API is an interface, which in this case exposes data. The fact that this data is held by objects at the field level as nothing to do with the purpose of the API: it's an implementation concern. The consumers of this API do not, and should not, need to know whether a field or anything else is used to provide the requested data. If the public API gets bloated when using getters/setters then blame Java, not this basic encapsulation principle.

is a getter just a simple data value, or is it doing a bunch of complicated shit behind the scenes?

> As you said, and as a rule of thumb, never do a bunch of complicated shit inside a getter: always expose a method for this operation. Just because getters exist does not mean methods should disappear.
Let's see, the previous post is based on published psychological research, and this post points out a failing of humans that is, dare I say it, obvious to anyone that has critically observed any person, ever.

He isn't exactly making controversial points here, but rather trying to raise the awareness of such ideas.

He also isn't trying to sell you a pop-intellectual book.
While he was fired from Pay pal, the other two claims are factually false.
>> Lucy Koh specifically warned them about this before the jury began to deliberate

To me, this is absolutely the most interesting part of the case. I'm wondering who refused to blink in this game of chicken.

I've seen some reports that Apple approached Samsung with some highball settlement terms as a starting point for negotiations, but I'm wondering if Samsung's execs just decided to dig in their heels because of pride.

I'm making a big assumption here, but in Chinese culture, "face" --http://en.wikipedia.org/wiki/Face_(sociological_concept) -- is a big deal, especially the higher up you go in the food chain. I've seen relatives do stupid things just to "save face" or "give face". Not being Korean, I don't know whether "face" is a big deal, but I know their culture operates on similar ideas.
Good tip, though we all know half of the web is built using that throw-away-soon / it's-just-an-mvp code. there is nothing as permanent as temporary code.
agreed. I hate when people have anything less than 14pt font now. Luckily I have a readability for chrome installed.
You can use Bluetooth keyboards with iOS.
There was a typo indeed, thanks for pointing it out. Could you link me to that tweet?
I agree.
There is also a bit more to the Sammelweis story than simply doctors refusing to be self-critical.

From the wikipedia article on Sammelweis (http://en.wikipedia.org/wiki/Ignaz_Semmelweis):

"It has been contended that Semmelweis could have had an even greater impact if he had managed to communicate his findings more effectively and avoid antagonising the medical establishment, even given the opposition from entrenched viewpoints."
Is the Future Functional? - Rob Harrop
Trabzonspor 0 – 0 Videoton Özetin Video Linki Dahil … ) | Hayat ve İnsan
I've always told people that many of the best conversations with folks have started out with "Chuck I think you are wrong and here's why ..." This is especially useful when you are "important" (like someone's boss) because getting honest feedback when you are the boss can be nearly impossible at times.

Steve Bourne (yes that Bourne) told me once that you should try to cultivate people who could give you a different view on the world, That is helpful stuff but you do have to also get people to be honest. That is hard to do if they think you're 'hot headed' or likely to shoot the messenger.
Except that a lot of reflection-based Java code relies on the Javabean property pattern (getters & setters) by default.

You can often customize this (it is Java after all!) but sometimes it's better to just go with the expected standard in the language.
Very interesting, I did not know that.
You're confusing revenue with profits. There is certainly one revenue stream current media could be exploiting but are ignoring. If they could turn profit from it, after subtracting their costs, is another question. But they're not even trying.

You cannot make sure it would be much less money. What we can be sure is that A) megaupload and others are/were making tons of money that old media wish they were doing instead. And that B) the old media's current business model is decaying, flawed and doomed from existence. They would switch because or else they'll disappear.
Yep. The problem with modern shoes is that they give people the bad habit of hitting the ground with their heel, the shoe compensating the shock with some kind of absorption.

The "secret" is simple is to simply run using the ball of the foot (the fleshy part at the end). You run on the tip and use the heels as a natural shock absorber and preserve your knees. This will have the added benefit of strengthening the heels as well.

With that in mind, running barefoot is pretty safe (and you can do it outdoors with Vibram-like shoes).

I do that kind of running regularly as part of the warmup routine at my Taekwondo dojang.
"a misguided government/agribusiness lead food pyramid that is way out of balance with our pre-civilization diets"

Pre-civilization diets were not the ideal to reach either.
Tuto : Installer Windows 8 sans numéro de série.
While overall, I like this article, there is real danger in advice like this:

>Look up, not down. [...] to do that you need to look at the people who are even better than you.

While this is great for those who exaggerate their skills, I doubt those would even read this piece. For people with self-esteem problems and a tendency towards depression, however, this is about the worst advice you can give, because they tend to look at the top 1% already and therefore experience their life as a complete failure.

>But people will feel more comfortable telling you the truth if you start by criticizing yourself, showing them that it’s OK.

In theory this is fine, but if you start seriously criticizing yourself in front of others, you anchor this critique in the minds of your listeners.
You're probably looking at extended validation vs a standard SSL cert.

In this case, it's literally whether or not the bar will be green with your name in it.

Standard Example: https://limitless-atoll-7423.herokuapp.com/

EV Example: https://simple.com
The rules are different on each provider of digital media, but as I recall iTunes in particular allows you to authorize up to five devices to playback media, and you can deauthorize devices you no longer own.
Minority Report came out in 2002. It contains pinch-to-zoom. It is obvious.

http://www.youtube.com/watch?v=NwVBzx0LMNQ

Edit: Another commenter linked to this 2002 video, which is a better example: http://www.youtube.com/watch?v=waSXkJBKT1s&t=2m19s
Was that because the author had no comprehension of complexity and couldn't understand what was wrong with the design, or because of a lazy oversight that was fixable once the problem was brought to light?
Even more common is the code that was never written.
So will we be able to have sex without the entire 3D full-sensory experience recording immediately being uploaded to 2050 Youtube?
U.S. Navy Photos of the Day Update
How OfflineIMAP works
Curious, how do you know your friend is wrong? Was your friend factually wrong (a Holocaust denier) or did you just not like their writing?

With that said, I've critiqued writing I've not liked, but I rarely say, "I didn't like this", but rather I point out everything I think needs improvement, with at least one specific example to back up my point. As giving vapid criticism is easy, and producing works is typically much harder, I attemtp to put some effort into my feedback.

And always be aware that there's a good chance that what you might view as an improvement may not be. I'm no more offended that one doesn't incorporate a given piece of my feedback than I'd expect them to be in getting the feedback.
With a meta tag the data could even be hosted by a third-party service if the site owner prefers that.
Off topic, but that star plot was impossible to read. Straight up parallel coordinates would have been an improvement (maybe), but I can't help feeling like, with only 25 data points, a summary table would have been even better. I love visualizations as much as the next guy, but only when they are aids to understanding, not, you know, detriments to it.
Steve Losh is doing a series about making a roguelike in clojure actually- http://stevelosh.com/blog/2012/07/caves-of-clojure-01/ You might find those useful.
Ok, sorry, I'm not a native speaker and such nuances might very easily escape me.
Actually, tax incidence in Italy is even worse than that:

https://twitter.com/MicheleCaivano/status/240087376465125377...
Judging by the bump in AAPL today, I think you sold too soon.
I had heard about the universal search part, but I tend to think that at some point in the near future you'll see Google and Apple work out a cross-licensing agreement similar to the one between Apple and Microsoft, which means that feature will be coming back.

--edit--

According to: http://www.theverge.com/2012/8/25/3268609/how-google-has-avo...

Apparently the universal search is back in 4.1 in a non-infringing way.

>> Google significantly revamped search in Android 4.1 (Jelly Bean) by introducing their new search product, Google Now. The persistent search bar stayed, but it now pulled up Google Now with its fancy prediction and useful cards. It now intelligently pulls in weather, driving directions, sports scores, and more without the user even asking. They also tweaked the way it searched both the web and the device, side-stepping Apple's patent. In addition, they countered Apple's Siri by offering a similar (but often faster) voice search and actions within Google Now.
pbreit - Point taken on using only GET. I have edited the article accordingly.
So... this looks exactly like what GraphMuse does:
http://graphmuse.com/
The big question I almost never see addressed: Why would true REST be worth pursuing anyway? What's so good about it over other ways of setting up APIs?

If I recall correctly, Fielding himself says that it may be detrimental to an individual organization in the short term, but if we all do it, it will eventually help make our APIs collectively interoparable.
I would say that nowadays there was no reason not to use UTF-8, but then I found out that Notepad still saves using ANSI as the format encoding. Damn you, Microsoft!