skysight-inc/HackerNews huggingface dataset:
Want to Listen to Spy Broadcasts? Here’s How
What I meant was I don't understand how I could set up an efficient rolling backup scheme using this tool. I included the link to Mike Rubel's page because it demonstrates using hard links to share unchanged files between backups.
Show HN: A mostly complete 2014 "Tools of the Trade"
Hand dug water wells – cows, grain and snails
What stove doesn't use heat to cook?
A ToC of the 20-part linker essay (2008)
If that's always made clear then it's probably fine. I haven't played around in Swift enough to know it to be true.

I'm used to the memory-free semantics where equality equivalates a mathematical variable with a value. Assignment doesn't have a place here and it works very well with immutable values. Only mutability needs the notion of assignment so that you have boxes to subject to mutation.
I think he mean't offshore waves
It's helpful to also consider conspiracies using Julian Assange's framework which may have been influenced by Moore.

http://estaticos.elmundo.es/documentos/2010/12/01/conspiraci...

Without secrecy there is no conspiracy.
I'm a bit disappointed it solves one problem in isolation (heat transfer from gas to pan) and not much else.

Having said that, I wonder how it would combine with pot skirts and fireless cookers?

http://www.lowtechmagazine.com/2014/07/cooking-pot-insulatio...
Oh, there's tons of much better methods that would be more than good enough. Adobe even provides specific redaction features that drill down within the PDF data itself to make sure that nothing gets drawn under a redaction block, it works quite well.

But the government is about making procedures that are both easily understood by low-paid civil servants and unlikely to be screwed up in major fashion (e.g. our GS-7 scanning documents back in might use the wrong file name or reverse the pages or something, but they probably won't leak classified data if they do that).
Agree. Note that the quoted text is from the docs that were released with beta3 and is a big (and welcome) change from the original docs.
> According to the Swift language guide Strings, Arrays, and Dictionaries are all copied on assignment to a variable.

This might've been a recent change in docs. Quoting part of the same section from my copy of the Swift book downloaded a while ago (emphasis mine):

‘The assignment and copy behavior for Swift’s Array type is more complex than for its Dictionary type…

‘If you assign an Array instance to a constant or variable, or pass an Array instance as an argument to a function or method call, the contents of the array are not copied at the point that the assignment or call takes place. Instead, both arrays share the same sequence of element values. When you modify an element value through one array, the result is observable through the other.

‘For arrays, copying only takes place when you perform an action that has the potential to modify the length of the array.’

As an aside, it would be nice if Apple offered some kind of change log or a “what's changed” page for Swift docs (though to my knowledge they had made no promises regarding spec stability yet).
Yes it seems incongruous to assume that factory workers were likely to be rural, or even that any reader of TFA would be likely to make that mistaken assumption. I'd hazard that few enough American factory workers would have had much contact with mangoes in 1968, so GP comment is doubly bizarre.
Ask HN: Looking for Excel-based side project ideas
I studied math and computer science in college and went on to work in finance for a couple of soulless years. The best thing that came out of my time in finance is 1) the sober realization that Excel is pervasive 2) I became pretty good at it.

So, my question is, what are some applications/add-ins do you wish Excel had? I am open to any ideas.
It's still comparatively slow and safe, however. Even though we make some really weird alterations that way to suit our needs (which is well and good in and of itself, why shouldn't we?), the time spans are usually waaay longer than what i refer to as "frankensteining". It's not like you have a wolf, then a chihuahua, and in step 3, all wolves are suddenly chihuahuas. But that is effectively what we can do when we use more artificial methods.
That's a hypothetical ("if the regulation limiting the number of cabs had not been in place") made real exactly by Uber/Lyft. Let me put it this way:

Hypothesis: Too few cabs mean more DUIs

Experiment: Add more "cabs"

Expected Result: More cabs will lead to fewer DUIs

Uber/Lyft is the Experiment. The argument about other Experiments is irrelevant. Sure, less regulation could mean more cabs. But that wasn't the Experiment.

