skysight-inc/HackerNews huggingface dataset:
I'd love to see page-internal isolation functionality: basically, a better Caja. Let me designate part of the page as untrusted by the rest of the page.

What if a web-specific StackOverflow-like site could (securely) display arbitrary examples? What if a social network status update could contain live code, but that code couldn't break out of the update?
Some interesting Facebook facts explained through infographics
Took me a while to figure out the title.. hyphens, people. They work!
I think the bigger issue isn't that arm customers don't want a desktop, It's that desktop customers don't want to be forced to use an ill fitting touch interface.
I'm not sure why you got voted down for that - perhaps because you just wrote things as if they were stupid slogans. Since what you write is true (well, except you neglect to mention the difference in maturity and interest rate between US$ and Treasuries), let me elaborate.

Both US$ paper bills and US Treasury Bonds are liabilities of the government (where I consider the Fed as part of the government for obvious reasons). I use liabilities in an accounting sense, but you really need the basics of accounting down solidly to understand the monetary system.

Another term for liabilities is debt. So when you have a 1$ bill, the government "owes" you something. Here's where things get a bit confusing, because what exactly does it mean that the government "owes" you 1$?

Well, they have to extinguish the liability in the agreed-upon way. Usually, you extinguish a liability by moving a corresponding asset that is on the same level or higher up in the pyramid of liabilities (see here: http://neweconomicperspectives.blogspot.com/2011/09/mmp-blog...). When I owe you something, I extinguish my liability to you by giving you paper money.

But the government is at the top of the pyramid, so their liabilities can only ever be transformed into either another form (exchanging cash for bonds or reserves or vice versa) or they can be extinguished when you pay taxes.

That takes some getting used to, but nobody said economics was always intuitive.
Reading the discussion comes off as you getting very personal in the attacks while most of the comments were centered around code/crytography.

I also am confused by you stating that 'resorting to best practices can be dangerous.' If they are the best practices, they should be the least dangerous one would think?

I've got no horse in this race but that's my opinion and confusion.
Great, but... Ive only does industrial design, as far as I know.

The other side of the coin is the software, and if that declines, Ive's going to be creating very well-designed paperweights. So who does Apple's software design?
Simple, honest-to-god, true drag-and-drop of files. To/from the desktop.

And don't make me download/install an addon, because odds are you just caused my support expense to blow up by 10x.
Why Occupy Wall Street will fail
Non-paywall link: http://www.reuters.com/article/2011/10/21/us-groupon-ipo-ifr...
Show HN: From zero knowledge to web award - this is my story
Why I comment:

When I'm learning a language I write comments for myself. Notes about syntax, idioms, gotchas, and whatever else.

When I'm fixing a problem I leave XXX markers around to easily keep track of what I'm doing.

When I'm writing maintenance code I reference the ticket number, describe the problem or feature, and why we implemented the fix or feature the way we did.

You should never see the first two types of comments in checked in code, but I bet that I've probably saved later maintenance programmers hours of frustration with that last type of comment.
Comments on Doe v. IMDB Privacy Lawsuit
Surely the minute DDG starts costing them revenue then Google, et al., will simply cut them off from using their search results (eg via !) and substantially reduce the utility of DDG?
Normally I don't upvote humor on HN, but that was great.
For Java, running jstack a few times can be much faster and easier than tying up to a profiler and often will show your bottleneck or problem right away.
Then don't run any Metro apps!

I can happily continue to run all of my existing apps without having to touch the Windows App Store, or any other locked down stuff.

The only downside is, apparently, the launch screen. If they don't see sense and allow a launch direct to the Desktop then I'll be annoyed.
In some ways because Ive was the head designer he had more power than anyone else regardless of Steve's extra effort. His work would impact every level of the company so immediately regardless of peoples personal opinion.
Before you remove the onions, make sure you understand why they were added in the first place.

Unfortunately, while this is correct, it is nowhere near strong enough.

Just because you know the initial hypothesis that drove someone to throw the onions in, doesn't mean you know what the onions are actually doing. The onions are interacting with all the other ingredients. Onions are more complicated than you think.

Before you remove the onions you must understand what they are actually doing in your recipe, not merely what you think they are doing... or you must be prepared to find out. Because even very tiny systems are generally too complicated for you to fully understand, you usually have to settle for science: You must have good enough test coverage to detect any breakage as soon as possible after the onions go out, so that you may frantically throw the onions back in and then go back to the drawing board.

And the longer the onions have been in the recipe, the longer the recipe has evolved in the presence of onions. Take the onions out and all the other changes that have happened since the onions went in might have to be tweaked. Oh, the subtle things you could find.

Here is what can happen: You'll take out the onions, and then five years later your customers will complain that your company's red paint has started peeling, ten years ahead of the fifteen-year warranty period. Oh, no. You call an all-hands meeting of your QA team. They spend months doing expensive research, while your product engineers fly from city to city trying to pacify the increasingly irate customers. Eventually the scientists find that the paint can be fixed by mixing in some kind of protein or other. But why did the paint used to work? Oops, the onions had protein in them! Sure enough, if you throw in some special Essence Of Onion Protein compound the problem goes away. Great. Now all you have to do is issue a field recall of about six years worth of your product.

You will bring this story to your CEO and the shareholders, and they will ask why you didn't just pay for some onions? Or, if removing the onions was critically important, why you didn't run a small set of onion-free test batches on a parallel process line and then put those batches through lots of tests, both in the lab and in the field, before making the change?

I've worked as a semiconductor engineer, specifically in charge of diagnosing problems that arose in the field, so believe me when I tell you that I've seen "simple", "well understood" little tweaks in a semiconductor processing recipe cost companies millions of dollars and one hell of a lot of stress. I've also lost six months of my grad student career to one specific bad step in a recipe. Once you get a working recipe you do not change a thing without a specific plan to thoroughly measure and document the effect of that change. Find someone from Intel and ask them how this works: I've heard that you can't so much as touch a knob in Intel's fabs without a signed change order.
The Real Point of Visualizations: Managing Data Overload Without Algorithms
Why More and More Designers are Switching to Fireworks
His point is that it puts together (complects.. ha!) lists, the data structure, and list-like operations into one and the same thing, when logically they are separate ideas. He's trying to point out that separating things brings simplicity, even if you end up with more of them, therefore unifying everything under one syntax for example is not necessarily "simpler". You may not agree, that's okay, but it's consistent with what he was saying, not a straw-man.
I found this pretty useful. It tells you how to fix the worst annoyances and how to get a decent desktop back.

http://www.webupd8.org/2011/10/things-to-tweak-after-install...
This is why when Comcast announced its bandwidth limit policy, I actually cheered rather than jeered. By solving the problem correctly, they eliminated their need to solve it incorrectly. I only sort of wish you could pay for more bandwidth, though that's an abstract concern as my worst month ever barely cracked 1/3 usage. (But I know others can have issues.)
Does your name really affect your personality?
I completely agree with your "don't roll your own crypto" argument. But there's a difference between using a hash and inventing your own cryptography.

What kind of use did you have in mind with "trivially breakable"? hash(salt+pass) ?

My point is just that _some_ (not all) things considered unsafe in crypto is still good enough for this kind of use.
I imagine he has some voice in the aesthetics of the software design. But it's true that the whole package (hardware and software) is the combination that makes apple products great.
Speaking of that photo, the documentary it's from (Objectified) is very good and is on Netflix Instant Queue. (Might be available other ways but that's how I watched it)
OpenClass not Google Product
Thanks very much!

