skysight-inc/HackerNews huggingface dataset:
It's not so deep. The takeaway is that modern terrorism will go through wires. Today, the logistics needed to generate massive power failure able to damage severely the economy of all developed countries are arguably simpler than what's necessary to re-create a 9-11.

I think we should fear and get ready, unit testing and agile software are not enough. We need to make sure some systems are NOT reachable in any way via internet, we need formal methods and expensive secure designs.

I really hope terrorists never get smart enough to attack digital infrastructures.
That's a bit of a help, thanks!
Yes it does. A law that some people continue to support is not a valid example of a law that is "outdated and unnecessary." Blue laws and dry laws, for example. You may disagree with them substantively, but they're not just cruft someone forgot to take out.
Yes. My religion teaches it (along with some other healthy things). It was actually reiterated very recently (https://www.lds.org/general-conference/2015/04/is-not-this-t...). The emphasis is much less on the health benefits but they are none-the-less talked about from time to time.

I think part of it that doing it a couple of times help reduce the extreme biological need. Also, when did you finish your fast? Dinner (5pm - 5pm) seems to be a good way to do it. Break it by drinking a lot of water to start.

Edit: I also find myself eating (snacking) less the next couple of days because I'm used to holding back.
There are two Node projects that I've been part of which illustrate some of these problems:

The first one is a hobby project of mine, admittedly a small app with no more than 300 users connected through websockets. Node was fantastic for this use case (and I replicated this model afterwards for a largish gambling site I contracted on): listening for connections, keeping them open, manage their relatively minimal state, and buffer relatively small streams. At no point in the app is there more than one stream per connection in the air. Backend requests are issued quickly and return quickly.

This works so well because the actual backend processing is a separate construct. Even though websocket connections can and do stay open for days, they don't drain a lot of resources (except for a small amount of memory for state and data buffers). No part of the service - except for the dead-simple broker core - will ever be in a contentious state or stranded midway through an action waiting on an unreliable communication partner.

Howeve, this isn't always feasible. My second example is a Node.js project I consulted on for a bigger company. The architecture was quite different: there were the same client-facing persistent connections to manage, but on top of that the backend logic was so immensely stateful and data-laden that a large chunk of it was actually implemented right in node. This meant, because streams and callbacks seem so misleadingly elegant sometimes, that situations occurred where lots of file streams, database connections, and all sorts of backend systems had to be kept in lock-step with the frontend-facing Node.js client connections.

It's no surprise this construct choked, a lot. Some of these are actual hard choices, for example where large and long-running data streams are concerned, but in the end we managed to make the entire thing stable by decoupling client-facing mechanisms from backend resources, and yes: by putting some blunt restrictions in place.

Like with any technology, you need to be aware of the tradeoffs.
Cart Life link is a dupe of the Spelunky link. This is the correct one: http://www.richardhofmeier.com/cartlife/editions.html (at the bottom of the page)
I'm not saying Schneier is right. More to illustrate his previous thoughts on this.
Debian switching back from libav to ffmpeg
The quote comes from 2010... Which was 5 years ago. PSHEW! (As my mind explodes.)
The best interviews have been interviews where I have been warned ahead of time what to expect. Ie in the phone screening interview I was given an informal hint that I should add unit tests to my programming task (the next step of the interview process). Or the time I was told that my in-person interview would include a hello-world with a certain IDE and a certain language (which I had no previous experience in). I felt comfortable because I knew what to expect and I could prepare ahead of time. I think it also showed I was listening and I was willing to learn new things.
Everything I've found so far says that opvault is still buggy.

I didn't think v5 was still in beta as I've been happily using 1Password 5.
You are not supposed to feed the fish everyday, they died because you've poison their water, especially if this was in a small tank without an integral water filtration system.

When you saturate the water with fish food (and also well fish poop) you pretty much give bacteria a free reign in the water which causes the water to be extremely anaerobic, so yep you've caused your fish to drown :)
I propose we call this the Brandon Eich Effect. Where if you hold an opinion or donate to a charity that the community of social justice warriors doesn't like, you can be removed and have your career ruined.

Most of these SJWs are left-wing so any right-wingers like Conservatives get targeted and driven out of the industry. You kind of wonder why liberals dominate tech, and then so see that anyone who doesn't hold liberal views gets driven out of the industry.

I kind of liked the tech industry before politics became a major factor.
I'm sure it's different for everyone, because I sometimes just don't feel like eating much for a couple days.

It makes sense to me, because some of our ancestors might have had only an itermittant supply of food, while others might have been accustomed to eating several times a day.
That's a pretty sad result to get from 128 cores. I've seen amateur Beowulf clusters get better results.
I had no intention of making the end result useful, but I run into interesting problems.

First, I wanted to make it as pure Rust as possible. I tried to avoid UNIX specific code, and since there is no library with Windows support for asynchronous IO in Rust, I was pushed into spawning thread and blocking waiting for client data. I quickly noticed that the benchmark was way below Redis (around 60% of ops/sec with 50 clients). But then someone point out to me[1] that I was running tests in a machine with two cores, and this actually may be better for machines with multiple cores[2]. I have yet to try it out and benchmark the results.

So far Rust API was disappointing for network operations. For example, `TcpStream.read()`[3] and `TcpListener.incoming()`[4] do not have a timeout. Maybe because its development is driven for Servo and not for servers.

I have thought about doubling down on multithreading and instead of a global database lock as rsedis is using now, having one per key (or some other arbitrary partition), and having concurrent operations, which is hard to do safely in C. But I have not gotten there yet.

[1] https://github.com/jonhoo/rucache/issues/2

[2] https://github.com/jonhoo/volley/

[3] http://doc.rust-lang.org/1.0.0-beta/std/net/struct.TcpStream...

[4] http://doc.rust-lang.org/1.0.0-beta/std/net/struct.TcpListen...
In theory, if you had an explicit query language, you could write the query planner in that language. You could then rely on the default query plan by calling functions invoking it, or make part or all of that plan explicit by invoking the lower-level functions directly.
Did you find that you got light-headed when you stood up too fast after 14 or so days? I fasted for 25 days (water) and found that I would get a little bit light-headed if I stood up from a seated position too fast. I also found that I would have these weird nightmares where i was eating a ton of food and would wake up thinking I had ruined my fast...very bizarre. I have never talked personally to anyone that had also fasted longer than a week, so I was interested if your experiences mirrored mine and if you found any way to reduce that light-headed seeing stars kind of feeling when you stood up. Other than that, I'd say I didn't notice many other issues except for maybe a quicker onset of fatigue if I was climbing a flight of stairs or something.
I went for a jog with an ex-colleague who was starting a new company in NYC. He had asked to meet up to get my advice on how to interview people for a research project that his company was working on. After 45 minutes of me explaining how a candidate would ideally approach the work, he offered me the job. I basically said yes on the spot.
> the proprietary bits on top are how we can make value.

Important nitpick: this is not how you make value. Being proprietary reduces the value you make.

No, this is how you extract value from your users. Maybe you have to (one's gotta eat). But I'm sick of the English language speaking of wealth appropriation as if it generated actual value.
Gluster library written in Rust
I'd be interested to see if the results end up looking something like DIPT which is the only known mainly audio hallucinogenics.
I think these are really cool looking, i especially like the man-dog on the dog-horse-thing
Whatever they are they're oddly poetic:

* The Endless Forms More Beautiful
* Pray for Toaster
* The Fall of Disorder
How to boost your site's performance
The Dark Web as You Know It Is a Myth
Keep in mind that the vast majority of "hardware codecs" are actually tiny embedded DSPs running software (well, firmware) that nobody generally gets to see.
JuJu library written in Rust
That's a fair criticism, and well taken, but keep in mind I'm learning the language as I go, and most of the commits are just rewriting things because they were suboptimal, not idiomatic, or hard to read. At this stage, I would consider adding comments wasteful.

I also have no intention of making this project live as long or have as many users as Redis does.
> Isn't that the same with _any_ ecosystem?

It is!
No lander?? :-(
How many secretaries are there? By this reasoning, if there's one secretary, that secretary is worth millions.
Keeping track of development hours
See his next post: http://www.frankmcsherry.org/graph/scalability/cost/2015/02/...

How big are the jobs being done? I remember reading a statistic[1] that is a couple of years old that 50% of the big data jobs were less than 10 GB. 90% was less than 100 GB and only something like 1% was bigger than a TB. You can fit multiple terabytes on a single machine. I wonder if anyone has new statistics about this.

[1]: http://www.msr-waypoint.com/pubs/204499/a20-appuswamy.pdf
Servasm: Literate webserver in assembler
and the Mathematical Recreations by Robert Kurosaka. Or Chaos Manor (Jerry Pournelle). But to the parent's point, I remember also wanting "world-dominance" even then ;)
Not that I know of. Gherkin is the simplest language I know of with any sort of rigor. Less than that, and you start falling on non-rigorous language that will have gaps of meaning, intent, and completeness.

What you came up with was pretty good. Good luck enforcing it with nontechnical stakeholders, though.
Unlikely. They haven't so far in the last 20 years they've been around. And the (painful) processing time required for "place & route" massively limits the degree to which their dynamic nature can be exploited.
If you are wondering about the origin of that custom, it's because Jewish weddings are consecrated with a ring, technically any item of value works, but a ring is the custom.

The bride who receives the item must be able to tell more or less what it's worth (so that there is no falsehood involved). If the ring is decorated, or if it's made of more than one metal, or if it has jewels on it, this is more difficult.

It's hard to tell just by looking what the quality of a Jewel is, but everyone knows that gold is worth something, and you can see how much gold there is. (So a hollow ring would also be a problem.)

As a result the guidance is that wedding rings are always plain gold bands.
Sorry- but you mean that you didn't eat anything at all for 23 days? And you felt energized?
Lesson: make sure you can always (re)run your code in a fully deterministic environment.
The Anti-To-Do List
GNUnet is a framework for secure decentralized peer-to-peer networking
This is a great way to spin not having a query planner as a feature, but I'm glad to have one every day that I write and compose semantic bits of SQL that can and should have different execution plans depending on the context in which they're evaluated.
The Human Genome Project wasn't exactly a marvel of government big science: https://en.wikipedia.org/?title=Craig_Venter#Human_Genome_Pr...

On the other hand, the Manhattan Project beats all of these aside from that obscure networking stuff, Apollo and the HGP were more taking existing working stuff and doing it on a more ambitious scale. I've been studying the Manhattan Project as of late, and it's for example amazing how much the plutonium path was pushed before they understood really important details about it, like fast neutron cross section, average number of neutrons from fast neutron fission (needs to be > 1), how to chemically isolate it after transmutation in a natural uranium reactor, and how to do that with that fantastically radioactive irradiated stuff.

Or the faith that they'd be able to develop a good enough membrane for the Oak Ridge gaseous diffusion plant (high pressure + fiercely corrosive UF6). Or how they got all this in motion before having good bomb designs, and how the Pu240 contamination of reactor brewed vs. cyclotron created plutonium required getting the most difficult bomb design to work ... and it worked the first time! Or how they set to making multiple reactors before they really knew they'd work, and if the size they'd chosen would work in the face of the neutron poisons it would likely generate.

And in such short time; study of the people and their methods of management (e.g. Groves and Oppenheimer) is very worthwhile for many HN readers.
What’s a barometer? And why is there one in my phone?
Imagine your world being constructed as such though
I'm talking about really big data, which requires hundreds of nodes just to store it and etc.
For myself. I think the best interview experiences I have had are when the interviewer is honest or when they provide constructive observations about my abilities.

For example, one of the best interviewers I have interviewed with would answer my questions about the company and their culture straight away without hesitation or himming-and-hawing about the response. It helped me feel like I could trust what he was saying. As well at the end of the interview he took the time to lay out his thoughts about me, my abilities and how I could contribute to the company. When I left the interview I had no doubts in my mind about what he was thinking and I was left sweating for days while waiting on a response about the position.

Since that interview has always left a lasting impression on me, I always try to do the same with anyone that I interview now.
Also GNU utils http://aadrake.com/command-line-tools-can-be-235x-faster-tha...
The above experiment (which has an interesting github repo) is somewhat over (and real world unusable), but still is eye opening. Hadoop and Spark bring so much complexity that looking for simpler solutions is something worth considering.
Yeah that's definitely true, I tried to allude to that with the ranges example, "Elvis" would be good for an index, whereas "Chris" or "Matt" you might as well do a full table scan.
No. Learn to trust the query planner. It's a good thing. When you want explicitness, take a look at the explain plan.
Like ship names in the Culture!
Not so much, no. I did attempt to paint a wall around day 16 I think and didn't feel comfortable looking up while standing on the ladder so decided to put it off until I ended the fast. Other than that I felt as normal as can be during the entire fast, although I couldn't get myself to stay up very late and so my evenings would end around 9pm.

I didn't have nightmares but I do remember that my dreams during the fast were incredibly vivid. I never imagined such dreams were possible and it's one of the things I miss most since ending the fast.
Hoverboard Night Flight [video]
That's funny, it looks like they are building an operating system.

And by that I mean theres nothing in there that gets you any closer to, you know, actual communication hardware.
The google seems to think so.

Though it instantly gives an idea for a sci-fi short story.
Tends to signal "I'm off hunting/shooting, it would be a really good idea to finish before I'm back...."

Particularly strong in Texas, at least until the law is judicially nullified as it's been in other states in the nation like Oklahoma, where you to can use lethal force to stop a theft, as in someone walking away holding your TV, after a verbal warning.
Incompetent buyers is the best description for it, but it's not all. There are few financial incentives/penalties in government, the only real risks are political. You'll not get in big trouble for securing funding for a project that ultimately doesn't succeed, but you will end up in big trouble if you run a successful and frugal project that steps on the toes of someone higher up.

And ultimately those political forces are what drive these projects. You do some work for a client in the army, and then Mr. Army gets on a bus with a guy in the air force. Mr. Army sings your praises to a big-shot from the Air Force and just like that you've got another $5M contract (to make Drupal websites).
The project might have simply been the result of the "revolving door:" military people ensuring big profits for defense contractors who pay them high salaries as "advisors" later. Most of these projects that appear to be failures are actually successes of theft from taxpayer. Article on this below with examples:

http://www.counterpunch.org/2014/02/11/the-best-government-m...

On the technology front, I was about to suggest they use Field Programmable RF to help solve this and then look what I find:

http://finance.yahoo.com/news/altera-lime-microsystems-demon...
Checks and balances have truly failed in nearly all aspects of government.
> Even these "cheap" missions are a half billion each, so it's a little more than nominal

over a decade or more, though :) I just wish we could have more.
The next logical step is an ad 'blocker' that simulates ordinary user behavior by still downloading the ads, in the background without displaying them, and added random walks by simulated 'clicks' on advertisement. This allows all the creepy tracking that comes with loading the spyware, but if done right has the potential of disrupting the already disgusting mind-manipulation while silently giving back to the content publishers.

Happy arms race.
h264 exists in hardware everywhere now. VP8/VP9, not really.

And VP8/VP9 has again the same patent issues as h264.
CSS layout properties apply to SVG. It is possible to manage the flow of the text (http://blog.scottlogic.com/2015/02/02/svg-layout-flexbox.htm...).
Maybe I'm an edge case, but I have never once had to deal with a whiteboarding session in a single interview I have been in. Though, this is obviously a small sample. I've worked at one startup, largely contracted otherwise, and am just now looking to join another.

Largely my experience has been 1/2 to full day pair programming sessions, building a sample application that does something reasonably nontrivial, or a combination of these two.

I really personally enjoy this practice. Even though a day of billed hours is a large opportunity cost, so is the expense of potentially hiring a bad fit for the team. It goes both ways.
A little bit. But in the end, I feel confident that most of those who might resent the attention given to Waterloo can still feel overall morally superior to the oppressors who won this battle. A lot of people don't care at all, but among those who care a bit, it's not comparable to, say, the 8th of May where most people more or less agree that the "good" won. Very few people in France will have the opinion that the good won at Waterloo.

I mean even when admitting Napoleon's numerous bad aspects, the Coalition was hardly more legitimate that the Empire, so from this point of view commemorating Waterloo feels more like pure military brag and less like celebrating something actually good, thus reinforcing the feeling of righteousness on the losing side.

It sure feels much less important than de Gaulle's Appeal of 18 June.
See now the R7RS which is split into a small and large standard (the latter still in progress). R6RS was largely ignored by the community, and there wasn't huge growth prior to it.
This problem extends to other event-driven environments as well. When you have a thread pool it's easy to know your limit (e.g. N threads can support N concurrent requests, and N is usually a known, reasonable number), but in an event-driven environment concurrency can feel limitless. For a typical event-driven HTTP server, the default limit may simply be the operating system's file descriptor limit.

You could limit fds, but to me this is crude (because you need fds for things other than incoming requests), and in some cases an fd limit isn't enough. In our case, we've built event-driven workers using ZeroMQ, where the number of peers is usually stable, but these peers may each issue a variable number of parallel requests over their ZeroMQ connections. To ensure we can still have backpressure in this situation, we have a setting to limit the number of active requests at once. The number to choose here feels a little arbitrary (as the limit is entirely enforced in-app, and it has nothing to do with hard OS limits like threads or fds), but just some number that we know the CPU can support in general.
The premium smartphone kickstand case for the Samsung Galaxy S6
> we were already diverse by design decades ago

I would suggest actually asking (not talking) with minorities in tech about how diverse/tolerant the tech industry appears to them. Part of being in a privileged group is blindness to the experiences of those outside the group, so without conversation, we live in an echo chamber.

Discrimination is rarely an intentional thing, but caused by our unexamined attitudes and beliefs. I don't consider myself racist at all, but my half-black fiance routinely points out blind spots I'd never noticed.

> I find it offensive that there are claims of sexism in OSS and tech.

This statement sort of assumes the claims are groundless. But until you ask outsiders for their experiences, how can you be sure? What basis do you use that you are so sure you're right?
NSA have been divided from the word go.

One the one hand they are to spy on the communications of "enemies", on the other they are to defend the nation against such spying.

Problem is that you basically can't do one without compromising the other.
Yup my daughter has recently started 'admitting' to being smart after we did an electronics kit and making minecraft mods, she also started hanging out with different friends who seem to appreciate intelligence more and are way less catty.
Many parallel algorithms become slower if you make them use too many cores, as they spend most of the time in communication, and very little in actual computations. Maybe the parallel systems would have been faster on a smaller number of cores than 128?