That counter argument is logically equivalent to saying "Drones, Blimps, Automated Cars all could have been cabs. There's nothing special about Uber/Lyft". There the difference is between a hypothetical and an actual result.

I'd also add that Uber offers far more than just "More cabs". It offers more safety, convenience, and trust. The driver is known, the car arrives when you are ready, and you don't have to haggle about not using cash.
Mantel instead of mantle is one that jumped out at me.
EDIT:

> “Nadella is a repeat befuddler. His first email to employees, sent just after he assumed the CEO mantel on earlier this year, was filled with bombastic and false platitudes:”

mantel: a beam, stone, or arch serving as a lintel to support the masonry above a fireplace

mantle: a figurative cloak symbolizing preeminence or authority <accepted the mantle of leadership>
Haha, that's surprising. Maybe the better presentation makes the examples look more plentiful.
The article states that the pan is cast aluminium.
then said author would need to brush up on their own writing skills.
Regarding c++, const foo * is the same type as foo const * .

For consistency, one should postfix the const to the thing you want to be immutable, so foo const * is a pointer to an immutable foo, foo * const is an immutable pointer to a mutable foo, and foo const * const is an immutable pointer to an immutable foo. It works pretty well, as far as I can see.
We can't literally live in Star Trek's universe because, so far as we know, the laws of physics don't allow FTL travel. But, there are numerous elements of Star Trek's society that are worth trying to achieve, even if we don't have to go about achieving them the same way the writers envisioned.

As others have mentioned, it's just fiction. It's not a roadmap to a destination; it's encouragement to build that destination ourselves.
To be fair, it's more complicated than that. Try to get from SF to anywhere in the East Bay at or after 2am on public transportation and you might wonder why BART stops running at 1am.
Great point. I wonder if a hot handle is at all avoidable when using a more efficient pan.
Electricity is usually generated by turning heat into motion, which is then turned into electricity. You lose energy at each stage, but the heat to motion stage is limited by Carnot's Theorem, which puts an upper bound on the efficiency of heat engines. Efficiency varies based on implementation, but it almost never rises above 50%.

If you need heat, it's much more fuel efficient to just burn fuel and not bother turning it into electricity in an intermediate step.
The Minimalist Guide to Crafting a Great Elevator Speech
It may handle some of the subtly of assignment and references but there is a lack of understanding of Swift. If it is a general debate about the meaning of assignment it isn't just about arrays but structs and dictionaries too.

If you want to opt in to a shareable mutable array it is easy to implement it by wrapping it in an object (class based) and passing that around.
I called a cab in SF in the middle of the day (Luxor, I think). They said it would be about 15 minutes. 20 minutes later I see the cab pull in to the parking lot I was waiting in, get flagged by someone else, and drive off with them. I waited another 15 minutes in case that wasn't my cab that just drove off, but no cab came.

