skysight-inc/HackerNews huggingface dataset:
>those lawyers would write "As you know VMWARE was damaged to the tune of several billion dollars because they didn't use the GPL correctly, and we know that you aren't using GPL correctly either..."

If the GPL is litigated to the point of a published decision, doesn't that give the legal team of the targeted company the ability to say "actually, we know we ARE using it correctly, so buzz off"?

According to the lwn link 'JoshTriplett provided upthread, corporate general counsels often contact the Conservancy to request GPL enforcement: "Their interest, instead, is in a demonstration that the GPL has teeth so that they can be taken seriously when they tell management that the company must comply with the license terms of the code it ships. "
The inevitable Road Kill link.

http://youtu.be/U81_0waqEWA
A-Z List of Software Product Epiphanies Everyone Has Every Other Second
I think my stubborn and and somewhat anti-authoritarian streak helped me avoid most of this damage. I was the kid who always questioned the arbitrary restrictions placed on problems, the ones designed to drive you down a certain subset of paths.

I still have trouble with trying to "conform" or find "the right way" to do something, though.
To answer the 2nd part of the question:

vmnix was the name of the Linux kernel module that was loaded during the Service Console's boot process.

The terms "Service Console", "Console OS (COS)" were at times used interchangeably and referred to the Redhat distro you logged into at the terminal.

VSphere 4.0 had 2 versions: ESX (with COS) and ESXi (without COS). In 5.0 the COS was removed entirely.
Iot companies to watch for in 2015
"That raises the question of what is the smallest implementation of full chess?"

