skysight-inc/HackerNews huggingface dataset:
One of the things with maintenance is that, although you do not want to use your them, you must make sure that your warheads work if you ever need them.

The traditional and easiest way of doing that is to frequently build new warheads, and test explode the older ones. That is expensive and, nowadays, forbidden/frowned upon (I think the test ban treaty hasn't been ratified)

So, one stops building new ones and ends up with thirty+ year old warheads. The radioactive materials inside them have aged, steel may have become brittle, etc. To ascertain whether these devices still work, tests are needed. You could do them on the devices themselves, but it is easier and cheaper to do an experiment with a few grams of radioactive materials than to work with a kg or so from a warhead (all IIRC; corrections welcome)
The MIT engineers
Nexus 4 factory images and binaries wiped out from Google servers
Meanwhile, for every object ever drawn in an anime, that anime MUST be mentioned in the article for the object. Because this is notable content, you see...

Wikipedia, 2030: "The Holocaust was also mentioned in episode #22 of Robot Cheerleader Girl, where Tanaka-san fell headfirst into a bucket while giving a speech about it."
I know, Minecraft rocks!
Sorry, I don't remember it. I quickly closed it. No harm was done.
Please, dear ${DEITY}, no.
That makes sense, here's another idea. At my day job the price of your product is perfect. Its an enterprise app that we want to support on all 3 mobile platforms, which we sell for $5k a pop (and another $200k * N in hardware). $600 is actually cheap (though so is my company, so we probably wouldn't pay more than $1k).

On the other hand, at home I couldn't afford more then $200. When I make an app at home, its for my own fun.

Instead of trying to satisfy both situations in one model, have you considered licensing per app? Every computer I develop on has an internet connection, so i'd be okay having to connect to your server to compile. I'd even be okay with having subsets of the framework licensed separately if it means I can get it cheaper at home.
it's not, it's an argument that wikipedia _as of now_ is not suitable for an indefinitely large number of pages.

I am not a wikipedia editor and am not defending strawman deletionists, I am only giving an opinion based on my daily findings of broken links, flags raised years ago and never updated, missing links between languages et cetera.
this would be awesome for group vacation planning via airbnb.com.
Thanks, removed. (https://github.com/jpf/wikigifs/commit/7568a938942b1ce37ac40...)
Because you are not the majority?
If you built all this in a Hackathon then I'm impressed - well done!
I agree with you, my point is merely if the deletionist types are so fast that it's actually a problem for new content (that the Wikimedia Foundation has made special notice of it), then they need to resolve it. Either ensure new pages receive a grace period, or come up with a clearly marked draft area. The grace period is my preferred solution, 8 minutes is not nearly enough to determine that a particular article should be a one paragraph blurb and not an honest to god entry.
In fact, you can provide citations which don't actually say what you are using them for (or say what you want while totally failing to substantiate it in any way) and it tends to work as long as the group of people who camp that particular article agree with your editorial slant on the matter.

I'm always chasing down citations on wikipedia and finding this to be the case.
There are plenty of things that you can leave out when writing parseable source code, but don't because it would make the code horribly un-readable.

That is, there's a reason for whitespace around operators, after commas, extraneous newlines, etc. It makes the code easier to read and maintain. Now while I'm willing to admit that this whole area is largely aesthetic and personal, if you submitted a line of code to me that was just this without the parentheses:

> 2 * 3 + 1

I would reject the code review in a heartbeat. Part of making your code readable to others and less error-prone during maintenance is adding extraneous stuff to it that isn't necessary for the code to parse/compile/interpret.
When I lived in the US I was puzzled to find, say, May magazine issues available in newsstands as early as mid April. Similarly, it seems not only acceptable, but indeed expected, for major companies to review the year before it's over.

Can Americans (or else) shed some light on this phenomenon?
...and these kinds of issues, which I've faced myself many times, are why I'm building Uptano. The "cloud" vs "dedicated" vs "co-located" are issues that were created by the artificial separation of a few good ideas.

There's no reason you shouldn't be able to have dedicated hardware performance, instant deployability, on-demand usage-based billing, at costs close to, or better than, co-locating it yourself. As I'm working to prove with Uptano (https://uptano.com)

I really think server hosting is going to look very different in a few years. We've not come very far in the past 5 years.
I'm a little disturbed that they are using this as evidence, yet one of the "forensic scientists" is quoted as saying

Normally this frequency, known as the mains frequency,
is about 50Hz," explains Dr Alan Cooper

That is incorrect. Normally it is exactly 50Hz. That's why the time displayed on battery-powered clocks drift over time, but clocks plugged into the wall stay correct.
It is claimed that it also happened to the OpenBSD crypto code: marc.info/?l=openbsd-tech&m=129236621626462&w=2 (a bit of analysis on the story: https://threatpost.com/en_us/blogs/experts-openbsd-backdoor-... ).

Long story short. The FBI put on its payroll a well paid crypto analyst trusted with commit access to the OpenBSD code. Years after that, somebody claims that the analyst has put on the FBI payroll to implant an hidden weakness in the crypto code. Audit follows; nothing found in the code. FUD still remains.
1) Great built-in library

2) great third party libraries,

