skysight-inc/HackerNews huggingface dataset:
I do understand why he behaved this way. Look at the recent attempts to coerce various high-profile projects into adopting a particular code of conduct. These attempts invariably introduce identity politics and drama into a previously purely meritocratic community, and result in a huge amount of wasted time and lost productivity.

Regardless, I don't think he went about it the right way. It would have been more effective to simply reject the patch with a note stating that the variable name was appropriate in context (assuming it was so).
Right, my bad. Though there is hardly any 'code' in there. I copied the defines from LLVM initially as I couldn't find any good documentation except in the header file. I suppose I will have to retype it or something :-)
It's also there for the previous 512 bit prime. Probably just the style preference of the project.

Edit: Actually, it looks a lot like the code was originally generated using openssl dhparam -2 -C: https://gist.github.com/xnyhps/df16e7d43e32b7dbe3fb
Your comment calls "code review", the practice, "toxic". You go on to suggest that project maintainers "merge [the pull request] already and be done with it", suggesting that the normal review process not apply to this particular diff. You suggest that there should be a high bar for commenting on other people's code.

Your comment sounds to me like it advocates lowering the bar for merging of external patches. That's a sure way to technical inferiority.
The IPO price was $42.50 per share split adjusted. Which I brilliantly passed on. I mean how could some search software be worth that much?
I used to use it for that but now with chrome profiles I've setup a new person for that called Mr Debug. It's good in that I can enable different extensions, ones that I wouldn't have enabled normally and disable the ones that interfere with dom inspections (looking at you Evernote).

You can run both at once.
What has rust to do with Nix?
Yep, Google does this exact same thing. I search, I buy, and only then I see ads for a product I already own.
I'm struggling to understand why such a term in a codebase would be offensive. Even if it were intentional (which apparently it's not) I fail to see how it could be considered 'exclusionary', as claimed. Frankly, the author comes off with the baffling sort of self-righteous political correctness which scares me a little in it's reductiveness.

That said, this is obviously not the way to build a community. Kicking people out for this sort of thing sets a bad precedent. If enough people found this offensive to enough to back a change, then maybe it's better to accept that view as legitimate, even if it's not one you hold.

Of course, we only know one side of the story, so maybe there's more to it.
> So unless you did profile, your comment didn't really add anything.

The previous comment explained why and how the author's analysis is flawed. Then it goes over top by speculating exactly into the opposite direction. But that doesn't reduce the quality of the first part of the comment. That part was still valuable to me.
I find it ironic that his complaint was of "exclusionary language", when his own language looks like this:

> This does not mean "all men suck". This means "society's conditioning and understanding of what 'male' means tend to result in a condition of suck". It's toxic for everyone (including those men. Of who I count myself a member).
I agree if page numbers are not visible. If page numbers are visible, next and previous page perfect sense.
I wish more project maintainers would emulate the good example Duncan set here. Identity grievance is a terrible disease for an organization to contract, but the prognosis is good with early and aggressive treatment.
Absolutely disagree with number 2; if the numbers are hyperlinks to other pages they should be underlined. The underline on links informs the user that it is a link to another page (i.e. they will be navigating away from the current page), that the interface is page based, that clicking the link will add the current page to the history and that their back button will work, etc, etc.

Removing the hyperlink makes the numbers look like numbers. The user will have to "learn" that they can click the numbers.

Oh, and make them blue!
I think that if you are going to teach someone the craft of programming (which is different from computer science) -- really teach them, you should follow what I call the Old School Curriculum. The Old School is based on the way many kids learned to program in the 80s, and the 80s version went: first BASIC, then assembly, then Pascal.

The first language you should learn should be a doddle to learn, even if it isn't very powerful. This was BASIC (or sometimes Logo) back in the 80s, but you could probably substitute Python or even Scheme today. This language teaches you concepts like these:

* Computers follow instructions supplied by the programmer

* The instructions have to be carefully worded in order for a computer to follow them (i.e., intro to errors and debugging)

* Arithmetic and mathematical operations a computer can perform

* Computers can remember things (i.e., variables)

* Computers can interact with the world (input and output)

* Computers can make decisions (conditionals and program flow control)

These are the very fundamentals of programming and it's amazing how many people haven't internalized these concepts at a deep level.

You can actually get very far with BASIC -- entire companies have been run with BASIC code. (Software written in and for Business BASIC variants was a major industry back in the 1970s and 1980s.) You can get even farther with Python. But once the learner is ready to go deeper, it's time to begin Phase 2.

The second language you learn should be assembly, which familiarizes the programmer with how a computer actually works at a fundamental level, as well as important concepts like CPU word length, memory addresses (essential for understanding pointers), program call and return (and stacks), etc. You don't have to even complete a large project written in assembly to get the benefits of this low-level, bit-twiddling learning.