Technically, that is a program that prints "I concede". If you also want it to play black (IIRC, this 1k chess doesn't) and validate moves, it would have to know the 20 opening moves for white and concede on black's first move.

Of course, you could claim that isn't playing chess. But it is hard to define what, then, is chess. Picking a random move? Moving only one of one's knights, and conceding when it is taken? Does a program need an ELO rating of at least 1500 to be considered an implementation of 'full chess'?
Native is mostly about widgets and UI -- which is what matters to the user.

Else even Objective-C apps, with the Obj-C messaging system are not native, e.g. they delegate a lot to C-based APIs...
My Data Set Reference List
There's a rather ahistoric perspective at work here. I wonder if there's a generational thing.

ZX81 chess was so impressive because it was impossible (at least, I'd have bet real money on it). It was the thing programmers namechecked as the kind of thing you couldn't do on these newfangled cheap home computers. You need a 'real' computer to do it. There's just no way. I was writing programs for the ZX81, and the kind of simplicity they had to have is difficult to communicate to someone who grew up with 8086 PCs on their desks. Get an emulator and have a go.

So, you're right, it wasn't 100% total, complete, full chess. But, good god, it was chess, recognizably chess, playably chess! And the guy did it on a freakin' ZX81. It is difficult to explain how astounding that was.

Pointing out it's lack of castling and en-passant (and stalemate, repetition, etc) seems a bit churlish then.

That's why the challenge for the smallest chess program uses the ZX81 rules, not the full rules. It is why smaller programs make it to HN, whereas you don't know about the smallest program to play FIDE chess. It is a historical honoring of that great achievement.
I don't do any visual design work, but I'll convert designs to HTML/CSS, though. I specialize in backend development and prefer taking that work when I can. For that, I charge $175/hr.
First Contact: How to survive your first call with a potential client
Understanding Regular Expressions 2: Groups and Captures
I store all this sort of thing in a dokuwiki instance. There are also a ton of 'personal' wikis. Dump it in, organize/clean as you go along. Important thing is for whatever tool you use to be searchable.
The 90's called, they want their Java applets back.
but you do have to stay up to date with tech, and that is a battle that gets harder and harder as you age.

Wait what? That right there is blatant age-ism.

You know what helps learn new technology? When it's the same shit we did 15 years ago repackaged. WSDL is coming back around right now, just in JSON or Protobuf form. Don't you think mobile apps that have to sync with the server are a lot like server/client apps from the 90s?

To think that it's hard to pickup a new language just because you are 50 is really missing the forest for the trees of what it means to be a software engineer.
NodeUp Podcast: Io.js Update #1
Many vehicles separate the bus on which the OBD resides from the one that actually controls anything. Here's how Chrysler handles it (and by extension, most modern Jeeps): http://tucrrc.utulsa.edu/DodgeRam_files/NetworkTopology.jpg
You can talk about the form or the substance, I'd prefer you did the latter.
Okay, but how do I prevent spammers from signing up with randomly generated email addresses?
How about "Your software skills were great, but so-and-so's were better"? Of course, not knowing you and not working at Fog Creek, there's no way to know if that was the actual reason or not - but I would think it would be an acceptable reason.

Something I've realized since ending up on the hiring side of things is that there's a bit of a mismatch between how candidates and companies see the hiring process. As a candidate applying for jobs, I used to think I was applying to "the company" as an entity, and I was either good enough or I wasn't. The company, however, sees its candidates as applying for a specific position - like college admissions, there may be more qualified applicants than spots the budget allows for - especially at a place like Fog Creek.

(And, anecdotally, I am female and many years ago applied to Fog Creek for an internship. I didn't get it, but I enjoyed the interview process - it was one of the more interesting and challenging technical interviews I've done.)
"I want to expand my lemonade business"

"Great, how much lemonade have you sold?"

"We have 50,000 lemons on backorder!"
The amount was arbitrary. The point is that there is more to a greatest movie than resources spent
And so you address that and then you move on. Use that to shape the direction the interview takes you in rather than as a way to get irritated. Having eclipse as an anchorpoint helps because you can now show how you're different from something the interviewer already knows. That's much easier than talking in a vacuum.
I can't say I gave up gmail out of privacy concerns, but privacy concerns motivated me not to sign up for it in the first place.
Finally someone mentioning these! I've used Sendgrid, but I love Mailgun.
We also have plea bargaining, in various forms.
The pages used to display an active load-bar to reassure the user that something was happening. One expected slowness back then, especially on dial-up, and you could always hit [esc] once enough of the page loaded.

There was a time, especially on older, slower Windows, that people would stab and swipe feverishly at the icon on the screen, resulting in multiple instances of the app when it finally emerged from the Stygian depths of the HD, and many copies of the icon on the desktop, since swiping served to copy the icon.
The same can be said for Babel, and it is actually very simple to predict or retro-engineer the transpilation from ES6 to 5.
OK, thought you meant the interface{} thing people go for, since Go doesn't have generics.

This Sort.Interface thing is indeed safe and performant. On the other hand its not a solution to the problem we're discussing (that, to quote the parent, due to lack of generics "it is tedious to write library code in the language"). You still have to implement it all the time for all types despite having identical implementations.

So this doesn't show how it's not tedious. It just shows that it can be done in some way, which nobody doubted.
> Women would say things like "I worked on a team that did X," while men -- who obviously did the same kind of work -- would simply say "I did X."

Depending on what X is, and on context, it can be obvious that "worked on X" simply means that they worked on X, but that doesn't mean that others did not also work on it, with them. Especially if "X" is too big and complex for one person to do on ones own. In particular, researchers in CS (maybe coincidentally majority of men) tend to say that they "work on" or "are interested in" X, Y, Z - but that doesn't really mean that they don't collaborate or work with other people on those things. It's not exclusionary at all.

But this interpretation doesn't fit with the usual men-are-egotistical-narcissists-compared-to-women. So pay this comment no mind.
Our profile capture does not require applicants to include their demographic information, hence the only way we've been able to easily split by gender is by identifying their profile images and names.

Of course, outcomes have shown that racial diversity is also helped along. Our hypothesis is that if you work to remove bias through process there should be a measurable (even if it's small) change in diversity metrics.
I don't think you have to trust Google, you just have to trust the core team. While they all work for Google now, the language is open source and they have reputations that extend well beyond their time at Google. I share your distrust of Google, but I trust Ken Thompson, Rob Pike and the rest of the team enough that I don't worry about choosing Go. I have faith that if Google kills it or starts to misbehave, the team will leave and figure out a way to keep the language moving forward.
I get that, but you gotta think about how it comes across. A bunch of computer nerds treating a mental disorder like a math problem. It's seen as insensitive to dive into the problem like that, without a little acknowledgement of the human side of the equation. That's how it comes across to an outsider reading this.

But don't get me wrong, empathy won't always lead to better treatment. Science will. And we should ask these questions. Although you're comment "that's how problems like this get solved" is too optimistic. HN is not a forum for neurologists. I doubt a bunch of programmers on a comment section are going to to make a breakthrough in understanding this disease.
That sounds like a really pleasant experience actually. I think the dialogue here is most important aspect. Most of the interviews I have done the interviewer gives me the problem and sits there silently while I work on the solution.
Dell Hosting Hackathon at Burning Man
That sounds very plausible. Thanks for the insight.
Lease an Apple Watch
Internet Archive engineer here. We do maintain two copies of everything in our main data collection. Disks fail at an average rate of perhaps 5-6 per day, and the content does get restored from the other copy.

(That said, originally the Wayback crawl content was stored separately from paired storage, but it was merged into paired storage a few years ago.)

We would prefer greater redundancy, and may shift to a more sophisticated arrangement at some point, but as a non-profit with limited resources, we're constantly managing tradeoffs between what we should do and what we can afford to do.
Yay Postgre and thanks for running the numbers. However, it would be nice to see a summary of the major changes that made a impact on the performance on each version. I like geeking out on db internals.
Sendy is awesome and for non-technical people it is even easier and still has enormous cost savings to use a fully managed Sendy hosting provider. I use SendyHosting.com and it's worked great in my 2ish years of use with over 50k subscribers:

My referral link:
http://www.sendyhosting.com/?utm_source=tagsforlikes&utm_med...

link:
http://www.sendyhosting.com
https://en.wikipedia.org/wiki/SQRL
I am a newer developer, and this is how I feel. I didn't think it was normal. I always had problems grokking the docs as they are obtuse and thin. Also, things I find straight forward to implement in JS seem laborious in NG.

I am going to start learning react as well, and if you have any suggestions on how to get started, I would be appreciative of a few resources.
There have been a vast slew of articles on the problem of male unemployment, and particularly the problem of the unemployment rate in minority males, who got hit particularly hard by the recession and have not seen those jobs come back. Around the recession this was all over the news.

Higher education has also been tackling the issue of getting men into college, and keeping them there until graduation. As has primary and secondary education, asking questions like what it takes to get boys to read more, and the effects of having mostly female teachers.

That you have to ask where they are suggests to me that you haven't looked very hard.

And the assumption that you cannot tackle multiple issues at the same time, worrying about both diversity in tech and unemployment in men, is simply false.
That's a shady article and source.

If Google has offices in France, and they probably do, then Google must respect French laws. A country has sovereignty over its territory, which means that if you want to operate under it, you must respect its laws.

Don't know what happened with that lawsuit you mentioned, but if Google won, then it must have been because it was a stupid lawsuit.
Look at the list of contributors to the project (both in terms of numbers of committers and commits). Overwhelmingly Microsoft employees. Until it gains some serious momentum where it could successfully be forked and seriously maintained by the open source community at large, at this point it's a Microsoft product, and you have no choice but to trust their support and openness, so you can't hand wave away the trust issue as "Tarot card thinking".
Clearly it depends on your business and how you measure the value. I've worked for companies that spent over $5k/mo on Mailchimp and thought it quite worth it.
This has been posted in the past many times.
What's wrong with reimplementing basic things? Dependencies are points of fragility; I'm happy to pay a little extra redundancy in exchange for greater resilience.
New opensource Turtlebot tutorial aims to bring robotic dev to the masses
Yep. I shipped Tokaido and people use it. It was mentioned on Ruby Weekly last week.

You can get releases at https://github.com/tokaido/tokaidoapp/releases. Andres (who now maintains the project) released Tokaido for Ruby 2.1 (with support for Mavericks) recently and we're working on Ruby 2.2 support as we speak.

The org is here: https://github.com/tokaido/ and there are a number of auxiliary projects (muxr and tokaido-dns are the big ones) that I developed separately along the way.
Are you sure that's true? Doesn't Mailchimp have a per-per-credit alternative to their recurring monthly pricing?
Is TypeScript the new CoffeeScript?
Which is exactly why it isn't a good analogy. The amount wasn't arbitrary, it was the memory of the computer. There wasn't more to it being the 'greatest program' than the fact that it was created. There's no aesthetic judgement here. It is chess, with AI, in < 700 bytes.
Tangent, but... we're not there with music. We're pretty much there with the cost of copying/distributing music.

And we're partway there with the falling cost of production tools, and wider affordable/free availability of instructional materials.

But creating music -- particularly creating good music -- still takes a significant investment of time in the immediate act of creation and another order of magnitude of time in investing in skills.

And without an economic model to support that investment of time, we'll get less of it.
It's not like anything you build in React is going to transfer over to another framework either. In fact, I've been to a lot of React talks and people mostly ask "how do I do X" in react. The last talk I went to they spent 10 mins talking about how you might make a spinner when data is loading.

I think that's the nature of any framework.
"You have a problem with JavaScript. You rewrite your entire code base in TypeScript. Now you have two problems."
You mean like the people at MIRI? In a previous post, you suggest that most of them don't deserve any play at all on the topic.

No, like Joscha Bach, Yoshua Bengio, Ben Goertzel etc... the MIRI people are thinking about AI, not working on it. I should have made that point clearer and said as much. For AGI building = research, thinking =/= research. So for example, my Masters thesis is AGI implications of a nation state building it. This includes several rough roadmaps to AGI. I would not call myself anything close to an expert or researcher working on AGI because I am not building systems that are testing hypotheses about machine intelligence.

AGI does not yet exist.

Once it does, the field (in theory) doesn't really exist anymore really. So there can only be a research into it before it is complete. Arguably an AGI's (if you fall on the side of it being complete at "birth") recursive self improvement makes human input basically worthless.

The only consensus we will come to is when we all agree that the thing we built is actually an AGI. I can talk about those measures but at the end of the day most of the leading people think it's going to be "we'll know it when we see it."

Unlike atomic weapons prior to the first test shot (or even prior to Fermi's Chicago Pile-1 experiment), AGI does not yet have a solid theoretical underpinning, let alone a proof of concept.

Exactly. Which has been my point all along. Arguing about safety is totally a worthless effort, and harmful in my opinion, when we have no idea what the foundations are or the paths to it. When people are calling for regulation before we have anything like real funding for it it totally stifles the field. At best it diverts resources to making "provably safe" AI which is an endless rabbit hole in my opinion because it's an impossible metric.

there may not have been enough time for the aforementioned theoretical underpinnings to have been reasoned about to the level they were.

Enough time? That makes no sense. Lets instead call it an "Delta project" for AI - the entire front end of the project can be building the theoretical framework. There are no rules stating that a project has to be turnkey to realize a goal.
That's why slippery slopes are not always fallacies.
How the video of “Girl learns to dance in one year” was engineered to be viral
I don't personally find TypeScript a rejection of JavaScript in the way that some other transpiled languages are. It feels to me like optional typing plus a bunch of features JavaScript will get in ES6 or beyond.
I don't think it is as clear cut at all, but that makes it much more interesting. I left a comment there, but it bears some repeating I think

ESXi's kernel does not bootstrap itself from Linux at all.

There is no linux kernel as such [1]

ESXi does reuse linux kernel drivers ... a lot of them. But the way this happens is through a well-defined API provided by (proprietary) vmkernel called vmkapi. What you are seeing in the code above is the mapping between various Linux API's and these calls to the vmkernel.

I have no idea about the complaint. VMware's position is probably that anyone can go and write anything they want against the vmkernel's vmkapi interface. Indeed some vendors ship drivers written espeically for this API.

VMware have chosen to write a linux<->vmkapi interface, which then allows them to re-use many linux drivers. All of the linux<->vmkapi interface is released, along with the drivers and any modifications and this is considered sufficient. My guess is that the software conservatories position is that it is not.

Note exactly the other thing happens on the "other" side -- between user-land and the vmkernel. ESXi uses glibc ... but of course that interfaces to vmkernel via standard system calls. Maybe that's part of it too, I don't know.

So this may be a fight over API boundaries and where the GPL starts and stops. That's quite interesting...

[1] There was with the ESX product, which shipped a version of Red Hat. That hasn't been around for ages
No. Options can only be exercised if the owner(s) allow it. They can just as easily decide not to exercise them and revalue them at $0. This is generally considered unethical and would dramatically impact retention, but there is no explicit guarantee in options. It is implied and their value is entirely at the discretion of the owner(s).
When I used to hire people, I focused more on their intelligence, their focus, and their motivation. Any idiot can google snippets of code or memorize answers to questions. What I wanted was someone that could handle learning what they don't know, motivate themselves to get the job done, and most of all, get the job done.

And you can't figure those things out just by looking at a resume or by quizzing them for hours until they break. You have to actually talk with them. Engage them in conversation. Learn who they are and how they fit into this field. Learn about their past experiences and their future goals. Then the question as to whether or not to hire them is easy.

Resumes are a starting point. Previous knowledge is a time-saver. Problem-solving and motivation is where its at.

*As a side note, most of my interviews were 30 minutes or less. I only regretted one hire, and I got rid of him pretty quickly.
yes there is pay-as-you-go and alternatively you can suspend monthly billing.
Wonder if any student somewhere isn't trying to take up the challenge of adding castling to the code, using an emulator. I like to think that's something i would try to do as a student, because i'm pretty sure there's a tremendous amount of skill to gain by doing it.
Magnetic Resonator Piano
OK. When was the last time facebook emailed you to confirm that you liked a comment?
I'm guessing this is slightly tongue in cheek, but I'll bite anyway in the interests of decoding the hidden social rules :P

* considerate: walking in the middle, but fast

* considerate: walking on the side

* considerate: walking slowly or multiple people abreast, when there's enough room

* considerate: walking slowly or multiple people abreast, when there's no room, but paying attention behind you

Really, you (in the general sense here) have all these easy options to be nice, but you'll refuse even the most minor inconvenience?

Also, I'm not being inconsiderate for wanting to get somewhere - that's what most roads are /made for/. Roads made for leisurely strolling are made wide anyway. And it's not like I'm ramming through - I also do my best to avoid bothering the people I'm passing by. I'm taking the effort, so why shouldn't you? Inconsiderate would be me pushing through or telling you to make way when there's already room.

Sometimes a simple "scuse me", without even a frustrated tone, elicits the grumpiest responses so mostly I just walk slowly behind and don't even bother asking.

Anyway, this is longer than I even thought I would consider this issue!
My brain just broke. I can't even imagine Google and Microsoft working together on anything as big as Angular. The Universe just took a 90 degree turn.
mentioned article about fast string search:

http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.13....
Grep cheats
I so far worked as an at-will employee, but some of the positions I'm interviewing for are explicitly 6 month or 12 month contracts.