skysight-inc/HackerNews huggingface dataset:
Well, perhaps some have (haven't looked at this closely), however, since in nature the various types of it are only used by specific bacteriophages, i.e. as I understand it they are or tend to be species specific, using a particular one against other species of bacteria should be fruitful.

Then again, interspecies transfer of resistance through e.g. plasmids happens.
Certainly, we are a social species. There are thousands of social species. Isolate certain birds from social interaction, and they'll be depressed as well. I'm not talking about real isolation, they kind they do in psychological experiments.

What is conjecture, as far as I can tell, is that we're "hardwired to function by looking for approval from others".

> it's what evidence from pretty much every bit of research on the subject shows - from psychological experiments to brainscans showing that feeling "pain" over not being treated nicely isn't a metaphor - it actually activates the same areas of the brain as things that physically hurt.

But that doesn't tell me the order of operations. Is it,
a) Someone does something "not nice" (leaving aside whatever that specifically means)
b) My senses take the event in
c) My lizard-brain activates my pain center
d) I have a bad emotional reaction

Or is it
a) Someone does something "not nice" (leaving aside whatever that specifically means)
b) My senses take the event in
c) I have a bad emotional reaction
d) My lizard-brain activates my pain center

?
q is a neat language, and I spent some time studying it when I was in finance, because it's useful to know q/kdb if you're a quant.

Here's an offensive but accurate taxonomy. There are 6-month languages/technologies and 20-year languages. The 6-month set are optimized toward being quick to learn fast. Java, for example, inherited C++ syntax while cleaning up the OOP, so the C++ programmers of the time could pick it up in quickly.

Now, q and kdb are 20-year languages. It doesn't take 20 years to be productive with them, of course; it's that they're designed to optimize a person's productivity over 20 years, and not in the first 6 months. Unlike the various distributed tools out there (Hadoop, Hive) it will take you a long time to learn them, because they aren't like anything else. Superficially, q is Lisp-like, but the performance implications are very different and it doesn't look like a Lisp at all. (It parses right-to-left, for one example; also, it's written as a stream rather than in nested s-expressions.)

Many of these modern tools being bashed have grown up in a world where 20-year tools can't really be built; they'll never catch on commercially in a world where people change jobs every 2 or 3 years, when MVPs are more important than solid decades-proof engineering, and where employers are pretty averse to their people taking time to just learn new technologies.

There's too much volatility in the world for it to make sense for most people to learn q and kdb right away. You can get half-decent in a couple months, but it'll take much longer to learn why those tools are (for some use cases) so damn powerful.

This 6-month vs. 20-year tool concern is part of why I've gravitated toward Clojure recently. I haven't seen anyone else do quite as good a job of balancing those two need sets as Rich Hickey and the Clojure community have. Clojure is (becoming) a 20-year language, but it's no harder to become basically productive in than Python or Ruby.
If you are looking for a self hosted solution I would recommend taking a look at Dokku. Its like a self hosted mini version of Heruko.

https://github.com/progrium/dokku
I don't think I agree with your point. Javascript is a very small language, and while there are a number of gotchas they are enumerable and well-defined.

Central concepts:

- Objects

- Prototypes

- Scope chains

- Closures

- Function.bind, Function.apply/Function.call

Gotchas:

- Behavior of the "new" operator

- Value of "this"

- Type coercion, falsiness of "", == vs. ===

- var hoisting

- if/for/while do not create scope

- function expression vs. function declaration

Many of the gotchas are self-evident if you learn the central concepts.
Could this post be made into a poll?
The beauty of a programming language comes from being small and consistent. Such as Smalltalk, which has only 6 reserved words and implements message-passing as if it is a function call. This is the brilliant idea of Smalltalk - message-passing + blocks + booleans and out of this everything else is implemented. Classes are of second importance, but delegating (via message passing) to parent or another object was invented here.

Scheme, on the other hand, was also minimalist and consistent - s-expressions and about dozen special forms, and out of this everything else could be implemented, including closures, continuations, and classes and message passing, if needed (CS 61A 2008 does this for you).

Haskell is.. well, everyone know what Haskell is.

As for APL, in my opinion, the power of a language comes not from using esoteric math notation, but, like in CL or Scheme, from possibility to easy add new control structures (call/cc) and special forms (with macros) or even create a new languages, such as Arc.
I'm currently a resident (not in primary care), so I'm biased. But:

* Nursing sucks. It's terrible work. On top of that, you have to deal with jerk doctors and jerk patients. Not a single one of my many doctor friends would ever have considered nursing over med school. (Side note: if you meet a good nurse, thank them! Truly good nurses are rare.)

* PAs generally do not know all that much about medicine. With very few exceptions, it was frankly terrifying signing out my service to them every night, and never fun cleaning up their messes in the morning. But with resident work hour rules, there is no alternative.

* The bottom tier of medical students/residents aren't very good either. Pay doctors less and the smart ones will realize that maybe there is some other way to achieve life satisfaction, because money won't be a differentiator any more. Care will get worse but the general public won't notice or care. They will keep getting fat, diabetic, and ever sicker, insist on keeping their essentially vegetative elderly relatives alive at all costs, and then complain that healthcare is expensive.
The dynamic in the industry is obvious: its content creators versus content distributors. Tech companies are the latter. Of course they think that copyright hurts "innovation." What they really want is weak copyright laws that let them keep the maximum amount of money in the chain. But when you think about it, people don't go to Youtube, Netflix, iTunes Store because some engineer at a tech company implemented a really great video player or ad distribution platform. The part of that transaction that is the biggest value-add to the consumer is not the part the tech companies do. The big value-add is content. That's the important part. So why should the tech companies make all the money in that chain?

If the media companies weren't such dicks suing grandmas, people probably would have more sympathy for them. Here is a vastly bigger industry (all US music + movie sales are less than Apple's revenue alone) pushing for weaker property rights so they can keep more of the profits in a transaction where someone else does the real valuable work the customers are paying for.
I just used them for a small project and was really happy with it. They provide just a couple environment vars attached to the process object and you're good to go.