3) decent documentation and tons of books and instructional material,

4) best-in-class virtual machine, good GC, as speedy as you get with managed code,

5) tons of profilers and development tools

6) several industry leading tools written in it (Hadoop, Lucene/Solr, Hbase, etc) and for it (IDEA, Eclipse),

7) Enterprise support from big companies (Sun, now Oracle) and IBM, and several smaller ones

8) Keeps improving (closures added in current 8 beta for example)

9) A large ecosystem of interoperating JVM languages, from Ruby/Python like (Groovy) to Haskell like (Scala), to Lisps (Clojure)

10) 15 year history, and at some point it fixed a lot of C++ pain points for enterprise programers
Yes, but the credential is supposedly tied to actual abilities that matter.

If they use their fraudulent credential to get a job and then perform well, then the material really was pointless and the system really is a big show without substance. I can hardly fault someone for gaming such a system.

On the other hand, if they fail miserably because they lack relevant skills, then they didn't really prosper from their cheating.
My point is more that if the community has an issue with the content, then take it someplace else. There are more wikis than Wikipedia. If you imagine that all knowledge in the world is a library, then Wikipedia is only the two or three shelves of big, heavy encyclopedias. If you don't think there's a wiki for your domain, then start one.
If coverage and quality is woefully inadequate, that means people haven't been doing much with them, so of course nobody is going around harassing these nonexistent people. Only pages that people are actually interested in get the jerk brigade's attention.
Don't know why people are saying you're an ass for calling out glaring design flaws in a $200 book about design. I felt similarly about Sacha's book on UI, but it was only $6-$12 so it didn't seem worth complaining about. If people want to drop two coffees on something they think they'll get value from, that isn't a big deal. Additionally, the app he designed for actually exists.

This is a little different from Nathan's offering because as far as I can tell, there is no end product, nor are the examples provided good indicators of good visual design or UX.
In addition to the other links in this thread, Fernando's PyCon.ca keynote's has a great introduction to the power of IPython and how it's revolutionizing the scientific (and soon the general developer) communities. https://www.youtube.com/watch?v=F4rFuIb1Ie4
I've always assumed this is the case, but I also wonder if it applies when clicking to unsubscribe.
I would note, I specifically sought that information. It blends into the background very easily. If it's really their suggested solution to a problem in their community, they need to make it more obvious or the default for new page creation.
No. He is tech support and must talk. He literally doesn't have an "indoor voice", so there is nothing he can do about it.
Looks nice, but as with MonoTouch the pricing kills it for me.

While I'm sure it pays for itself in overall value if you actually ship a product with it, attaching a price that high to a development tool causes (IMO) all sorts of secondary effects like balkanized user community, inability to realistically use it for writing open source software that anyone will collaborate on, etc.