I welcome the death of the SF cab companies. Long Live Uber/Lyft/Sidecar.
hyper late bound lazy streamed os cached interpreter pattern
In fact, I'd argue that because Uber/Lyft are more trustworthy than traditional cabs, the result on DUIs is more robust. Using Uber is far safer for a drunk person than trying to hail a taxi, haggle with a driver, and hope you make it home.
It is hard to use clear terminology without getting very technical. The basic idea is that a gas power station has a limited efficiency, I think about 55% of the chemical energy in the gas becomes electrical energy. This is due to a mixture of engineering limitations and fundamental thermodynamic limits of a heat engine (http://en.wikipedia.org/wiki/Heat_engine#Efficiency).

So for gas hobs to beat induction hobs, if we assume 100% efficiency for an induction hob (electrical energy to heat energy in the food), the pan needs to get >55% of the chemical energy from the gas into the food.

I don't have any figures but it isn't infeasible that a gas hob could be more efficient.
As an addition to this, it may be possible to modify it in such a way that it always returns colours that meet WCAG2 AA/AAA contrast requirements
Ask HN: If you had to build a clone of Facebook, what tools would you use? Why?
If you had to build the current version of Facebook from scratch, which technologies you would use and why?

Let's assume you had to build an application of complexity comparable to the current version of Facebook and can take all the time you need.

What technologies would you use for each part of the application? Why these? Which languages would you build it in? Any existing libraries or would you write everything from scratch? Why?
wait... how does that even work?

Read the current file's source from the start of a block and eval() the text n times or something?

That's just cheating.
What thaumaturgy said. I guess my background as a systems administrator has made me somewhat particular about what people consider to be backups.
Thanks for clarification - I had overblown sense of Monsanto's size, guess the other players are just better at playing quietly!
I hope people know I was joking
Tips & Tricks for Sketch
Yes, I know how doctorate degrees work and what they mean. It was a joke (as indicated by a smiley) and as with every joke there's a grain of joke in it. Not all PhDs are created equal.
Do you really wanna know ?
Alcohol stoves are nice and light but (along with any stove without an off valve) are technically illegal in most national forests and have started forest fires. If you spill one it is almost a guaranteed forest fire as you have invisible flame everywhere.

Personally I'm a fan of isobutane models after years of fighting with white gas models.
Absolutely true. Nadella knows exactly what he's trying to say, but he has to fluff it up to avoid ambush.

But at his level, you're gonna get ambushed by someone no matter what you write.
I don't know where you're getting that information. Burning wood produces significantly more CO2 than coal or oil regardless of your air flow; not to mention CO, volatile organic compounds, and nitrogen oxides. If you've ever had the displeasure of being within a few miles of a forest fire, it's really rough on the lungs.

You can argue that by growing the tree specifically to burn and then being careful how you harvest it, the wood burning ends up being carbon neutral. That's obviously not the case here, and it doesn't scale in general.
I've applied the technique in a project once with a pretty nice effect. I think the key requirement for AOP is that your code really is very clean, and to never influence logic in your main code in any other way than stopping it.

I.E, if you insist on catching exceptions in your crosscuts, don't go trying to fix the exception by modifying state. Either kill the thread, or let the original logic deal with it.

Our project was a bit of a laboratory environment. It was a university course that meant to test our ability to apply Patterns of Software Development (i.e. GoF) by having us implement a board game called Bohnanza (basically a heavily simplified Magic: The Gathering).

Our approach was to fully focus on implementing the business logic in a correct and test-driven fashion. In the weeks we spent on implementing the business logic we never implemented any GUI.

Then when it was done instead of polluting the business logic with the traditional MVC architecture, we designed a GUI that was layered on top of the business logic through AOP.

The GUI was just observing through cross cuts the transitions of the games state machine, rendering the relevant game elements and making available the valid inputs. We were one of the few teams who managed to have both a correct game logic and a fully functioning GUI as well as a test suite with good coverage.
Edward Snowden will speak at HOPE X on Saturday
"If you need heat, it's much more fuel efficient to just burn fuel and not bother turning it into electricity in an intermediate step."

This isn't always true. Carnot's Theorem works in reverse as well, so you can use a heat pump (like an air con unit) so get more heat out of your electricity than just dumping it into a coil. This is actually practical and is being done today for heating houses, you can easily beat the other inefficiencies because the temperature difference that you are trying to create for your house is much smaller than the one between the gas furnace and the ambient temperature around the power station.

For heating a pan though I think this is unlikely to be practical any time soon.
Author here. After maintaining a blog built around a "real" CMS, and a "real" CMS that I built myself, I'll say that my existing blog is built atop Jekyll and Git, the same stack I chose for Grimoire. It's simply the most basic thing that could possibly work, and it doesn't demand that I run a JVM on my inexpensive DigitalOcean instance. For all that I enjoy using Clojure, a "real" Ring server with a "real" database backend simply doesn't add anything to this project beyond complicating it further. As such I don't expect that a database rewrite of Grimoire is on the cards for some time to come.

To "how you build such a site in Clojure" the answer is that the entire Clojure ecosystem shies away from monolithic web frameworks and prepackaged solutions ala rails. Instead, Clojure libraries tend to pick a single feature or some small set of fetures, cover them well, expose a simple API and make composition trivial rather than trying to solve all possible problems.

Dash integration... Dash only makese sense for languages for which the documentation isn't trivially introspected such as Java. Clojure has the clojure.repl library (http://grimoire.arrdem.com/1.6.0/clojure.repl/) which is designed to solve this problem by exposing Clojure documentation to users in their interactive development (REPL) sessions. As I explain at some length in the Grimoire announcement post (http://arrdem.com/2014/07/12/of_mages_and_grimoires/) Grimoire seeks to fill a fumdimentally different niche than Dash. Clojure already has docs, and those docs are already handy for users aware of clojure.repl. Grimoire seeks to solve the problem of documenting the various ins and outs of the standard library which do _not_ appear in the official Clojure docs and which are currently spread out across any number of other low PageRank score community sites.
Quite a few people throughout this thread seem to be under the assumption that the intention of this device is purely as a charger.

I think quite a few on this thread haven't camped or hiked enough to realize that cooking is an important part of those activities.
Rust traits only don't support higher order types because they are missing from the whole language, i.e. it's not a philosophical difference between traits and type classes.

Also, Haskell has existential types, which are exactly like Rust's trait objects.
High compression sterling engines also tend to be really heavy and bulky since the whole thing ends of needing to be encased in a compressed chamber. They are cool though.
I can assure you its not an advert, haven't even tried ajenti: I had just seen an article about the system and since I'm fed up with administrating server via console window AND wanting to try nginx.. well, it seemed reasonable to suggest fusion of two potential goodies!

may still be clumsy but.. well there we go.
Accurate World Cup predictions posted on Twitter the day before the match
Wouldn't a properly formed DMCA complaint in this case be one of the few times you could commit perjury with one?

There's no way they have any good faith belief they own the copyright to (or are authorized by its holder to act in their stead about) the material explicitly named.

I'm just going to assume that their lawyer is smart enough to not have filed a DMCA notice, as such, and just send a thuggish letter instead.
It doesn't actually expand to that any more. You can see what it does expand to by running rustc --pretty expanded with a recent compiler:

for pattern in iterator {
body
}

becomes

match &mut iterator {
i => loop {
match i.next() {
None => break ,
Some(mut _value) => { let pattern = _value; { body } }
}
}
}
Presumably this comes too late to warn anyone who would have been inconvenienced? Or are we supposed to worry that active free accounts are next?
The game wasn't actually rigged. This twitter account just posted lots of potential outcomes and deleted the inaccurate ones after the game.
Though I don't really understand it, I'm really enjoying this series so far. Whenever I read functional code from Haskell or Erlang (or some other pure language), I feel like my girlfriend feels when she peers over my shoulder at some python code and her eyes glaze over.

Haskell has been at the top of my `list of languages to learn the basics of` for too long. It's time to fix that. I'm doing a tutorial this week.
This article is a great example of NIH syndrome.

You can get the same improvement with "About $5 of materials and an hour of time." [1]

That's by Dale Andreatta, a mechanical engineer that's been tinkering with improved stoves for decades. But he's not the only one, there are plenty of pot tweaks that achieve comparable or better the the improvements cites in the article.

Like many commenters below bring up, there are other design constraints to cooking technology than raw throughput -- performance at low temperature, manufacturing complexity, ease of cleaning, evenness of heating, performance under varying ambient conditions (humidity, wind, temp).

I encountered many such rocket scientists (literally) while designing improved stoves over the last few years. The engineering of stoves only superficially resembles the engineering of jet engines: the quantities are all different (low flow rate, low pressures, lower temperatures) and, as a result, the overall drivers of performance are very different (for example, stove to pot efficiency is largely governed by excess air control, NOT surface area)

A good example is that I got many recommendations to add "swirlers" [2] to stoves to improve mixing and reduce output CO. This works great in a jet, but it's useless in a stove: there's not enough pressure generated by natural draft to make the device effective.

[1] pg. 14
http://www.vrac.iastate.edu/ethos/files/ethos2008/Sat%20AM%2...

[2]
https://www.google.com/search?q=swirlers+jet+engine&espv=2&t...
Any idea which sandbox utility to use?
Atomic weapons were not feasible for use until we destroyed the Imperial Navy and the expert aircraft pilots that made up their offensive and defensive air-service, from what I know, which admittedly is not expert-level.
I've got several accounts deleted as well. Let me say that they warned that those accounts were going to be closed with several emails, all sent with weeks of advance. I realize that your customers may have simply ignored all the communications, but in this particular case, Google just did a fair and comprehensible move (at least, makes sense to me). On the other side, Google accounts that were actually actively used, are still there.
For pretty much any pan that's not a saute, nearly every meal in every restaurant (at least all the ones I've worked in or been in the kitchen of) is cooked in aluminium. Go to your nearest restaurant supply store -- almost all of the saucepans and larger pots are spun Al.
Argh, yes, you're exactly right, and now I'm too late to edit my post. I hate it when I get that backwards; sorry about that.
> ...but would turn into a mess with the proposed "fix".