Finally, the last language you learn should be Pascal. C or C++ would be today's equivalent. In this phase you synthesize the knowledge of high-level programming, structure, and control flow that you learned during your "BASIC" phase with your low-level understanding of machine details that you learned during your assembly phase. Then, the details of how and why the language works the way it does make much more sense.

So yes, to me it makes total sense to teach C -- as (at least) a third programming language, perhaps after several years of proficiency are acquired in the other two (depending on the student).
Given the post and especially the authors comments on the blog, this seems probable.

EDIT: I mean, the author definitely knew that this is the thing that brings hate mobs on twitter, so by this blog post, he wanted to start a harassment campaign.

I can understand why they would kick out toxic people like that.
It takes the combined work of millions of people to even create the simplest 3D destktop printer as of today, you're not going to produce one that travels to extraterrestrial bodies and replicates itself anytime soon.
We are using jspm on an inherited codebase that was concatenated "by hand" with Rails' asset-pipeline (it has lots of old libraries and the overrides are very good to handle them).

What we hate is jspm is extremely slow in development for us. There are two main causes:

- The amount of xhr. This is solvable with http2's server push (but
our dev server is in Ruby, and there's no http2 webserver yet).
- Apparently jspm doesn't cache the result of Babel's compilation,
so for each page refresh every file has to be recompiled again.

We will look at Webpack2 when it's released, if it allows us to use these legacy libraries and wins us some development speed we will not look back.
Berkeley is hard to cluster... the undergrad population has a much more diverse demographic profile (hugely more first-generation college students & more nonwhite students). I'd say the students have more raw talent, but generally less economic and cultural capital than typical students at top-tier private universities. The faculty is Ivy-class (though larger!) but the university itself suffers from periodic shortfalls in the state budget.
This is so true. It's human nature to take everything for granted. I need to constantly remind myself that even though I'm not rich, my salary as a frontend developer is definitely way above average. On top of it I work for a big corp with a lot of benefits and most important of all a healthy work climate with exceptional work life balance.

To really appreciate our situation one could try to take a month off, and try to live with a limited budget after paying off all the monthly fixed costs. If you have to decide between buying a fancy gadget or food, I think it will be easier to emphasize with people who have to work hard just to provide for their families.

I'm happy working as a programmer because I don't have to do repetitive work like for example selling something. Sure, it's not always as exciting as working on a green field project because there is enough legacy code to maintain but overall I like my work.
This is not at all obvious, would you care to expand ?
are there any sample pages running with Jekyll 3 to see?
Honestly, I don't know where "Next" and "Previous" idiocy stems from, but Older and Newer is what I've used too. Now that I think of it, perhaps I should write Greasemonkey script to try to replace next and previous where applicable.
Ok, you have a point.

Original author's analysis is flawed, it doesn't extend to multi-socket systems.

What we don't know is how thing scales beyond a single socket. The graph is not going to tell us anything about that. Profiling will.

Experience has shown to me assumptions are bad.

So now I don't assume a certain call will succeed or even work the way I think it does. Instead I check return value of every call and test it against my assumptions.

I never assume much about performance either. I might occasionally use microbenchmarks as a hint. But the main mode of operation is measuring as big of a piece of functionality as possible. Many different size, but realistic, workloads. Preferably on multiple different systems as well.

If performance is the goal, I'd advocate one trying out different concurrent hash map implementations in the system one is building.

Never assume.
It's really interesting how the sprites are implemented with PSETs
The article reminds me of the book Flash Boys by Michael Lewis. Lewis also describes what was going on (and maybe still is) at the Wall Street with dark pools, HFT and normal traders. Definitely worth the read.

EDIT: maybe I should've read the article to the end before commenting. But my recommendation for Flash Boys stands. It is a good book.
Migrating a Parse app to the Azure cloud
we looked at jspm and switched to webpack. detailed comparison here:
http://blog.dripstat.com/why-we-switched-from-jspm-to-webpac...
I fail to see how using a pre-made Bootstrap template means 'stay away'?
My take on this is that the culture flows from top to bottom. Decision maker should be the one who start the process and pass it on.
Its better if you try to put your hands product management and start to improve it from there. They will soon realize the benefit of this and that might bring the change.
Organized mind – devil's enemy
Absolutely. This reminded me to subscribe his complete rss feed, before that I had just the 'Money Stuff' feed in my reader.
No connection between Greek and Italian doesn't seem right. Many Italian words are influenced by Greek, to the point that antique Greek is studied in some schools.
AIUI these researchers are complaining about what might become of their data after they have published their studies.

Edit: no, on closer reading, I am incorrect. My bad.
How would one go about calculating the Fourier series for an elliptical trajectory?
And here is the exact phenomenon we're talking about, in action!