If the product cost more like $99 it might be able to overcome the inertia a bit better. I know I'd be willing to buy it for that even if I wasn't sure I'd ship a product on it, but $399 is Real Money, so as hypothetically interested as I've been in MonoTouch, etc, I've never really looked at it beyond the press releases.
$1,000 seems pretty meager to me. If I can share well over 50% of my code across multiple platforms then that is code that I don't have to rewrite in another language. If that 50% takes more than 10 hours to reproduce (allocating my time at $100.00/hr) then it is well worth the expense. That doesn't even factor in the time saved in maintaining the application going forward.

Granted, if you are just building a small application that you don't plan to support multiple platforms then that price would seem steep.
Show HN: Easily copy your GitHub Downloads to Google Cloud Storage
Federico Pistono Shares Why It Is OK For Robots To Steal Your Job
It's not an excuse, as I have never flagged anything for deletion.

It's a purely external reasoning: wikipedia as I see it is already in a un-maintained state for many not notable articles, more articles without a change to how WP works will lead to more of those diminishing the overall quality of the project.

And no, I don't buy that not deleting articles will magically increase the number of contributors.
I thought that their removal from Ubuntu's default installation was simply that it's a large set of libraries that kept made it hard to keep the image under the size of a CD. And once Tomboy got ported to C++ (Gnote is almost exactly the same thing), it wasn't really necessary anymore.
You're defining the problem away (No True Scotsman fallacy). Instead of deleting articles that are not-notable (according to criteria X) you suggest deleting articles that are spam (according to criteria X). In both cases, you'll need some sort of mechanism for performing and reviewing deletions. Many of the articles in AfD are, in fact, spam.

So, the gain of deleting articles seems to be clear to you (you are in favor of deleting spam), it's only the criteria which lead to deletion that are up for debate.

Deletion of something may be worth re-examination/arbitration because both "sides" of the argument may try to game the system, particularly if a negative vote on AfD was eternally valid. Banning further discussion and modification also seems contrary to the wiki spirit.
Eric Schmidt says Google is the new Microsoft and it's winning
Maybe you should acquaint yourself with a book called "How to lie with statistics". In a biased environment, there are lots of ways to harm with innuendo (and similar) and then claim no such thing was intended while continuing to deepen the damage, often intentionally and maliciously, sometimes obliviously.

(But have an upvote. I am pretty sure your intent was to be supportive.)
Interview with Metafilter founder Matt Haughey
Where in the exploit HTML + JS is the ActiveX component being invoked from?
This is probably related to the YouTube video embed on the demo page, which I believe uses Flash. The mouse tracking itself is entirely JavaScript.

Edit: I am one of the authors of the demo code included in the disclosure.
I could recognize 80% of the companies in their portfolio. I guess that makes them pretty good at spotting good companies for investments. Comparing from the fact that generally when I see a VC firms' portfolio I could hardly recognize 50% of the companies. This could also mean they are taking less risks than usual.
Introducing Britely - idea saving app for Evernote dropouts
Anti-semitism or anti-zionism?
Julian Assange to form Wikileaks Party, run for Australian Senate
And then it says: "that company is prohibited from using our users’ personally identifiable information for any other purpose."

It turns out that sencha.com might not be sending personal information. clustrix.com appears to be, their privacy policy says:

"The Personal Information we collect is not shared, rented, or sold to any third-parties. We may provide your Personal Information to companies that provide services to help us with our business activities such as shipping your order or offering customer service. These companies are authorized to use your personal information only as necessary to provide these services to us." - http://www.clustrix.com/privacy-policy

I'm not a lawyer, but as a normal native English speaker I read that as they are not going to send my name, email, and phone number to another company, who will in turn share it with with anyone who pays them. But that's what they are doing. They are selling your personally identifiable information.
Sure, it's not a gorgeous next-gen startupesque web design, but I think it's more than visually appealing enough.
I post this all the time;

Having no cofounder is better than having a bad one, and starting a company solo is better than not starting one at all.