Can you explain why?
I'm not sure this is what he meant, but I think he refers to the temperature of the water. If you lower the pressure, it takes a lesser temperature to get the water to start boiling.

So if you go on a mountain and put a pot with water over a fire, it will start evaporating rapidly(boiling) at a lesser temperature than 100 degrees Celsius, so he needs a more efficient way to transfer more heat into the water to get it to 100 degrees Celsius(normal boiling temperature).
You are actually both mistaken. I'm quite sure he understands what a javascript library is. He is simply asking for a library with a similar API, with the qualification that the colors are not truly random, but contrast with each other in a significant manner. Don't be so hasty to conclude that someone is saying something stupid because you might not agree with the phrasing. Try and understand and add to the discussion if you're going to respond.
How to talk to a 36-year-old space probe with GNU Radio, a USRP and a big dish
Your comment about merging two schools of thought reminds me of two blog posts by the designer of Rust:

Part 1: http://graydon2.dreamwidth.org/3186.html (discussion: https://news.ycombinator.com/item?id=8026868)

Part 2: http://graydon2.dreamwidth.org/189377.html (discussion: https://news.ycombinator.com/item?id=8028255)
If you ask, "cui bono?", the decision on who to side with is pretty obvious, at least for the average consumer.

Amazon has for decades been one of the most pro-consumer companies out there. The publishers have been slapped in court for trying to collude to raise prices. In fact, the whole source of this dispute is that Hachette wants the option to charge more for its books on Amazon.

