skysight-inc/HackerNews huggingface dataset:
I see them in airports...
Yeah, you should never see anything like "IN ALIAS" in the output of dig, for example, and getaddrinfo(3) wouldn't know what to do with that sort of record. It's all internal to the authoritative NS.

...which is a bummer, because doing this adds a weird sort of black box step in the DNS resolution chain between client and server. It makes troubleshooting DNS problems not so much fun.
The problem comes about when someone wishes to rule out the idea that the SC can make faulty judgments by construction...

That's what it fucking means to be supreme! There is literally no higher authority unless you want to start shooting people! If you don't like a Supreme Court ruling you can only petition the court to reverse itself or amend the Constitution. By definition, the Supreme Court is the highest legal authority, ergo if they make a "mistaken" ruling (according to whom?) there is no higher legal authority to express that conclusion. So yes, by construction no power exists to override the court, only to amend the Constitution. Faulty judgments are part of the system, the rule of law is the system whereby you agree to operate within this system, even when rulings are made which you personally object to.
I could have sworn bitbucket was an SVN host to start with, then patched in mercurial support and then git support later.
It seems like Pepper have raised the minimum plan to 40 hours/month.

http://www.peppervirtualassistant.com/pricing.php
I wrote up a blog post today about the Oculus and its potential to grab a big bite out of Hollywood at https://medium.com/best-of-tech/1a3151f2bc55

Don't mistake it with the Digital 3D experience that came to home televisions and is absent this year at CES - it is a totally new ballgame.
"Your stupid minds! Stupid... stupid!"
If the price is high they want the user base.

I don't think big companies care too much about a product in itself. They care about the team (which created a good product) and/or a userbase.
With regards to 1, it seems like I'm stuck between a rock and a hard place. I originally made the package in accordance to the docs I read which stated that if you are exporting more than one type, use NewType(). Now that so many people are using the package, I'd hate to make changes that would break it unless necessary.

However, with that being said, 2 might solve that issue. I'll add an example this evening showing how to also create an email in one pass using an example similar to yours.

Thanks for the suggestions!
To the Moon

Buy this bundle for To the Moon, for poignant feelings.

Surgeon Simulator 2013, for ridiculous laughing.
Love front-end technologies? Balanced is looking for you
Calling on all JavaScript lovers who want to build cutting-edge software with extremely high visibility. Performance and code quality matter.

Requirements:

- Deep knowledge of modern JavaScript techniques and web development. You should have experience with at least one JS framework (e.g. Ember, Backbone, etc.)

- Writing TESTABLE JavaScript libraries with server-side development (e.g. Rails, Django)

- A passion for great design and usability

- Great communication skills and an ability to work well with others in our open community (https://balancedpayments.com/open)

Pluses:

- Experience working in rich client applications in JS or Obj-C

- Contributions to open-source, especially a JavaScript framework

- Lover of all technologies front-end. Think and dream in HTML/CSS.

This is a very public facing position. You will work with very talented members of the open source community as Balanced executes on its open company vision. Your code will have extremely high visibility -- you can see some of our interactions with our customers here: https://github.com/balanced/balanced-dashboard/issues/

Send us something to impress us at jobs+hn@balancedpayments.com

Looking forward to hearing from you!

P.S. While we're located in lovely San Francisco, remote applicants are encouraged. However, you must be eligible to work in the United States.
Kibana [1] if the image file name is accurate.

[1] http://www.elasticsearch.org/overview/kibana/
hg certainly has had branches since 2008 at least.

What do you mean by partial commit? I can guess but I would rather know. :-)
Tech Corporate Rankings on Conflict Mineral Use 2012 [pdf]
Nice passive aggressive comment. Should try enlightening the commenter instead of berating them.
Facebook Hit With Lawsuit: Could Mistrust Spell The End Of The Social Giant?
CakePHP 3.0.0 dev preview 1 released
"Only"? That word isn't in the original title. In fact, the article states:

> though the study’s findings fit other recent indicators pointing to the app’s strength

And

> “Snapchat is really on the rise right now,” she says. “It’s been on our radar for some time, but we were pretty impressed with the number.”
I've never used a unit test framework for C ever.

I usually write a test exerciser for the library/command and a "known good output" file then diff the output and the known good.

will take a look at this for certain.
But this isn't something that needs to be nice. Files moving between libraries should be rare in well designed libraries, and splitting a subtree out of git is easy enough for when the need does occur.