Without the GIL what does that mean for extensions written in C. Would they need to be rewritten?
Read it; loved it. I highly recommend it as well.
"Unleash the Power of Ezines To Increase Sales"
I have a close friend who's 35 years old and has had mild RLS for ten years. She doesn't take medication of any kind.

It doesn't mean Merck doesn't have a drug that lowers the threshold, but it also doesn't mean that all cases are due to this Merck drug.

Anecdotally, RLS has been around for quite a long time, but again, I don't know the timeframe of the drug you refer to.
I'll just leave this here:
http://zachholman.com/posts/documentation/
Our company has its own internal analytics system and, while their approach could technically work to prevent spoofing, there's other, simpler ways. The first is simple deduplication of received events. This will carve out a large portion of invalid requests, particularly if you have thresholds of time for how frequently a received event is considered valid. The second is to calculate the quartiles and outliers. This allows you to remove all but the most sophisticated spoofing and is good practice to remove ill-behaved browsers and filter out things like malware detection tools that duplicate browser requests if they haven't seen the site before. There's many operations you can do to determine the validity of data received, however who knows how much of this is actually done by analytics providers. We've built our own internal analytics system (and expose it to customers) because existing solutions weren't robust enough for our needs. The biggest lesson has been that trying to get higher than about 98% accuracy on delivered events actually lowered the accuracy of events and using calculations on the backend was more reliable, but requires specific knowledge of the type of events.
This is a really awesome idea
WYSIWYG form element is an excellent idea. Never though about it before... not sure how it would be possible to implement though.
IMHO, the thing that bothered me about the whole exchange was that it could have been avoided with a little bit of common courtesy. Instead it turned into a "oh let's go roll that pull request".