Don't get too hung up on the latest startup / incubator trends; plenty of companies have been started with one founder. Just go out and do it.
Almost all of the energy comes out as kinetic energy of the fusion byproducts, which are mainly atomic nuclei and neutrons. Sadly, a great deal of the energy of the easiest to achieve fusion reactions (D-D and D-T) tends to exist in the neutrons released by the reactions. And those neutrons tend to fly right out of the charged plasma quite readily. This makes creating a self-sustaining magnetically confined fusion reaction more difficult but it also makes building a fusion reactor slightly challenging. But far from impossible. Neutrons can penetrate fairly deeply through many materials but fortunately ordinary water serves as a robust shield. So by surrounding a fusion reaction with water you can quite easily capture most of the energy of the fusion reactions and can use an ordinary steam turbine generator to produce electricity.
"Simulating explosions helps determine maintenance for nuclear warheads?"

Yes. Radioactive material is, by definition, slowly becoming non-radioactive by decaying into other atoms. You can think of those other atoms as 'contaminants' in your plutonium soup.

What this means is if you create a nuclear warhead, and put it on the shelf, if you did nothing you would have a very sophisticated box holding some lead. But long before that it stops working as a nuclear warhead.

So what you do is you take put one on the shelf in the lab and you sample it periodically to see how its content has changed, and run your simulations to see if plutonium or uranium with those makeups would still work within the boundaries of the device, and you try to test it periodically under conditions that simulate, as much as possible, an actual explosion.

They used to do this at the test site, basically explode one warhead from a batch every 2 - 3 years to insure they still worked. But they stopped when we banned such testing.
I really like this technique. I've used it in a number of places, and it really does give great performance.

My usage has never been as clean looking as this though.

It's always been a bit surprising that Rails doesn't use the multi_get caching calls very much. These can be key to getting great results.
It depends on the type of fuel used. The holy grail is a boron + hydrogen reaction, which produces three helium nuclei.

Since the nuclei are positively charged and moving quickly, the net voltage is around 2 million volts. When done correctly, fusion will create electricity directly. At that point it's just a matter of stepping it down to a usable voltage, but we have lots of ways to do that.
That's definitely something worth chasing down. I haven't found it in the articles I edit, but I guess I tend to avoid editing articles where people have axes to grind (Israel-Palestine, U.S. politics, climate-change, alternative medicine, that kind of thing).

I do sometimes find misreferences, but in the areas I edit (archaeology, geography, engineering, history) they're most often misreads or misinterpretations by someone who was reading either too carelessly or without enough background.
Yes, and fair point.
I have an iPad, Kindle3, iPad3 and an iPhone (really thinking about the Nexus 7 or iPad mini).

The Kindle and iPhone are the only devices that I use in bed. The problem with the iPad is that I have kids and it needs armor - increasing the weight significantly. I really don't care if my $130 Kindle gets dropped/thrown (it has, and it creaks now).

Hardcover books have a much better weight distribution than any tablet/ereader, and yes, I prefer paperbacks for bedtime reading over hardbacks.
I knew someone was going to point out my confirmation-bias...thanks!
I like what I've read, but with a couple of cavaets. Ruby is the way it is on purpose. Discouraging people from using features of the language because the OP (presumably) does not understand how to use them: that's an anti-pattern.

The and and or keywords are banned. It's just not worth it. Always use && and || instead.

If you find "and" and "or" not to be "worth it", it tells me that you don't understand the difference. The "&&" and "||" versions bind more tightly, and that is not always desirable. Perl has the same set of constructs, and the Perl monks have been using them correctly for years.

As you can see all the classes in a class hierarchy actually share one class variable.

Well, yeah. That's meant to be a feature of the language, not "nasty behavior". It's good advice to use class instance variables, sure. But let's not imply that Ruby is a badly designed language; it's quite well-designed. This isn't Javascript. :-)