Keeping a giant repository on the other hand makes it very easy to do stupid things and end up with tightly coupled code. You don't want that to be the path of least resistance.
same here, the only way i finally got out of bad state was to click on the logo to go to /news
if i navigate to news.ycombinator.com i'm still seeing the "we're down" message in chrome.
Did you read what I wrote? Yes, there are use-cases where the request->response model breaks down for web applications. I'll even admit that the set of applications where this is the case is increasing. But my point is that these are the exception to the rule, they are against the grain of the HTTP protocol anyway.

The Node environment seems to have shifted from "use this for your one-off, high performance, I/O dominated real time service" to "hey, you know Javascript, build all your webapps in node, build your command line tools in node, build everything in node, since it's the lingua franca of the web." This latter trend sucks, and results in things that to me seem absolutely bonkers, like the Vows test framework.
That's not my point though, I'm talking about what you see when you visit for the first time.

If you visit the site for the first time, like I just have, you have no idea what it is. You are just looking at a large image with some additional photos in circles. Just a simple phrase, such as the first line from the Learn More page: "Capture [and view] the places you love in amazing resolution and full 3D.", and perhaps a "Try it, select a scene" on near the circles would make it much more obvious.

Or perhaps even better, when you visit for the time time give them a quick demo or walk through.
That fits with what the Sencha team reported for iOS 7 - big wins for static SVG but bigger losses for animation:

http://www.sencha.com/blog/the-html5-scorecard-the-good-the-...
This is one of the 'features' of Technology companies in general and Silicon Valley in particular.

When a company raises funding, either seed or a series A round with a venture firm, they become tied into a giant loose web of relationships which provides things like introductions, heads up on quality candidates, and general interest queries. This is further enhanced by the somewhat astonishing mobility of talent from company to company.

So when a company says "Hmm, we really need to get into X" they can tap that network to see who is out there doing that and how well they are doing it.

Sometimes an investor wants to 'close out' their investment and they will approach a friend on another board or a friend of a friend looking for "ideas", other times people just meet at a social event and decide they should work together. Large firms have a group that is nominally called something like 'Corporate Development' which is code for acquiring companies to fill gaps or needs.

During times of scarcity when folks are looking for talent, under capitalized companies are seen as a good place to 'pick up an entire team' of engineers.

The classic way to connect into this 'web' is to go through the process once, which is start a company (or join one), connect with the funding folks at company and social functions, and have an idea of what you're trying to achieve. An 'agenda' if you will.
You're underestimating NPM and the community of modules around it. Node is well-rounded, and it's capable of handling most programming tasks. I use it to write utility scripts, which it's pretty good at. When I make a service, Express is a nice DSL-like framework.

It gets lots of stuff done, so I'd say it's pretty well-clothed.
Agreed and the option is often displayed along other real DNS records names adding to the confusion if you're not familiar with DNS systems.
Good might me next laptop series... Hm.
Original HN thread topic ("How Airbnb Improved Response Time by 17% By Moving Objects From Memory To Disk") is misleading compared to actual article contents, but speaking to the topic subject rather than the article, I do find it pretty common for many developers to blanket assume that memory-based caching is always the way to go, because, well, memory is fast and disks are slow.

This sort of thinking ignores the fact that filesystems already have their own (often very well-tuned) caching systems and in some cases (eg. sendfile(2) in Linux) the kernel can do zero-copy writes from files to the network that (along with decent fs caching) will easily outperform app-level memory-caching. Of course, this only applies for data that will remain relatively static, but often your best option is to mostly get out of the way and let the OS do the heavy lifting unless you've measured actual loads and are sure your solution is better.
The Firefox trademark dispute is not the same thing. Red Hat was attempting to keep their product from the open-source homebrew market -- they wanted to charge money for their software, and did this as far as the license would allow. Red Hat was as hostile as legally permissible to anyone trying to circumvent this, like CentOS.

Mozilla simply claimed that the Firefox trademark cannot be applied to any codebase that Mozilla, the trademark owner, hadn't officially sanctioned. They began to actively prosecute those cases because some people were modifying the Firefox source to contain malicious code and calling it "Firefox", misappropriating Mozilla's trademark. Because Debian issues a version of Firefox that contains unofficial patches, they cannot legally call their distribution "Firefox", since Mozilla hasn't officially blessed that exact codebase.

tl;dr Red Hat was trying to make money from users, and Mozilla wasn't