Back when neural nets were "fundamentally novel" we didn't have the understanding or computing power to tap their potential. So they "weren't really AI" because they couldn't do much that was interesting.

Now, we have a better understanding of how to use them, and we have enough computing grunt to make them do really interesting things. But they're "not really AI" because they're "not fundamentally novel."
Indeed, I think you're correct in this.

You'll find two arguments against this in the wild – "we've always used that terminology," and "it's the only way to describe the relationship." I don't think either are that convincing.

I used to be pretty clear that I thought this was a stupid thing to complain about, until one day when I was presenting a small distributed software project to a group including non-technical people. I explained about the 'master' and the 'slaves', and at the end someone asked 'why did you use those terms? Isn't there something nicer we can use?'.

I realised that they weren't complaining because they were offended or anything, but because slavery is sort of not a nice thing to talk about – the fact that I was used to those terms in a technical context maybe blinded me a bit to the fact that others might find them distasteful. They were changed, everyone was happier, nothing was lost.
> Your comment calls "code review", the practice, "toxic". You go on to suggest that project maintainers "merge [the pull request] already and be done with it"

I'm with you until there :)

> suggesting that the normal review process not apply to this particular diff

If the normal review process is to feel diff should absolutely be commented, then yes, totally, applying it to such a small and casual diff makes what I feel is the ridiculousness of the process totally shine.

Note that I'm not saying the diff should not be read. I'm not saying either we should not comment other people code if we feel there is a problem with it. I'm challenging the fact that this diff should have generated discussion, and call the fact that it had a problem.

I don't think making teams more efficient lead to technical inferiority. And to me, the abuse of commenting code is all about inefficiency (regarding both productivity and sane relations between team members).
This is a devastating account of today's society.
OK fine, I wear my glasses all day. Not gonna wear them to bed, sorry.

Yours is a very weak argument, find a better one.
When watching h.264 VLC consumes lots of CPU when QuickTime doesn't. I don't know why.
Same here. Even had an 8-note keyboard-driven music player built in, iirc. Although it lead to a life-long interest, I never really wrote anything 'serious' from scratch since then. Scripts and editing others' code was about my limit.

And this is despite trying at 12-13 to 'go pro' with Visual C++ ordered through a student discount and the C++ For Dummies book (I had no idea where to start) that never took off the ground. A wish there was a local group or mentor I knew about back then!
I regularly use JSPM (with systemJS) for new projects, and I've liked it a lot.

Back when webpack first came out, I struggled a little bit with figuring out what it actually did. While I understand now, I am not why I would want to (or you) switch from JSPM to webpack. I don't see any features that webpack has that JSPM doesn't (and JSPM offered ES6 support well before of course, with babel on by default).

I like to use JSPM because of how relatively easy everything fits together -- and how straightforward it is to use and configure.

For those not familiar, JSPM is a package manager, module bundler, and module loader all in one for javascript applications.

This means you can:

jspm install <package>

