skysight-inc/HackerNews huggingface dataset:
>Not completely. Proprietary modules and forks of both exist, so in the broadest sense they are not

This is also true of GCC. Lots of organisations have private forks and the GPL allows that. More generally, if somebody offers 'compiler as a service' over the internet then the GPL becomes irrelevant and they could add as much private code to GCC as they wanted. The GPL only forces you to contribute back under a very specific and narrow set of criteria. Criteria that the majority of software being written in 2014 doesn't meet. The GPL is largely irrelevant to most software shops these days - they freely incorporate piles of GPL licensed code into proprietary closed source products. They can do so because most new software is internal to organisations or delivered as an internet service. The GPL was designed for a different world.

Software freedom has been set back because of people clinging to the GPL as the final word in software freedom. Your kind of GPL centric propaganda results in young developers today thinking they are doing the world a favour by writing proprietary closed source web apps - because they are using FOSS GPL libraries, right? And targeting the 'open' web, right?

Do you AGPL licence all the code you write, including website backends? Does your employer? If not you should probably take a close look at yourself and consider that maybe you are part of the 'problem' you are decrying.
Yes, people say horrible things when they think they are in an environment that will tolerate saying those things. But I'm going to give the management of whatever hypothetical org of which we're speaking the benefit of the doubt and say they don't want to start that way. I hope that, for new organizations who have yet to establish their own culture, that tendency is a projection of expectations for the industry as a whole. My advice is for people who are serious about being fair and equitable in their dealings with diverse groups of people. If we don't have that baseline, I can't help them.

But with that baseline often comes a person who is specifically trying to be nice to others and not hurt other peoples feelings. This is, unfortunately, not going to keep bad actors from getting in and ruining the soup. Thus the need to be firm and resolute. One must establish early, often, and unequivocally that the org is not going to be party to exclusionary behavior.

It's easy to say, "you have to increase diversity", but that's a goal, not a plan. Being a part of the "majority", we're not going to be able to increase diversity by ourselves. That's rather much the whole point of the idea of "diversity", that the homogenous group can't solve all of the problems for all of the people of the world. That rather much includes our own damn problems and the problems of our own damn industry.

For example, take these "<TargetedDemographic>CanCode Campz" things. I'd like to see numbers about them. To me, they've always seemed very forced. I've also heard first-hand complaints from said people in the target demo that the concept is perceived as patronizing. I applaud the organizers for putting in the effort, and their heart is definitely in the right place, but I wonder if they aren't doing more harm than good.

It almost sounds like a chicken-or-egg paradox, that I'm suggesting you can't foster diversity without already having diversity, but that itself is a symptom of the problem. There are very dedicated people out there who are trying to work and trying to be accepted. I've seen first-hand how easy it is for one, single, isolated incident to drive away the very people who would help introduce our organization to a broader audience. We have to stop being blind to the people who are already here.

All that it takes is to not let the vocal, hopefully-minority-of-bad-actors drive good people away. All that it takes is the shocking, controversial policy of just treating "them" not like "them"s.
Great to come across such an even-handed review; thanks!

One quick note:

> Other than cherry picking studies to confirm an long-held position, the most common response I’ve heard to these sorts of studies is that the effect isn’t quantifiable by a controlled experiment. However, I’ve yet to hear a specific reason that doesn’t also apply to any other field that empirically measures human behavior.

In practice, I'm not actually aware of any good studies on 'tools productivity' in any other fields. (And it's not for lack of strong opinions -- grab a professional photographer sometime and ask them about Canon vs. Nikon.) I think it really is fundamentally difficult to measure things like this: getting the most out of a tool can take years, and ecosystem factors can outweigh even a large difference in 'inherent quality'.

