skysight-inc/HackerNews huggingface dataset:
> As for Haskell, do consider that while the base of it is quite simple, just like Lisp

Lisp is only syntactically simple. (Admittedly, it is syntactically the simplest.) Semantically, it is still a mess.

> it also has the massive ball-of-wax that is monads, which people have been trying for years to explain simply. [1]

That is a weird thing to say. Monads are simple: an endofunctor "T : C -> C" with two natural transformations "pure : 1_C -> T" and "join : T^2 -> T", satisfying three coherence laws that basically say "the Kleisli construction yields a category". Of course, explaining monads in terms of "bind" instead of "join" is bound (pun not intended) to result in a huge amount of fail.

> [1] (Though this is mostly because most people trying either don't have the required humbleness to admit they're a hotfix to a core failing of Haskell, or don't dare explain it in those terms.)

It is not a hotfix. It is a feature. Haskell's segregation of effects makes it possible to reason about effects in a compositional manner, using equational reasoning.
Linux distros have to do that sort of documentation as there is no standard. There is only really one freebsd distro. Also the change rate is lower.
Cause of aging reversed in mice: Human trials may start next year
On my machines, the 'Spotify' launcher in the app menu is actually a shell script that first pkills the running-but-hung spotify-desktop process...

For me it usually takes two or three attempts for it to realise that it is online ( 'Discover is not available offline' ) and then occasionally it ceases to respond to UI input but keeps playing music.

Another favourite is to load a band's page with their name but no tracks.

But I keep paying them because when the service works it is excellent. It's just infuriating that it takes 10 minutes from making a decision to actually playing music, due to their buggy app.
Consumer app data privacy concerns are fueling the workplace BYOD phenomenon
FreeBSD is a 'distribution' and Linux is a 'kernel', which in the context you're discussing is an important distinction. Pick a same-level entity to compare - Fedora? Ubuntu? Arch? Not saying that the documentation is as good, just that the question is apples vs oranges.
Data Scientists: What tooling do you need? We're building.
Please Comment with your Wishlist!
"Java or C++" is such type of key phrase/statement, but there are other ones, depends on job profile you are looking for. Front end devs should rather avoid job offers, which mention some particular javascript library as an must have requirement.

Question is simple: I don't have a lot of professional experience in required language/technology, but (here goes something interesting about you), should I apply to your job offer?
Perhaps you're being down-voted because this thread has drifted off-topic.

Sorry, this subject matter has been discussed and debated at great length in a dozen places. No one has the time to hand-hold each and every person who learns about it and freaks out, especially if they come off as demanding and abrasive rather than inquisitive and helpful.

Saying that it is considered a non-issue would be a misrepresentation. It exists as part of a large collection of things which are potentially concerning but which are not currently problematic. Your proposed urgent deployment of "fixes" carries enormous risk and so it absolutely will not be done. So far as I've seen none of the proposed "fixes" are compromise free and many carry new, subtle, and difficult to analyze risks which may have far greater practical implications than the problem they claim to solve.

From a more practical perspective, action has been taken to improve network connectivity so that achieving alpha much greater than zero should be impossible in practice, and do the extent thats successful then there is only an issue with >33% consolidations— which are already problematic for other reasons (e.g. they can reverse six confirms with a 20% success rate).

Your specific concerns seemed to be mostly related to mining pools engaging in this activity without the consent of their hashers, this particular threat is eliminated completely by hashers that use GBT and submit blocks themselves— as you were pointed to.

In any case, in the future when you find yourself sending demands to volunteer developers asking them when they will solve your pet concern you should first ask yourself when _you_ plan on solving it.
NBA broadcasters sometimes describe a play using phrases like "his patented turn-around jump-shot". Imagine if you really could patent such a thing? The YogaGlo patent seems to be in the same vein.
That's sort of an inverse Gresham's Law [1] scenario

[1] http://en.wikipedia.org/wiki/Gresham%27s_law
I think you're distinction is a semantic one. pavpanchekha could have easily framed his observation as Sir Doyle "creating" aspects of Watson's character.
Essentials of Docstrings
>business may never come to exist, which is clearly a net loss to society

That is not at all clear.
This reminds me of dual photography [1], in which you trade many projectors and one camera for one projector and many cameras using time reversal symmetry.

The video [2] gives a good explanation, and the revelation of the playing card is what strikes me as similar to revealing reflected hidden faces.

[1] http://graphics.stanford.edu/papers/dual_photography/

[2] https://www.youtube.com/watch?v=p5_tpq5ejFQ
> Monads are simple: ...

Ahahaha, please tell me that was meant to be comedy and that you're actually aware of the simple explanation. :D
Maybe so, but some programming languages have case insensitive keywords or identifiers, or take into account only the first several letters of a keyword or identifier. Distinctness is nuanced too.
Solo Founder, Bootstrapping to $7 Million in India
I like how it comes out when there is writing in the margins or the in the magazine example, but for a pure textblock it just seems to be a huge amount of wasted space at the bottom of the page and even on the sides.
AWS GovCloud
> He's trying to make the point that we don't know what caused PayPal's application to speed-up and Node.js may not be the root cause at all. The cheese analogy is not correct since he's claiming their benchmark is like the orange color - a false proxy for what you really want: good tasting cheese.

I think you've misunderstood the analogy.

He's claiming that without knowledge of the prior state of their systems and the differences (besides implementation language) between the Node.js and earlier implementation that underlies the benchmark, "using Node.js" may be analogous to the orange color in the cheese -- something that came along with the cause of the improvement that is not actually the source of the improvement -- and that splashing Node.js on other applications (as in PayPal's stated decision based on the result of this upgrade to use Node.js on all future consumer-facing applications, but more importantly other people using PayPal's experience to justify using Node.js for their applications) may be analogous to dyeing the cheese.

> They had a measurable increase in success - they made better cheese.

Right. He's saying that "PayPal made a faster web app. They used Node.js. Therefore, we should use Node.js if we want our web apps to go faster" may be analogous to "Farmer Bob's cheese is better tasting. His cheese is orange. Therefore we should buy orange cheese if we want better tasting."

Though, really, like most uses of colorful analogies to get points across in technical articles it does a lot more to obscure the point than to illustrate it.

The TL,DR: You are taking a significant risk of serious error when you accept a claim that a change that preceded an effect caused that effect when you don't know what other changes occurred at the same time that may be relevant to the effect under consideration.
Let me say that I think we largely agree, and that I'm deeply sympathetic to your immune system analogy. The US over-reacted, badly, and many, many innocent people were killed because of that. And arguably we are all less safe now, precisely because of that over-reaction.

I have been extremely critical of that reaction in the past, along much of the same lines you state. I haven't changed my mind on that, but I have also come to realise that it's actually really hard to calibrate risk in this situation - in the case of car accidents or lightning strikes, say, we can forecast expected outcomes very accurately, and the variance of those outcomes is relatively low. The threat model for an intelligent opponent is very different - history is a poor guide and the variance of potential outcomes is very high.
One way is to go back to the old US system, whereby you had to actively renew copyrights, and it costs enough that only active authors or publishers will do so. In reality, it was pretty messy, and there's a lot of arguing about whether a magazine copyright that wasn't renewed causes a story published in multiple places to have a lapsed copyright, etc etc.

It was also extremely painful to search for renewals until all of the renewal records were digitized by the Project Gutenberg Distributed Proofreaders. Now it's just moderately painful, because you have to be alert for variations in titles and author names.
Very cool! In this case, since the injected text will end in a newline, that approach will work (and it appears to work with r"""triple-quoted\'s"""

But I do see syntax errors if the bare slash is at the end:

>>> r'slash at end\'
File "<stdin>", line 1
r'slash at end\'
^
SyntaxError: EOL while scanning string literal
> The point is speed is a false proxy for the quality of Node.js.

Well, no, speed is the actual measure of interest. The point is that reimplementations that change language also often change other design features, and that without knowing what else changed one cannot validate the attribution of the post-change speed improvement to Node.js.
As other commenters have mentioned, Pandoc[1] is an incredibly useful tool for converting documents between formats. I do not, however, think that its usefulness in a solution to your specific problem has been framed clearly enough. It uses a version of the markdown syntax which is slightly-modified to ease writing of lengthier or academic documents. For example, a citation to a BibTeX bibiliography (usually performed in LaTeX by typing `\cite{McElroy-2000}`) is written `@McElroy-2000`, headers can be tagged to simplify internal references, and actual LaTeX commands can be called if you need them. Since the changes from standard markdown are minimal, you can write using any of the many markdown editors which are available.

As to my particular setup, I write Pandoc markdown in Vim using a plugin which I wrote for that purpose.[2] Nothing fancy, mind you, just light syntax highlighting, some keyboard shortcuts for (1) exporting to html or pdf (via-LaTeX) and (2) jumping between headers, and document folding, the latter of which is especially useful for outlining and organizing lengthy documents.

[1]: http://johnmacfarlane.net/pandoc/

[2]: https://github.com/shushcat/minimd
But who wants to scroll through hundreds of 'playlists' when you just want to know what albums you like. Coming from GMusic, this is one thing I miss...the separation of albums and playists.

I feel OPs pain, which is why I'm slowly working on a project that would make Spotify more useful for how I listen to music: better search, more detailed song / album / artist info...granted it'll just be a web app but it can be a real chore sometimes to use the mobile app for searching and browsing (see just about any Classical or Jazz for an example).
No, the whole point was the distinction between "discovering" and "inventing", a distinction which would not exist if "discovering" was replaced with "creating".
iOS Defeats Android in Battle of Christmas Day Shopping
Brain-washing at its best.

It's like they don't realize how silly and contradictory the argument for privacy is. Defending privacy by fighting secrecy? Come on.

In 20 years, people will look back at this and realize how blind they were.

Sheeps be clappin'.
The idea of web workers as a solution for performance problem is dangerous for the web. I have 4C CPU, 6 threads max, 15 pages open in tabs, imagine each of them opening 4 web workers, because one CPU core for modern website is just not enough! madness !
Our backgrounds and experiences may well be very different, leading to starkly different opinions - but, well... that's programming!

Though I don't know Haskell, ML, or Rust, I do know Java, Clojure, C++, and a few other languages quite well.

In a nutshell, I like type-checking and smart-pointers, and module systems and such. They often save me lots of trouble! But not all the time. Sometimes, these features get in the way - either to making the code more flexible, or to making the code more readable. (casts dirty look at Java)

But at the end of the day, no matter how precisely one can communicate to the compiler, and no matter how good one's compiler is at detecting (or even correcting) inconsistency, flawed logic, corner-cases, over-specificity and under-specificity (or the reverse of genericity, take your pick)... We puny-brained humans still manage to screw things up. The compiler can't read the spec, never mind actually cognitively understand the problem trying to be solved... so it's up to us to attempt to translate.

And fill in the inevitable gaps.

And attempt to anticipate future needs.

And finish on-time.

With our pitiful, buggy, meat-based processing organs.

Sure, "readability", "maintainability", and "understandability" are all pretty subjective, but that's part of the point. With the languages I've used, I find that sometimes the "safety mechanisms" get in the way. Working around them with "design patterns" tends to add code that might not otherwise be necessary. And might contain more bugs. I'm sure I'm missing something life-changing by not knowing Haskell or ML, but more important to me is that the code I write be, well... "readable", "maintainable", and "understandable" by whomever might be working on it (fixing, extending, whatever) next!

'Cause experience has shown me that bugs happen. And I want finding and fixing them to hurt as little as possible - whether it be me or some other poor fool.

Oh... also, I couldn't help but have a snarky response to your last remark: (no offense intended :)

> I see writing buggy code as negative productivity. So a language that gives you the illusion that you are writing correct code, when you in fact are not, actually makes you less productive.

FTFY: I see writing buggy code as inevitable. So a language that gives you the illusion that you are writing correct code, (by sucessfully compiling) when you in fact are not, actually makes you less productive.
Dewees?
Interesting list. Isn't some of the advice outdated? I recall an older story about al Qaeda's drone-avoidance manual, and how some of the advice given isn't as helpful, or can make you more of a target.
While these are examples of great software in terms of functionality, they don't necessarily contain 'good code'.

I suspect that the quality of the product is strongly related to the quality of the code underlying it, but then it could be argued that Windows is a good product, and yet I've read several stories about the code not being particularly good quality in many areas. Conversely, much open source software I've seen has wonderful code, but the products of that are horrible.
Hmmm norton can not, but PF & SNORT can ;)

Seriously 'security' and 'Microsoft' do not play well in the same sentence.
Out of curiosity, what did you use to prototype the interaction?
Zuckerberg was a developer, who was trying to make it big by using ideas and theory that he was hired to implement; He understood that the requiring of a university email address curated for people of a certain demographic.

There's usually a misconception between size and importance as well.
Whilst it is simple, it's important to note that the curating of an album is an important creative output of a band/group/artist, the other being the actual tracks.

What I really want from Spotify (or any other music service) is the ability to have a playlist of albums, not a play list of tracks. Spotify has no concept of an album as a single entity, so I end up using the service in spite of this. This might be down to how I listen to music, but I'd guess that my album-centric view of music isn't particularly unique.
Twitter is now worth almost as much as Yahoo
The universities are top heavy with "Associate Vice Provost of Faculty Diversity" and other such bullshit admin pukes pulling down $300K per year for made up jobs, while the actual teaching is done by adjuncts who get literally raped by the universities who pay them a couple thousand dollars a course and cobble together a handful of courses to teach to break into the five figure salary range without health insurance or benefits. It's a travesty.
The cynic in me wants to rush out and find a way/source to grab a copy, before they find a way to lock it up, again. (The other benefit of Mickey Mouse legislation: Yanking materials back out of the public domain.)
The choice here is between something tangible i.e. million dollars or skills to get a million dollars i.e. a promise which may or may not be fulfilled at some time in future. A bird in hand is worth two in the bush.
Might be off topic, but I have always wondered where do these public domain university emails come from? Was E-mail a public forum back then?
It's what technology is leveraged for that determines the value of something. Planes were used by individuals to crash into a building. What lead to that hate existing? Could technology have been used proactively and prevented it- and in a non-violent, kind way?
Then there are what seems to be the standard-issue security cameras, where it's hard to even tell what the main subject is wearing.
Federal judge rules NSA phone surveillance legal
"Because without all the data points, the government cannot be certain it is connecting the pertinent ones,” said Pauley.
I'm not sure about that minimum, but I do know noise (dark current signal non-uniformity for those in the know) increases considerably with temperature. So yes it matters.
http://intercoolerjs.org/

Please help, if you are interested.
I think we're saying the same thing :)
Totally. For all my real life friends I am beyond comparison when it comes to computers. Reading people's comments around here or on SO makes me think I know nothing...
Military are not criminally underpaid. When you factor in housing benefits, pension, health care, education, etc, the military is a fantastic career option, which is why so many people join it. For a non-college graduate, it is absolutely the best career path you can take in the US.

When you get out, you have access to federally subsidized loans that nobody else gets, as well as the ability to have Tricare (ultra cheap health insurance) for the rest of your life. When you consider that less than 10% of active duty military will ever see combat, this is a bargain.
There's a great classical example of this in the Book of Jonah:

4 Then the Lord sent a great wind on the sea, and such a violent storm arose that the ship threatened to break up.
5 All the sailors were afraid and each cried out to his own god. And they threw the cargo into the sea to lighten the ship.
But Jonah had gone below deck, where he lay down and fell into a deep sleep.
6 The captain went to him and said, “How can you sleep? Get up and call on your god! Maybe he will take notice of us so that we will not perish.”
Investors want the big ideas, though they don't want to pay for them. Tesla Motors and SpaceX would have never of started if Elon Musk didn't have money from PayPal being sold. This is why unless you know you'll have the funds to work on the big ideas yourself, it could be time and energy invested that will leave you not benefitting from it. Really it comes down to learning to enjoy what you're doing in the moment, and be working towards something bigger. It helps knowing what that bigger thing is, though I imagine not always necessary.
> Is there a sensible way to extend copyright on "active" IP that is still being used in new content, while allowing copyright to expire on "dormant" IP that has been left untouched for years?

Periodic -- say, every 7 years -- renewals with exponentially increasing costs to renew.
India's tit-for-tat forces US ambassador Nancy Powell to call off vacation?
What to expect from mobile networks in 2014: The 4G car, LTE...
Rework by 37Signals ^ is good.

Personal favorite are:

1) As a Man Thinketh by James Allen