And JSPM will look in NPM/Github (and it's possible to add registries, like bower) for stuff . That's the package management facet.

jspm bundle-sfx js/main dist/build.js

Bundle your code all together, and drop it in a file

<import src="system.js">
<script>
// set our baseURL reference path
System.config({
baseURL: '/app'
});

// loads /app/main.js
System.import('main.js');
</script>

Load your modules on the fly like you would with something like RequireJS.

As you may have guessed, JSPM relies on SystemJS (https://github.com/systemjs/systemjs) internally for some of the features above.

This video really opened my eyes to what it could do:
https://www.youtube.com/watch?v=iukBMY4apvI
hey thanks for that!

we are serving our JS files as static assets behind nginx - we dont run nodejs on the server. does webpack allow you to create static assets (htmls,css,js) and serve them ?

the big issue is of course the fact that some libraries (Handsontable) are coming from github and are not on npm. is it possible to use them - with overrides,etc. ?
Twitch VR Analytics – Visual app for understanding your Twitch account stats
Clojure Survey 2015 Analysis
I hope you're right, I want you to be right. But honestly, I can't see it. A lot of what we do essentially lives on credit.
We're like real estate. We're in demand as long as there is a buyer. Essentially, buyers will cease.

We're not doctors, cops nor lawyers, the world won't cease without us. Hell, even civil workers in governments although less salary, have better safety than we do. I can't shake the feeling that essentially we'll realise that all these companies we work for don't really "exist" as they're just the imagination of someones account balance. At some point its gotta run dry.
There's a paragraph in the article that explains that when such an investor places an order with a broker, it gets broken up into many small orders, which are indeed at high risk of being tagged as "too much positive alpha".
"But wouldn't any other researcher who obtains the data from doctors who recruited the patients have to give credit to the doctors who shared their data?"

In academia, it's better to be the primary author of a paper. More primary author publications makes it easier to get funding, keep your job and advance your career. If you share the data that you might have spent a lot of time and money collecting, you will either gain a citation or a non-primary author position. This is worse for your career. I don't like the system. Most academics would prefer to share to have their work verified or even to see what others might find but the incentives are to keep it private so that you can squeeze as many primary papers (or papers from your research group) as possible out of a data set before sharing the paper.
ANSI C++, section 23.4.2 and 23.4.4, doesn't specify the implementation only the complexity requirements.

Any C++ implementation is free to choose their std::map implementation as long as it meets the requirements, it doesn't say anywhere that a RB Tree is required.
Opendata.swiss is the portal for Swiss open government data (OGD)
Mercurial 3.7 release
I'm using SystemJs + JSPM and it's awesome. I previously made use of bower + requirejs. I love how JSPM automatically populates the config.js file so I can start importing whatever I installed straight away. SystemJS loads pretty much any module format so it was easy to use AMD modules while I was migrating to CommonJS. I recently moved over to ES6 modules without having to touch my SystemJS/JSPM config. I've not really looked into Webpack. It seems to be more popular than SystemJS. When I was considering it, the docs were not that great.
Small exercises to get you used to reading and writing Rust code
well i like jspm, but as others have mentioned - it is too slow.
is there a way to compile all the dependencies and cache-buster-fingerprint them ? I serve my app statically using nginx and cloudfront.
Let's be clear – it is not pragmatism to kick productive members of the community out of it over minor issues. If anything, it's the opposite.

Anyone who complains about something as trivial as the variable name in question is someone who lives for attention-seeking and virtue signaling

As I've pointed out elsewhere, I find the complaint ridiculous. I'm also keenly aware that my view is not the only legitimate one; there appears to have been an number of other people who felt the same way about this particular issue.

It's bad community management to tell participants that their views are not valid, and to unilaterally kick them out. One of the authors points is important – it creates a perception that complaints or suggestions will not be taken seriously. And that's not useful to a community.
TalkTalk call-centre workers arrested over customer records security breaches
Magic Leap secures another $794M in funding
So SELECT yada yada LIMIT n + epsilon + 1, and if you get that many elements out, display n, otherwise, display all of them.
True the origins are cryptic, but it's become pretty iconic and recognisable. For a nice example take a look at this tweet (the author is semi-famous for selfies captioned with "Come to <place> in the next 15 minutes if u want an ass-kicking") and try to imagine a similarly funny/engaging tweet about any other piece of video playback software.

https://twitter.com/drewtoothpaste/status/525044698071957505
The original line from the editorial was:
" There is concern among some front-line researchers that the system will be taken over by what some researchers have characterized as “research parasites.” This issue of the Journal offers a product of data sharing that is exactly the opposite. The new investigators arrived on the scene with their own ideas and worked symbiotically, rather than parasitically, with the investigators holding the data, moving the field forward in a way that neither group could have done on its own. "

I do not read that as the editor calling researchers parasites. Rather, the editorial is exploring different ways of data sharing and collaboration.

See the NEJM editorial that sparked the controvery at http://www.nejm.org/doi/full/10.1056/NEJMe1516564

The blog post appears to go to some effort to misinterpret the editorial.
Generating those parameters is very slow. Just run `time openssl dhparam -text -noout 1024` a few times and see for yourself.
Do you have cache disabled?

Also, how long does your actual bundle time take? For small projects, I actually get away with just triggering the bundle command when appropriate files in the project change. I highly doubt it would work for you, but if you're spending 10 seconds waiting for stuff to come in over the network, and your bundle command runs in 5, you could just do that instead, and actually work with the bundled code (and generated source map)

Looks like I'm not the only one who thinks it's sometimes a good idea:
https://60devs.com/optimizing--default-jspm-workflow-with-gu...
Why is that? With abundant clean power you can have everything under the surface: space, daylight, clean water, air, food, wood. I'm guessing more could be recycled if energy is not a concern. Surface could be the place kept nice where you go for vacation, all other activity could move underground.
Profound and quite philosophical article! That’s right, “poor design teams deliver the UX people ask for. Great ones deliver the UX that people need,” but the worst design teams deliver the UX for the UX sake. It’s so popular now and item 8 of your article only prove it. Hope design proselytism won’t make it till 2017.
Typically QSBR algorithms don't require blocking the world, or even blocking any single thread. They just require each thread to periodically check in and run a bounded amount of code which amounts to "hey, I'm not currently looking at the map".

Some other background collector thread (which is going to actually delete removed objects) just has to wait until it sees every mutator thread cross a safepoint, at which point it knows that none of those threads could be hanging onto references that have been unlinked from the data structure.

I'd recommend reading some surveys of RCU and SMR algorithms if this stuff is interesting to you.