Disclaimer: I personally fully support making money from users and reject freedom 2 as a true fundamental of "free-as-in-freedom software". I'm just explaining why some people in FOSS dislike Red Hat, as it pertains to the CentOS backstory, and why nobody cares about Mozilla's brief trademark dispute with Debian.
"Are you not entertained!?" - That is what drives it. People need more and more.
Depends on the school. Even in the same discipline (I'm also in the geosciences like jofer) some departments don't accept grad students as MS students except in certain circumstances, such as U. Michigan, my current employer. Most of the grad students here come in with a BS and consequently (and understandably) take a little more time and often flail a bit more at first, relative to PhD students who start with a MS. Some schools that only/mostly take PhD students on give you a MS when you've written your first paper or taken you PhD qualifying exams.

I did a MS before I did my PhD, at different schools and with reasonably different projects, and am glad I did. Where I did my PhD, it was difficult to be accepted into teh PhD program without an MS.

However, I wouldn't say that the MS or equivalent is necessary to reach a 'full time course' because the American BS is less specialized than an equivalent degree elsewhere in the world, based on what I've learned from the many non-Americans I've worked with.

edit to answer question better:

In the American system, there is a lot of unrelated coursework (which has some guidelines, it's not just a sum of credits), but there are also a fair amount of core/science courses. I just looked at my coursework list and counted 16 courses (including fieldtrips and independent studies but not labs) in geoscience, then there is the requisite math, physics, chemistry.

The American system still takes the idea of a well-rounded 'liberal arts' education seriously (feel free to be skeptical and call it welfare for poets and historians, although I don't entirely share this position). I think university in many countries is a shorter process, although their high schools may be much better...
Mercurial itself runs into issues way before git does, it's just that Facebook has essentially gutted a bunch of things out Mercurial in order to make the resulting thing fast (punting on things like computing status, downloading diffs, etc).
I guess it is not reasonable to expect KDE to stop 'being KDE', but I am a little disappointed to see that they don't really seem to have shifted their emphasis anymore in the "lightweight" direction.

I used to be a KDE user, up until about 4.2 (I even used 4.0), but after that I stopped and switched to a lightweight window manager. Most linux desktop users that I interact with often have done the same, more or less at the same time. There is probably some selection bias going on here or something, but from my perspective it seems like the linux desktop zeitgeist is moving towards barebones tiling window managers, rather than traditional desktop environments, perhaps as the dream of "Linux for the proverbial grandmother" is slowly abandoned (or perhaps as the idea of the native GUI application dies, in favor of browsers (which provide the same facilities regardless of your WM/DE) and terminals).
Then of course there are the classics such as Trainspotting.
Moved around after graduation? This helps you find & meet friends nearby
They're Rubyists, what did you expect?

(other than misogynistic and crude library names)
(shared memory -> require 'gangbang' or somesuch)
>While the camera was on, which was kind of intimidating

Felt the same way. There should be a homescreen of sorts when launching the app (e.g., an aggregation of all the questions you have asked. If none, then place a prompt to "ask a question" which takes you to the camera).
This problem has been solved for many years. Thermostats and HVAC equipment have what Ableson and Sussman describe as "conventional interfaces". That is why The HomeDepot does not carry model specific thermostats, and people installed Nest thermostats in the first place.

The complexity is solely introduced by Nest.

https://nest.com/thermostat/installation/#thermostat-diy-ins...
I've been hearing nothing but stories about i. people getting sick and ii. the rift "completely fooling" people's senses. I had the opportunity to try the dev kit out over the holidays and I was really excited, but after trying a whole bunch of games I was actually kind of disappointed. I understand that it's dev hardware, and it DOES have a ton of potential, but I didn't even have the slightest hint of motion sickness. Maybe that's just my brain. But I also didn't feel like my senses were being fooled. Yes, I could look around and things were 3d-ish, but I really didn't find it immersive. Anyhow, I could see a high res display making a big difference in that department.
Some people like it, but my basic complaint with it is that it introduces a new concept, the "patch", that is basically a crippled commit. When a patch is not a commit, you get rejected diff hunks when it fails to apply, and it can easily forget its history.

An MQ patch is basically a commit that doesn't know how to merge and doesn't keep backups. It's way too easy to make a mistake and lose work. I consider MQ one of hg's youthful mistakes before tools like histedit, rebase, and Evolve came to exist.
This looks awesome, kudos to Razer for attempting it.

One thing I wonder is, the perpetual problem for diy system builders is that eventually socket/connection technology is obsoleted and you have to upgrade your motherboard in order to upgrade the CPU, GPU, HDD, etc.

This essentially looks like a more accessible motherboard, but still subject to that problem where eventually you'll have to replace the core product in order to keep updating the peripherals.

In fact, I doubt a stable socket/connection technology will ever be arrived at, so it seems the only solution is to make those (and the motherboard) as interchangeable as all the other components, essentially an equal piece of the puzzle rather than the core of it all.

I wonder if it's even possible to engineer a computer where both the motherboard and the sockets/slots are abstracted away into components that are just as easily replaced/upgraded as the GPU, CPU, Disc player, HDDs, etc.
I can't see support for collapse anywhere. It is in bootstrap.js and ui-bootstrap. Handy for responsive navbars amongst other things.
Ask HN: In 10 years, what will be the role of the coder/developer?
In 10 years, what will be the role of the coder/developer?

What type of languages (functional, behavioral, beyond cryptic code, ?) do you think will be used mostly?
I haven't heard of ToffeeScript before, but this is pretty much how Erlang works. Whenever you make a blocking call, all of the async stuff happens under the hood, so that you just deal with sequential code.

Erlang's concurrency model deals with lots of lightweight processes. Rather than having callbacks it uses a message system. Whenever a process waits for a message it yields so other processes can be executed.

In your example there would be a process separate from the main[0] process that handles the database connection. When you request the update to the database, you are just sending a message to the database connection process. This will receive the message and handle the update when it can[1], and once complete, send you a message back with the result of the update. During the waiting period the VM will continue executing other processes. No callbacks needed :)

[0] Erlang concurrency is based upon the actor model. There isn't really a main process, but for the sake of explanation...

[1] The database connection process will actually block while making the update, so if you have 10,000 processes calling this, you will have a bottleneck. As such you should have a pool of database connection processes, rather than just one.
Certainly, see for example https://aws.amazon.com/ec2/reserved-instances/, search for "Scale with your Business". Similar discounts exist for most of their other services.
Yeah. When a good guy tortures, it shows he's how far he's willing to go to save the day. And when a good guy is tortured, it shows how tough he is when he resists (and he almost always resists).
Letting Off Steam | GamesIndustry International
Hah! Thanks for that, I've seen folks in that costume in Switzerland and always thought they were musicians :)
I'll just kick this out by saying that widely used languages seem to be normally a response to a problem (functional programming got a lot of traction because of parallel processing), so another adjacent question to these is: what will be the future use cases in tech? Wearable tech, quantum computing (as its consequences), -?-
> I find it really odd that some FOSS people regard Red Hat as some sort of evil

Why do you find it odd when it is succinctly explained in the comment to which you are replying?
Slow Change Interaction Design
You’re right, there are disadvantages to a single codebase and builds at trunk. You pick up regressions, and it is difficult for your team to develop on its own while holding everything else constant.

But I don’t think the speed of receiving fixes is the essence of, or even primarily the source of, all my headaches with versions. The problem with mixing and matching versions within an organization is the enormous complexity that it introduces. Perhaps your downstream coworkers are still using an old version of your project, so they don’t want you to refactor their use of your API. Or perhaps you forgot to update your required upstream dependency when using a new function from a library, and your coworker’s program crashed because they’re still using the old dependency. Or perhaps someone forgot to bump the major version number when changing API or behavior, causing a previously built downstream project that is linking against the new upstream project to crash.

Now, these problems are all solvable if you and your coworkers are very disciplined in updating your version numbers and your required dependency versions. But it means that you constantly have to be aware of what APIs you export and what versions of APIs you are calling. You constantly have to edit the project manifests to bump version numbers. You must think about whether your changes will be major or minor. You carefully read the Changelist before using the newest upstream projects. It is a mental burden.

Contrast this to a monolithic codebase and build system. There are no version numbers in the dependency manifests to other projects in the company. If you want to change an API, you are responsible for fixing all the downstream users (rather than the other way around). Making a new project adds little mental overhead. If there is no impedance mismatch between the different teams of your company, it can make life much easier.
I don't think anybody was confused about the numbers and their relations.

That being said, I think in a system where everybody has a basic income, it is probably less important to save money, versus what we do right now where you have to save up for job-hopping.
What's wrong with RPM?
FBI Bitcoin sell-off co-inciding with China deadline
Yovigo Sites just got WAY cheaper
What A Shampoo Bottle Can Teach You About Marketing
"Know your limits beforehand."

I know a lot of entrepreneurs want to just jump in and take on the world, but this advice is awesome. Don't be pessimistic, believe you can do great things, but there are definitely limits somewhere. Knowing them can help mitigate disastrous failure.
No France, The Problem is Not Newsweek
I am sure Mercurial has always had (named) in-repo branches, so you were using Mercurial in strange manner.
If you haven’t seen them already, have a look at HN’s monthly ”Who’s Hiring?” threads: https://news.ycombinator.com/user?id=whoishiring
Having spent most of my career thus far building cool things I can't really talk about in detail this hits home.
This is exactly why I bought mine, and it was totally worth it.
http://www.matthewratzloff.com/

That is pretty badass.