edit: formatting
By saying "australasia" I'd also include Japan (130mn), South Korea (50mn) and India (1.3bn) -- not China, which is notoriously insular on most levels. They sum up to a sizeable contingent that doesn't seem to be represented in HN posts (note: i'm not saying they should, this is not about political correctness).

I noticed the occasional post about Indian matters, but it looks like the other Asian communities are just not interested in HN at the moment.
Very well written piece that reminded just what the article intended. It amazed me that the Occupy 'movement' has already faded into the echoes of our society; that is my take and reality since I was not there nor directly involved. Once again, this was an excellent retelling and I for one appreciate it.
Don't forget hybrid solutions. I've done things in the past with:

a) co-location for the main DB servers (allows you to be very specific about hardware choices: RAID cards and SSDs not just preferred manufacturer but also the exact model) and backup machines (needed higher density HDDs than could be supplied by hosting providers choice of dedicated servers)

b) some unmanaged dedicated servers for the core servers that don't rely upon specific hardware requirements (HTTP servers, memcached, varnish). Also easier to slowly ramp up the number of these month on month.

c) virtual boxes spun up when required to handle spikes in the load and then canned when it goes quieter again

Even better if your hosting provider provides all 3 and can arrange a private VPN between the sets of hosts so you don't get billed for your 'internal' bandwidth.
This should be entertaining, if nothing else.

Nolan seems to bring a complement of actors between projects (e.g. Inception vs. Batman trilogy). Will be interesting to see if he continues this trend.
Does this use "native" OS X components?
Why is Apple increasing its capital spending?
What editors are interested in and what's important isn't necessarily the same, though. I try to focus my efforts on areas with the lowest ratio of editors to value of the content. I find that provides a much better effort-to-results ratio than trying to throw in my $0.02 on Israel-Palestine with 100 other people. It also leads to more pleasant colleagues, because when I'm writing about ancient Greek archaeological sites or mathematical theorems, my co-editors are typically other idealistic people who genuinely want to improve the Wikipedia articles on those subjects. If you're writing on something political, then a lot of your co-editors are going to be people with political agendas.

On contentious areas where a lot of people are interested and strongly disagree, I'm not really sure how to do it better. Wikipedia is often suboptimal, but so is the opposite, "expert-based" model. I'm an academic, and if you get bunch of us in a room, from different strongly opposed viewpoints, and ask us to try to come up with a consensus survey article, that experience is usually going to end up being painful. I think I'd actually rather wade into a Wikipedia edit war than serve on those kinds of document-writing committees.
This seems to be a popular style in javascript (particularly when using jQuery), but it's not actually valid ruby (edit: ruby 1.8.7, that is - see reply). The first line forms a valid statement, so the dots would need to be at the end of each line to indicate a line continuation. So it would need to be:

names.select { |name| name.start_with?("S") }.
map { |name| name.upcase }.
sort.
join(', ')

Which is slightly more annoying in that you need to modify two lines to add a new chained line (the line you are adding and the dot added to the previous line).

This also creates a mild headache when refactoring, as any change to the length of the "names" variable would force you to re-align the entire chain. You could do something like:

names.
select { |name| name.start_with?("S") }.
map { |name| name.upcase }.
sort.
join(', ')
Relatively none of the AWS/Heroku-type startups of the type most publicized on HN is spending money hiring those skills.
I find the postfix if and unless far more readable than the Perlish and and or operators. The "or die" construction for asserts is really amusing though.
The practice of tipping or not and how much is in a large part cultural, of course. I was just answering your question regarding the case of taxis specifically, since (in NYC, at least) I think the circumstances of "taxi economics" put most drivers at a disadvantage, and I try to acknowledge that by tipping.

I don't know if in Europe taxi drivers are better paid or have more autonomy, but I wouldn't be surprised. This article has a lot more detail on the issues with the medallion system: http://www.slate.com/articles/business/moneybox/2012/06/taxi...
What's needed here is a front end that can read C++ source and translate it into Shakespeare, and also a backend that can output Javascript.
both...
Digitalstrom: hackable home automation.
That email account is locked temporarily -- seems like everyone was trying to get in :)