I was talking to some of their employees at nodeconf this year and they explained that since Heroku only routes one request to an instance at a time, it essentially blocks on each request and you never get to actually leverage the concurrency of node.
Edward Snowden's not the story. The fate of the Internet is
Buggy whips, sure. Or record shops, to use something closer to current times.
Seconded. For our production game servers we've only used EC2 but a couple of us have started working with digitalocean for our own projects & are very happy with them all around.
Sure. At MS, I used it while working on mortgage prepayment and default models. Before we got the K license, I had been using SAS and R. There, I had been dumping aggregated (or sometimes not) CSV files from the database (Sybase) and running my model fits based on those.

I had a bit of exposure to A+ then, trying to debug bits of the interest rate model subsystem. I hated it. We were mostly using A+ as the wire protocol at that point, and I had endless problems getting the APL fonts set up, and so on. Non-ASCII was a huge black mark.

Once we got the license and expanded the team working on the models, we decided to switch over to using kdb+ for the basic data store. That switch was like going from night to day. I could operate over the entire dataset, rather than just on a subset. I could query things on the fly with real aggregations. Things that were a huge pain (and slow) using SQL were suddenly fast and easy, like "calculate the average default rate grouped by FICO in 25-point buckets, for loans issued after 2005" or "backfill missing data from the first non-missing observation."

The first example can be done in SQL, but it takes a whole lot more typing and is (IMHO) much more error-prone. The last, I'm sure you can do it, but it's a nuisance.

I first got comfortable with kdb+ as a database query language. I read "q for mortals" by Jeff Borror, and we actually had Jeff around for a while for questions.

After that, it we started actually using q to estimate the models. It was great at the data aggregation and was a pretty natural fit. It didn't have anything built-in, but so we wrote a few functions for multinomial logistic regression, and that was good enough. That part didn't have a huge advantage over using something like R. However, the interaction with the large data store was far superior, better enough that it was worth it to write our own routines to do the estimation.