If we care about using nice languages, it seems like the best thing we can do is try and lower the impact of these external factors. I think the situation here is actually pretty promising -- projects like LLVM take a lot of the heavy lifting out of implementing a performant compiler, and the JVM and CLR are becoming more and more hospitable to diverse language implementations. There will always be a cost to choosing an unpopular language -- but the smaller that cost is, the easier it will be for better technologies to win out in practice.
After last week, that answer for me is now going to have to be "code deploy"
Explicit delimiters compose inside expressions much more gracefully. This is the main reason Python doesn't allow multi-line lambdas: if you have some significant indentation inside another expression, it's hard to tell how the rest of the expression following the unindent should be formatted.

CoffeeScript does handle this, but I've always felt it was a murky corner of the grammar.
Is it completely out of the question to reflect light onto Philae using Rosetta (once they locate the probe of course)?
Can someone recommend a good web hosting site
So my friend got asked to find a good free web hosting site, he normally find good hoster, he found a good one for www.garagedoor-guys.com, but the owners of this new site he got don’t like anything he showed them so any recomendations ?
I do not understand this. Who/What are these recruiters and in which fields are they relevant?

I work in tech, and when I'm looking for work somewhere I don't have any contacts yet I'll just send them my cv directly. No need for a middle man or escrow service or things like that.

Edit: Perhaps my comments seems rude, sarcastic or condescending. That's not how I meant it.

I'm genuinely curious about how this all works, since I've never seen or been contacted by a recruiter. Nor have I heard such things from colleagues. I do not live the the states, perhaps this is not a common practice in Europe?
People, we can settle this with a line-counting tool. I just used http://gitstats.sourceforge.net/ and it appears I've been authoring over 1000 lines of code a week.

See for yourself at http://github.com/EGreg/Q

300k lines of code
over about 3-4 years
MongoDB was tested in a replicated setup, PG not, that's a pretty fundamental difference. Loosing acked writes in a master-slave replication with failover would be expected with a sufficiently large replication lag even for PG.

MongoDB is about the last database I'd pick for any given scenario, but I acknowledge that there are people that have a usecase where it might be a good fit because the tradeoffs work out for them.
I get a few emails from recruiters on linkedin and most of them are actually pretty nice... I realize most if not all of the emails are templated, but it's fine, usually if you respond, you get a human response back.

If I can help them (and help a friend or myself who is looking for a job), then I do, if not, I tell them I don't know anyone, being polite goes a long way, I think.

Recruiters are doing their jobs, in a pretty hostile environment (with posts like this), and just like any other job, there are those that will make the profession look bad, or aren't very good (yet).

[EDIT] - Is it possible that I'm somehow insulated from these really really bad recruiters somehow? I'm in Austin, TX (not SV), so maybe that's somehow it? Never had recruitment emails as ridiculous as what I have been reading
Hasn't the whole 10x myth been largely discredited, for some time now? How are we to take a company draws its business plan from it seriously?
That's because the modern web itself is a REST API, whereas most of the things that call themselves "REST APIs" aren't.
Facebook Is Said to Test Workplace-Collaboration Tools
Complex Single Molecules Successfully Manipulated on Atomic Scale, Manually
To flip the thought: If the license forbids you from building a competitive advantage, why contribute at all?

There have been issues with GCC for over a decade that go unfixed and unchanged because it doesn't make the most business sense to contribute to it. In the category of interoperation in particular, the GCC project proved to be openly hostile to the notion; they left a wide gap in the market for Clang/LLVM to fill.
The business model for flat-fee development will make sense about the same time as clients start writing unambiguous and fixed scope requirements.
When you're working with the JSON data type you need to create a number of indexes to get acceptable performance.

Typically one per natural key in the document set ( present in and unique to each document ) for queries that are using that key and then trigram indexes on fields where you're doing partial string matches.

If you're going to be doing random queries against the entire contents of the document you'll probably want to add a full text index.

Like so https://gist.github.com/laprice/90ea359c4f4dcd99e9f2
Recruiter: "Dave the Cxx is a great guy and will really like you."