2) Outliers by Malcolm Gladwell

3) 2nd half of Steve Jobs Bio

4) Maximum Achievement by Brian Tracy

5) The Big Short by Michael Lewis

6) The Four Steps to the Epiphany by Steve Blank
I'm in favor of IP laws, including copyright, but with the idea of creating incentives for people to create. Putting Sherlock Holmes in the public domain is probably not going to have much effect on Arthur Conan-Doyle's writing output, though, so it's probably a good thing at this point.
You're not an artist until an artist calls you an artist.
Hope this saves someone some time.
I wrote a chess playing service to teach myself app engine a while back, and I wanted to verify valid moves on the client before sending them to the server, as well as verify them on server.

I didn't want to write that logic in both javascript (for client) and python / go (for server) and create a suite of tests to attempt to verify that the server and client logic was equivalent.

I looked around for ways to either run (minimal) python functions in javascript or else run (minimal) javascript functions in python, but at the time didn't come up with anything workable (within the constraints of using GAE).

* no classes, objects, function attributes, prototypes, etc etc necessary, just chess move validity checking
Python 2.7, Scikit-learn, a few gb of ram, and a nice gpu.
I think NSA is a red herring here -- it may gave turned up the volume, but these are problems that exist no matter what.

If you are handling any data of significant value, storing it outside of the regulatory jurisdiction of your company and/or customers will increase risk and cost. Compliance requirements have already made it impossible for EU individual customer information to be stored in the US. Vice versa compliance has made it difficult for most healthcare or local US government data in Europe.
This was interesting to read. I have done this all my life and wondered why. It only happens after major events for me, but I'm out like a light for hours usually. I'll feel like I haven't slept in days.
I'm having trouble parsing your comment... I read your last sentence in one of two ways: 1) it is sarcastic and you are pointing out that we can move past terrible tragedies, in which case, that's the same point I was making, so I don't really understand the first sentence, or 2) you really can't believe we're trade partners with Japan because of Pearl Harbor, in which case we just actually disagree.
Watch people out in public sometime. Probably over half of them are absorbed in something on their smartphone. We're constantly processing information now. It's a huge change, and I'm not convinced it's for the better.

When we just had dumb-phones, we were "always available", but now we're "always connected".
I've been itching to play Red Storm Rising sometime again to see how it holds up. Or perhaps one of those microprose tank sims.
It's multiboot, so you can just boot it from grub.efi. See sheet 10, xv6/entry.S.

The more annoying thing is likely to be that it's 32-bit only. Are there any common machines that do x86-32 UEFI boot? Alternatively, does a 64-bit grub.efi know how to exit long mode and go into protected mode, to multiboot a 32-bit kernel?

(I was actually talking the other day with some folks about whether a 6.828 project involving a UEFI port of JOS, the other teaching OS, would make sense, but the 64-bit thing seemed to make it less interesting unless you also plan to do a 64-bit port of JOS. Which has been done before in a final project, admittedly...)