We even used q to run the models in production. That was more of a reach, but it worked pretty well.

So, I liked kdb+'s ability to handle large data sets in a speedy way. It makes a fantastic query language. I liked q's conciseness. It doesn't matter much for actual in-production code, but if you're doing research, every character counts. It seems shallow, but I think it's a real effect. Writing a half-line of q to do a paragraph of SQL is a huge win. I liked q's array operations, but by then I'd already been using Numeric and numpy and such for a decade, so those weren't really new. It was nice to be able to write them easily, as opposed to something like "np.concatenate((foo,bar))", but it wasn't really novel.

Basically, it was kdb+ that sold me on q.
Exposing only the "Add new card" and "Charge Amount XX" methods actually makes sense, Thanks for the info!
Programatic trading software at Publicis-Omnicom
Their node stuff is hosted on Windows, so some compiled modules will fail. Also, have had the deployment status lie to me a _lot_. Big green ticks when my app failed to deploy. Telling me the app has been updated to a new commit while still blithely serving the old version for _three days_.
Minimalism is oversold. K specifically eschews minimalism, providing an essential list of operators and combiners (verbs and adverbs). It's no "6-word" language. Every character is a word in other languages.

We don't have six characters in the English language.
This makes all the difference:

"Yet India’s Central Monitoring System, or CMS, was not shrouded in secrecy"

Doesn't make collecting all that data ok, but the fact that it's not all cloak and dagger means that people know what the government is doing in their name and they can vote for a change if they disagree.
Is there a Dummies Guide to customising bootstrap (literally or figuratively)

I would rather not waste the time experimenting these days
I find it much easier to read some Q/KDB I've written earlier than the equivalent C++ or C#/Java. For three reasons:

1) It is extremely terse. A small block of code will do what pages of boilerplate class definitions, interfaces, setters/getters, declarations, typedefs etc. will achieve. There is usually no need to navigate through a spaghetti chain of virtual function calls.

2) It is interpreted. I can quickly (without compiling) cut out chunks of the code and run them to understand what they are doing. I can create variables on the fly, fill them with test data, and run the function. If it calls another function, I execute the name of the function and it returns the function code, since functions themselves are first class variables.

3) It actually becomes easy to read because it is easy to parse, for both machine and human. K/Q is read right to left, and so breaks some traditional conventions. For example, 5*6+3 will evaluate to 45, not 33. At first this can be disconcerting, but eventually you will realise that parsing a line of code no matter how complex it looks is quite simple - you mentally start at the rightmost token and start gobbling. This is probably why the interpretor is so fast as well.

As someone mentioned below, I'm not sure why you'd consider it "too cryptic". Anything is cryptic when you first encounter it. I suppose the difference is that Q/KDB provides an (extremely valuable) solution to the financial world - the handling of big data long before it was even called that (a tick database with billions or trillions of rows) so there is a valid motivation to learn the language and it doesn't feel cryptic at all once you've immersed yourself in it.
somewhat related: this paper describes the haskell innards of Chordify, a web service that annotates chord structures of songs from videos or sound clips

http://ismir2012.ismir.net/event/papers/lbd2.pdf

http://chordify.net/pages/official-launch-of-chordify/

______________

The reason i picked up the book: I was thinking whether it was possible to annotate just intonation from equal temperament, but I think that's a limitation of MIDI that it can't do that. Also, eagerly awaiting §11.4, "Soundness and Completeness of Music Algebras".
PrettyGoodSync: Find Public Keys For Your Contacts
It's meant to be used as part of a web form, so just submitting the form would save the proper HTML code.

Alternatively, you could use JavaScript to get the value of the input. It's just an HTML textarea element.
I really hope you're right. I think giving people visibility into what their health care actually costs is the only hope we have of fixing our health care system.
Candy Crush Reveals and Confirms Life Lessons
Thanks, that's very interesting. Q for mortals is online and seems to be a good read, if anyone's interested:

http://code.kx.com/wiki/JB:QforMortals2/contents
At my hospital, residents take 24-hour calls. The trouble with shorter calls (say, 12 hours) is increasing the number of transfers of care. With 25 patients on a service, spending even five minutes on each means each "shift change" would take two hours. So you spend closer to one minute on each, and at that point it's easy to miss important details. We are skeptical of the "scientific research" because we've all seen errors made because of poor signout that were not happening before work hours were so restricted.

For the record, attending ER shifts at my hospital are closer to 8 hours, and residents do 12 hours.
Block any TCP protocol starting with string "SSH-"

Problem solved.

Seriously people think SSH or VPN is advanced? Every clear text handshake protocol could be blocked at ease.
http://www.greensock.com/gsap-js/

GSAP is more robust than these. With reverse playing and yo-yo'ing....so surprised it isn't mentioned more on here.
Setting up Spring web-project on IntelliJ using Maven
Coordinate Currencies, or Stagnate by Thomas I. Palley - The Globalist
Eckhart Tolle on Being Yourself
Probably nothing. The human race will quite happily walk off a cliff together, apart from a few of us that is.

Perhaps we need to just step back and watch it happen, then say "I fucking told you so".

I'm not particularly happy with that idea, but I see no other option.
Passive income always sounded to me like either a fantasy or a career of ripping people off.
It's a very nerdified take on music theory which is only popular with "computer music" researchers at universities. It would be a poor way to learn music theory in the way that musicians think about it.
>"I'm sorry, but that is incredibly shortsighted, and I wonder if you have ever been on the receiving end of bullying if you believe that.

I'm not the parent, but I certainly have been subject to intense bullying. I agree that "sticks and stones" is often a gross-oversimplification of actual bullying, but I also think it's a stretch to call this bullying.

>"If you are a passionate creator of games, I'm pretty sure that you care about what the games industry says about you."

His game was pretty unanimously well-received [0]. That's overwhelming validation as a "creator of games", there's little/no contention on that count.

All the disdain stems from his hypocritical persona. I expect a little honest self-reflection about this or even just a less itchy twitter finger could have a gone a long way toward helping that.

0: http://www.metacritic.com/game/xbox-360/fez
Yes he would be know as a person who likes to look at naked girls. That will surely not do a goddamn thing to his reputation, unless he is a nun.
Excellent points - something every tech startup founder should keep in mind.

Teh Portly Dyke's "How to Fuck Up" is a good companion piece. http://portlytruestories.blogspot.com/2007/11/how-to-fuck-up...
B+N is an even worse scenario, in that a buggy whip company can pivot into the lucrative adult toy market with little change other than inside the marketing dept.

"Expensive used paper retail" aka bookstore has no pivot options not already supersaturated. Coffee shop? Music/Video physical media store? Toy store? "Educational kids stuff" store? Generic department stores? Gift shop? Used book stores? All full marketplaces, or in decline, or both. B+N has been pretty good at picking trendy overdone and declining sectors to expand into. I think they need a in-house residential real estate office and a cupcake shop.

Their only hope seems to be outlandish. So they've got big mall stores... I know, give up on all this "book" stuff and become Tesla Automotive Dealers. Keep the coffee bar, I guess. My local B+N is architecturally beautiful compared to local car dealerships; it could work out well.

Larry's speech is pretty much the opposite of modern crony capitalism's "too big to fail". Its possible the only move left for B+N would be into govt bailout/jobs programs.
Why do you think a given language must have only one representation? There are core concepts at the heart of J and K. This tight syntax is one way they can be expressed, but there are others. We are certainly not limited to the simplistic character editors of the past. More than one simultaneous representation of a program can be shown and worked with -- concise, extended, graphical...
I think they just need to be a better bookstore. Think of Powell's in Portland OR. It's my favorite thing to do in that city and I barely ever buy/read paper books. They also have a building nearby the main one that sells only technical books.