..fast forward to the interview..

Recruiter: "Dave, it's nice to meet you."

It turns out Dave did like me, but he specifically asked for someone local and I had a 45 minute commute. At that point neither of us were sure why I was there.
2 hours is maybe on the far end of what I would consider reasonable. I might complete a slightly larger project for a more appetizing position.

10 hours is outright. That company is unlikely to value your time when you work for them.
This demonstrates the outrageous entitlement of tech workers these days. It's absurd that the way you treat people who offer you opportunity and employment is by mocking them and embarrassing them! At best, you can be flattered and find an amazing place to work, and at worst, you trash an email without a response. Act like global citizens and realize how truly amazing it is that you have a job let alone many offers, and instead of spending time spewing derision and cruelty, spend it building something great.
AwfulRecruiter.com
Debugging an MRI Ruby GC Segfault Caused by a Buggy RubyGem
I once had a recruiter send me his search instructions:

"Dear Philip,

Must have the following:

At least one strong OO language - (C#, C++ or Java)

AND

At least one strong scripting language - (python, perl, ruby, PHP,
javascript)

Include REST & API in search terms.

It will likely be easier to find someone who's specialty is in
scripting, but has experience in an OO language as well.

We want someone who has picked up multiple languages and has a desire
to do more.

2+ years experience minimum in professional requirement.

Hacker mentality...use the language that works for the specific
situation. "
> We have seen this type of stuff on Android with Dalvik (where Qualcomm has a special library / modified version of the VM).

Which they achieved at the cost of correctness: https://code.google.com/p/android/issues/detail?id=58726#c10

And vendors do contribute performance patches back to AOSP. ARM's Linaro group has updated & NEON-enabled some libraries, Intel contributed SSE optimizations and x86 support in general, Nvidia contributed NEON optimizations, Imgtec for MIPS support, etc...

There's a cost to maintaining a downstream fork, and a slight competitive edge tends to not actually be significant enough to justify the engineering cost.
> I hear some of the instruments were owned by private research institutes rather than European taxpayers (who funded the vehicle) so for some areas may take a while to publish. Might have to wait for proper papers etc

It is not immediately obvious to me why who owns the instrumentation would be a driving factor in the time to see results. Both private research institutes and public institutes would want to get results out as quickly as possible, to capitalize on the PR effect. But that is moderated by the need to perform sufficienly accurate and detailed analysis, which takes time. Those pressures are the same for both public and private research institutes. If anything, the private institues would feel more pressure to publish results quickly, to improve their chances of obtaining future funding.

I cannot tell if you are comparing the quickness of this press release with the lack of results from the scientific packages on Phile, but I will address the (potential) comparison, just in case... Part of reason this press release (with the image of Philae bouncing) was out so quickly is that it does not require a very detailed and specific analysis (requiring roughly the equivalenth of image stictching in photoshop), and the results are fairly straightforward. Additionally, it is not really providing much in the way of new scientific information and so does not have as high a burden of proof. Additionally, the OSIRIS imager has been used to collect data for a while now, so presumably the OSIRIS team has a decent understanding of the real-world operation of the equipment, enabling them to quickly release images in which they were confident. In contrast, the Philae lander's instruments had not provided actual data before the landing, so the instrument teams still need to do the careful calibrations and analysis to understand the systematics.
Riffle: a high-performance write-once key/value storage engine for Clojure
One big problem is programmers tend not to write programs from scratch, rather they work in existing systems.

And even though I'm a static-typing proponent, I will concede that developer productivity is likely to correlate a lot more with the state of your existing systems.
Funny, after some exposure to GNU codebase (including GCC) I used to thought, that evil M$ is trying to destroy free software, by poluting it with horrible code.
F.C.C. Chief Aims to Bolster Internet for Schools
For me, the biggest gripe is the "Company - Confidential" stuff. I can handle buzzword bingo. Nine times out of ten, the recruiter is reading from a script that he or she did not write. No sense in shooting the messenger over that. But I think we've reached peak ridiculousness in terms of "stealth" and confidential companies. Are you recruiting me for an undisclosed company in Langley, VA? Fair. If not, let's drop the top-secrecy. [1]

If you can't tell me anything about what company I'd be working for, I can't tell you if I'm genuinely interested. I'm not a faceless program that responds automatically to the right salary, equity, and title inputs. It's a bit more complex than that. At the very least, I need to know what company and what product I'm going to be working with. (And no, "it's a ___ app" is not sufficient. Show me the actual product).

Some recruiters are awesome, btw. My general experience is that in-house recruiters are better than hired guns. The in-house people know the company and its culture, and they often have direct lines into the hiring manager. Not all of them are great, of course, but there's a better wheat/chaff ratio there.

[1] I realize there's often a political need for secrecy, such as when you're replacing someone currently in a role. Or if you're trying to poach from a competitor for a given role, and you don't want it known that you're doing so. That said, both of these scenarios will out themselves eventually. In my experience, any veneer of confidentiality will evaporate the second you approach your first serious candidate. Especially if you're talking to candidates at a competitor.
I find it pretty cool how authors of text-mode UNIX programs are still around. In fact the GNU culture has kind of grown up around that. And yet, to me text-mode stuff is just a part of a much larger distribution, not something to be distributed to so many systems. Oh, how times have changed.
At the risk of butchering the concept for the sake of simplicity:

In a HATEOS API, clients need to know exactly one entry point endpoint. Nothing else is hardcoded. There is no Python code that happens to know "if you want to add a widget to a product, you POST to /product/$X/widgets". The API itself tells you where to go.

An acid test: assume your API entrypoint is /api. If your API keeps HATEOS kosher, you could in a serverside update change every other URL endpoint in the application without breaking clients, because the clients would be getting those URLs from the entrypoint URL dynamically anyways.

(That's not really the point of HATEOS, but it's a side effect).

There is nothing wrong with simple HTTP APIs, and a lot wrong with explicitly RPC (verb) oriented APIs in general, so adhering to REST principles isn't an absolute good.

This might be the point where 'dragonwriter tells me I, too, have misunderstood HATEOS. :)
Oh god, the "Big Data" project recruiters :')

I always like to piss them off by asking why they should get a cut of my hourly rate, since the don't know what they are talking about, how can they possibly add value?

Or another fun thing to do: send them your CV in PDF format, so they can't "improve" your CV for their clients, that usually pisses them off. I once had a "Professional international recruitment bureau" with "more then 40 years of combined experience" that told me they did not know how to open a PDF file...
Show HN: Payola, the Rails Stripe engine, now has Subscriptions
I personally think that POST should hit an existing resource and create a new, related one. While PUT should hit an existing resource and modify it (if permissions allow). GET and DELETE are pretty obvious. Those are the conventions I use when I create REST interfaces.
I had a recruiter contact me 10 years ago, asked what I was interested in. Didn't contact me again, then 2 years later called me with a really interesting job, (underwater robots!) I didn't get it sadly.

When I was looking to change positions a year ago, I went to look for him, but he had "retired" and became a preacher in New Hampshire. Not sure what to make of that.
Edit 7: Usually I wouldn't share a method for a trick, However in this case it is a mathmatic sequence, and I haven't seen anyone actually use this method. I'm a bit torn here.. but let's go with it.

A version of the concept explained by Brady from Numberphile
https://www.youtube.com/watch?v=EWG6e-yBL94

Edit 8: Here's some more detail for the math types. Universal cycles for Combinatorial Structures from 1990 by Chung, Diaconis and Graham

http://www.math.ucsd.edu/~fan/wp/universalcycle.pdf

And Products of Universal Cycles connecting it's application to card tricks by Diaconis and Graham

http://www.math.ucsd.edu/~ronspubs/08_05_products.pdf

Edit 9: So far I think I've traced this trick back to Charles Jordan in 1919, however given enough time I'm sure there would be better detail.
How to Implement Your Own HashMap
That's what I was wondering. Hard to tell from this: http://fnordmetric.io/documentation/chartsql/syntax_referenc...
> a truly RESTful service that follows the HATEOAS pattern doesn't require documentation to be hosted separately.

It might need documentation of the special media types it relies on to be hosted separately (one place where most "REST" APIs fail to follow HATEOAS is that they reuse generic media types but rely on out-of-band descriptions of the "real" format of the data, so that a client familiar with only the media type and the data would not semantics of the resource representations being returned by the API.)
That is more of an indictment on how poorly REST has been presented. It remains mostly impossible to get a very good definition of REST or point to an API/whatever that is a good example of REST.
The licence of the compiler doesn't affect what you build with it. I expect the reasons are the same most people are switching to clang:

* Modern modular design (everything is libraries)
* Faster compile times
* Nicer error messages

The modular design in particular is a good reason that might not be obvious at first. It lets you do things like debuggers, code formatters and static analysers in a much more sane and robust way than GCC's "no plugins, everything must be separate and flaky" way.
Valley Boys
I disagree. Humour is a method of dealing with frustration. Having unsolicited recruiters contact you with vague terms, simply to meet a quota is frustrating. The recruiters who are doing a good job are not speaking in cliches, or mass soliciting, and so they won't appear on this website.
Headhunting is a strange field. 90% of the recruiters are less than garbage, while 10% are worth their weight in gold.

The one comment I'll add is, like any cold calling, it's a very tough job. At the very least, I try to be polite to everyone, because you never know how hard it is to be in their shoes. In addition, if they're remotely reputable, I'll give them names that fit their search. (In my field I tend to know who is looking)

The key is to shut them down as soon as they start doing anything that smells of being unethical:

- Asking for where else you are interviewing.

- Asking for information not relevant to the position.

- Not telling you which company the resume is getting sent to prior to their submission.

- Pulling lines from Glengarry Glen Ross, Boiler Room, the Wolf of Wallstreet or similar.

It is amazing that many of these folks can keep jobs, but I guess it's like being a gym membership salesperson. Only the best last.
Humans were a 5th dimensional race? That was never the case.

Why would another race give a damn about some primitive lifeforms? Why not? Haven't you heard of Green Peaces?
Uber CEO: Obamacare has been “huge” for business
Open Source Network Function Virtualization, Introducing OPNFV
Computers are fast, Python has good enough performance for most people now a days.
I am not entirely sure why you got downvoted so much - probably due to the 'attacking GCC' part which I disagree with you on, but for what it's worth I agree with your point that proprietary modules and forks are a risk with precedence.

For instance Apple came out with A8X which I am sure required special clang codegen optimizations - where is that code? If that continues to sit behind Apple's closed walls then it's already proving OP's point.
I know the CLR was designed to support multiple languages from the very start, whereas the JVM has historically been very tied to Java. What sort of recent improvements have made the JVM 'more hospitable to diverse language implementations'?
Freegeoip becomes a Go package, web server meets Docker
25% off on one of the best Ruby/Rails courses on the web
> I find all the side programming work I want @ $150-$200 per hour.

That's pretty impressive. I find that people paying a reasonable wage inevitably want someone who is available during typical working hours.

Is this for a particular niche?
The spec for 403 states that "Authorization will not help and the request SHOULD NOT be repeated" so I don't think that is appropriate either. It's a good question though. I've always used 401 and haven't run into problems but I can see why it's probably not correct. I am sure that 400 (with a proper response body explaining the authentication requirements) would not be wrong, but I am uncertain if it is best.
In my world, a 45 minute commute is local (if not ideal)...
Assertions without evidence etc. ;-)
build your own thing, that's the best way IMO.