So on the one hand, we have a company that wants us to pay more for the same product. And on the other hand we have a company that, while large in the ecosystem, is by no means a monopoly (maybe it is a monopsony, but even that is someone questionable considering they only have a 65% share of the market), and wants to charge us less. You can always buy the publishers' books from a different store if Amazon won't sell them. Well, if it weren't for the DRM the publishers originally insisted on, you could.

Hrm. Well, I know where I stand on this.
The ISEE-3 Reboot Mission: a dream SDR application for Ettus Research's USRP
A Uniﬁed Theory of Garbage Collection [pdf]
They're already did. It was called Lisp Machines, but the market favoured the "cheapest" text UNiX systems instead.
Author here. Holy cow. Thanks for all the kind words guys! I'm primarily a back end dev interested in hardware, compilers and operating systems. As a long time HN reader I can't begin to express how amazing it is that a my first "real" web service which I started less than a week ago made the front page.

I hope that for those Clojure users among you Grimoire proves a useful resource and I welcome any feedback or other commentary you may have on the site and its usability. Stay tuned, there's plenty more in the works from me and I'm reading the feedback with interest.
Cynk Technology shares suspended after surging 23,000%
I compiled a few notes on some cloud backup solutions a while ago (2012), http://alicious.com/cloud-backup-solutions/. In the end I use duplicati (with cloud storage, was live drive but that doesn't work and it's actually a current todo to move-over to Google storage [backups are encrypted]) and crashplan with buddy storage.