The reason I like shopping and buying books there is the sheer selection. Of course, their footprint is much larger than BN. But BN could raise funds to expand their stores slowly and see if it works. Powell's has several floors of books and are probably larger than many large libraries in big cities. Next to each new book they also stock used books of similar or the same titles.

I just really enjoy the act of flipping through an entire book and then buying it on the spot. I don't think paging through the ToC in PDF form a la Amazon is that nice and I hate waiting for shipping. Plus, if on a technical book I'm going to spend $100 then I need to make sure for myself it's a decent reference.

It's been painful to see BN push the Nook. And to see them try to be a coffee shop. And CD store. etc etc. For the size of their store, they have a remarkably small selection of books, and they're all high-priced... and they complain they can't sell many books. Sorry, when I walk in to the store and see 4 crappy books on CSS, 10 on HTML, 5 on Windows, and a smattering of others, I'm not that inspired. But in Powell's technical bookstore, when there's a whole aisle on Javascript, I get excited.
Everyone certainly know what Haskell is: a thin layer over a typed lambda calculus. Everybody always overestimates and oversells its complexity.
So far I've been using Heroku, but lately as the apps I've been trying to put together have begun to have more interconnected pieces, their service has started to become stifling. For example, getting nginx to proxy to Node requires convoluted setups like "buildpacks" and other Heroku-specific custom configs all of which can be alleviated by switching to a VPS, which is what I'm planning to do in the coming months.
Perl was started in 1987, Python in 1989 [1].

[1] http://python-history.blogspot.com/2009/01/brief-timeline-of...
So run through their proxy instead?

No thanks.
Shortly after Aaron Schwartz's death, there was a lot of resentment for the more traditional information-distributors, such as Elsevier and other big publishing companies.

But you make a great point about ACM and IEEE. As a student (and now an engineer in industry) in the CS and applied math fields, I can't count how many times during research where I see a useful article behind an IEEE/ACM paywall.

Are you aware of any efforts/campaigns to demand more open access from these two behemoths, who pretend to be on our side?
Yes, you can choose to install GPGMail, GPGPreferences, etc., without MacGPG, and use your own gpg binaries such as from homebrew.
Don't mistake looking complex for being complex. These languages have very simple and clean grammars (or they'd fall apart quickly), which is quite a contrast to the dog's breakfast that is modern C++. A simple grammar = simple to read once you've learnt the syntax. There's no issue in having a lot of symbolic operators if they all work in a clean and consistent way.
Do you know a lot of Hacker News is not indexed by google?
Oh goddamn, this is amazing. As someone who hasn't even seen Ruby code before, you could include a bit more on the syntax of conditional/loop constructs (if/while/etc), but it's amazing. I'll send this to my non-programmer friends right now.
I own all three books in that series. One was out of print and I paid a lot for it. Excellent reads!
Barnes and Noble is an inconsistent experience. For example, at the Roseville, MN store, the technical book section is usually on par with, or sometimes even better than Powell's.
However, almost everywhere else, even at other locations in MN, the stores mostly suck. There used to be a couple of great Barnes and Noble stores in Manhattan, but they have closed.
The Man Who Put the Super Into Modelling
surprised that such article appeared on a column normally dedicated to beauty tips etc. think it'll make an interesting read for those interested in the vanity business :)
There's nothing hard about C. I fail to find support for your position on this.

Pointers? Really? Nothing could be simpler so long as you understand how a basic microprocessor works. Perhaps I see it this way because I started my programming experience typing machine code into a hex keypad. I can see that someone who comes from a frame of reference devoid of low level exposure can get confused by something as simple as pointers.

Even so, easy teaching analogies abound, for example: A pointer is the number of the post office box. The data is what it contains.
Interesting how one word is not mentioned in the article that has a huge impact on the issue of wages for the lower classes.
Bergia recorre el interior chaqueño | Provincia
Because full employment even when we have labor surpluses is desirable as who knows what people would do with too much time on their hands. I'm only half joking about this.
Chromecast: Exploiting the Newest Device By Google