I picked up pretty early on that antirez wanted to know the "why" first since one of his stated goals was keeping deps to a minimum. What could have been a nice productive discussion about crypto standards was fucked up by ego, asshattery and language barriers.

Oh and github pull requests are TOTALLY the appropriate place to have those kinds of discussions =/
I think you mean this as part of the investigation in what this code does.

That is, after setting up a test/dummy system, you remove the code, run your tests and try to break it. Perhaps sticking in breakpoints or print lines or whatever..

I doubt you really mean to experiment on the business-critical live system.

Thats unlikely to be very effective anyway. The most obscure code is often a bug fix for some really obscure bugs. Maybe it fixes some weird bug in Swedish XP SP1, or something which you don't find just by removing it and testing. Situation depending, you will need to actually read and understand the code and investigate properly.
Do I have this straight? Your response to someone complaining that they are being forced to upgrade would be that they should upgrade?
If you go anywhere in public you will hear people complaining about Rogers, it's more common than seeing a Tim Hortons.

Rightly so, Rogers is probably the most hate inducing company in Canada!
Ubuntu 12.04 LTS to get extra-long desktop support cycle
Definitely. The name sucks. It sucks just as much as other crazy names that make no sense... like GoDaddy - who would ever use a company like that? Sounds like an escort service. Or Yahoo. Or Google. Those names just don't make sense and should be changed ;)
منتديات حياتي
منتديات حياتي,منتدى,حياتي,صور,برامج,اشعار,خواطر,جوال,ايفون,قصص,العاب,الغاز,ايباد,نقاش,اسلامي,اسلاميات,هندسة,مدارس,بحوث,فوتوشوب,دروس فوتوشوب,مطبخ,عالم ادم,الصحة,قيمزر,كاس العالم,رياضه,الرياضة,يوتيوب,كمبيوتر,سياحة,سفر,اخبار,بغداد,سامراء,العراق,
> Why is it so important to your boss that the project be done in Perl?

It was an existing project developed by the client, and they used Perl. So the technology was fixed.

> And why is it so important to him that you do the project in Perl?

That wasn't important, I was just the guy with some free capacity.

> As you said, you don't even know Perl. Why isn't the project going to someone who does know it?

There was none who knew it (at least as far as I know), the company was a Java shop.
Or you notice nothing breaks so you leave it out, joyfully congratulating yourself that you reduced total LOC count by one. Then six month later things start breaking and you have no idea why.
Yes, but when you're trying to make an "end-user" product, you don't throw in huge changes a few weeks before release. Which is what they did with Pulse.
and by anywhere in public, I mean in Canada, or at least Southern Ontario.
A Letter from Goldman Sachs Concerning Occupy Wall Street
Two Entrepreneurs try living on $2 a day
Here's Evan Phoenix's answer from a while back:

http://news.ycombinator.com/item?id=2265163
> "It is better to have 100 functions operate on one data structure than to have 10 functions operate on 10 data structures."

Oddly enough though, you yourself are pointing out that it is better to have 1 function that operates on 10 data structures. ("length" operates on vectors, strings, hash tables, etc.) On the surface this seems opposed to the quote you chose.

However, it is clearer if you replace "data structure" with "interface". The is classic separation of concerns. When specifying the "what", we can get away with "100 functions operate on one interface", but the efficiency, the "how", can be specified independently based on the choice of data structure implementing that interface.
Ask and you shall receive:

http://codahale.com/how-to-safely-store-a-password/

(also explains _why_)
Another cool experiment with the graph example given there: http://worrydream.com/ExplorableExplanations/ — go down to the guitar icon (or find "incidentally" on the page).
Celulitis en las Piernas - Como Evitarla
It was a very 'sensible' decision if you are an MBA! If Sony had been a little more flexible and far sighted it could have worked. But as you say, it resulted in the DAT tape and minidisk being restricted to protect the studio.

It's the same sensible that means Apple shouldn't have started iTunes (we aren't a record company) and Amazon shouldn't have done Kindle (we aren't a computer company) !
The graph is neat...I worry that the link is a UI paradigm that my mom or dad simply wouldn't grok though...I'm not a particularly good son and I don't talk to them much...so does anyone wanna test my theory out?
Exactly. This is why Windows 8's future is still very uncertain. If it wants to compete in the tablet market, it will have to be on ARM, no ifs or buts about it. But the problem is Windows 8 is starting from scratch on ARM, not unlike WP7 in the smartphone market. So why would anyone still want a "Windows 8 tablet" over an iPad or even an Android tablet, which would still have many more apps that work on it than Windows 8 for ARM? There's not a very big compelling reason to want it.
And he has specified that you can drastically cut military spending and not affect national defense in any way. We are in 150+ countries currently and fighting several wars while we are basically broke.

It's time to make cuts in EVERYTHING
Likewise, some points in the talk brought to mind the OO SOLID principles. It's unfortunate that much of the discussion I saw on HN and twitter after this talk was argument about the value and purpose of testing. More useful would be examining the point of the talk and considering any common ground between Rich's "Simplicity Toolkit" and where things stand now with languages that aren't Clojure.

Take your language of choice. If you're not in a Lisp already, you can't do much about syntax vs. data, but what about the rest? Is it easy to work generically with data and values instead of making custom classes and mutable objects for every piece of data? Is it possible? Can we make it better? Are there persistent collections or managed refs available? Can we write them as libraries? Within the language's polymorphism construct, can we extend a type we don't control to our abstractions without creating adapters and more complexity around value and identity? What about transactions?
An Open Letter to Senator Durbin of Illinois
Live in the Quiet Paradise of Shadow Wood in Bonita Springs Florida
I heard that the second edition got some mixed reviews, which one do you have?
This is absolutely brilliant for educational uses. Even the front-page filter example is something I plan to suggest to my prof for the DSP class he teaches.
More probably that the detection of parcel packages is machine-driven and based on thickness.

I don't know why everyone is up in arms about this. The Indiana people had a problem (how to get the letter mailed via the service they wanted) and solved it creatively.

This is called a "hack", not "bureaucracy". And we should applaud it. Is the rule dumb? Yeah, probably. But it's hardly alone in the world. For every styrofoam cube there are a dozen people putting letters into boxes needlessly, and that is the bad thing. This is cute.
It ultimately depends on some greater fool to work, though. If we don't buy the stock, then either the equity owners of Groupon or the investment banks (or both) are left holding the bag.

I just hope that I don't indirectly end up involved in this through my 401(k) or something.
I think Unity is useless because these kind of inexperienced users almost don't exist anymore. Everybody got used to the "ugly" interface made of contextual menu and "hard" to adjust settings and those who didn't could live with sensible defaults that could always be overridden.

But with Unity it's like if they went out there to replace QWERTY keyboards with friendlier layouts without paying attention that none of the current users already got so used to the on-purpose-unfriendly layout you're actually slowing them down now.
Gov't testing car-to-car collision avoidance systems
Another classic story which illustrates your point: the "Magic/More Magic" switch.

http://catb.org/jargon/html/magic-story.html

Closer examination revealed that the switch had only one wire running to it! The other end of the wire did disappear into the maze of wires inside the computer, but it's a basic fact of electricity that a switch can't do anything unless there are two wires connected to it. This switch had a wire connected on one side and no wire on its other side.

It was clear that this switch was someone's idea of a silly joke. Convinced by our reasoning that the switch was inoperative, we flipped it. The computer instantly crashed.
Conversion rate is so much more than design:

Where are their website visitors coming from?

What is the messaging that got them there?

What are they trying to accomplish?

Does this product or service solve their problem?

Burying the sign-up button is an extremely simplistic hypothesis for a low conversion rate.
Exactly. The reason that OWS isn't making any specific demands is to remind everyone that those who keep asking 'what's the pitch' are part of the problem. Honestly if you can't identify the problems in this country on your own then you're not paying attention.
Two paragraphs of agreement with an old pg article. Why is this getting upvoted?
I suppose it depends on what you mean by compatibility. It will be interesting to see if current .NET apps will be able run on top of the ARM CLR or if Microsoft will actually strip out support for anything that's not Metro.
A quick overview of the Mexican Mafia
> The problem comes when we are so focused on proven stuff...

I sympathize with your overall point, but there's a really good reason why the focus should be on proven stuff: because it's been proven.

You are building an application which will be responsible for safeguarding some of its users' information. You should typically want to do that using a proven approach. If nothing else, it's a cover-your-ass situation: if it turns out that the proven approach has a flaw, you can at least say that you followed standard practices. If your invention has a flaw, you hold all the responsibility.

I hate to fall back to argument-by-analogy (but I have to, since I'm not a cryptographer), but you're somewhat in the situation of installing a fire suppression system for someone, and you're saying, "Well, I don't want to use halon for this, even though it's what all the experts say I should use, because I don't want to deal with the company selling the halon equipment. So let's just use lots and lots of kitchen fire extinguishers instead. They do the same job, and if I use lots of them, it will work just as well."

Maybe. Maybe it will. But, if it doesn't, you will be responsible for having made a decision that flies in the face of lots of advice from lots of very smart people, and the consequences of that decision will affect not just you but also anyone that uses your system.

edit: On the more technical side of things, maybe nobody has yet pointed you to Bruce Schneier's 2005 article on SHA1 weaknesses (http://www.schneier.com/blog/archives/2005/02/cryptanalysis_...). There are several very good points in there about the dangers of using broken cryptographic algorithms. By stretching a broken hash, you could be -- and probably are -- compounding its weaknesses. i.e., you might be making it easier to find a collision, not harder. And, that article was written almost 7 years ago; since then, newer low-cost hardware has been made available which can compute 33 billion MD5 hashes per second (http://blog.zorinaq.com/?e=42), and that was almost a year ago. I swear I read this year about some Russian kids doing a lot better than that, and that ignores things like EC2 which make it economical to do heavy-duty distributed hash breaking.
Forstall appears to have same tyrannical streak as Jobs.
location data is already freely gathered from pretty much every smartphone

https://secure.wikimedia.org/wikipedia/en/wiki/Skyhook_Wirel...
> So who does Apple's software design?

Scott Forstall is responsible for iOS. My understanding is that Eddy Cue is responsible for the iTunes Store, including the App Store, and now, iCloud. He was promoted to Executive Vice President back in August. I'm not sure who's in charge of Mac software.

You can see brief profiles of the various people here: http://www.apple.com/pr/bios/