skysight-inc/HackerNews huggingface dataset:
> I don't follow, why would SSA need to be translated into an input language?

Rust is a meta-language with very powerful macros in it.

What is a macro? Macro, essentially, is a compiler. You can have some petty macros implementing tiny syntax sugar on top of your language, that's totally fine, but that's not their purpose.

The real metaprogramming kicks in when you implement very high-level eDSLs on top of your macros. And for this sort of things, having a proper compilation pipeline is a must. Many eDSLs may end up being represented as an SSA. E.g., I'm doing this with a Packrat eDSL - it pays to represent its intermediate language as an SSA for doing some high level optimisations before spitting out the host language code.
It's interesting to read the Chinese social media reactions to the stock market crash. In the beginning it was mostly hopeful mixed with a bit of schadenfreude. Then it was resigned with a lot of morbid jokes.

Now, there is a degree of anger you didn't see before. There is even a streak of nationalism with some rumors claiming western forces are conspiring to bring down the Chinese market. Some social media posts are literally "buy stocks if you love our motherland."
I believe you can achieve that by adding custom filters like here http://angjobs.com/#!/jobs/inbox/hn
There's a middle ground though.

On my team, the long-standing rule is that you need to make a best effort to stick to the module's existing style. So we're not gonna bust your balls because you don't split at exactly 100 characters or whatever... but if you never wrap your lines and if you insist on indenting things completely differently than everyone else then yeah, you're creating a problem.

It also helps that our "style guide" is pretty minimal. Brace conventions, indentation, spaces before conditions, etc. Things that have a serious impact on readability and ease of debugging and that can easily be auto-formatted. What we don't specify is the higher order stuff -- provided you are internally consistent. We don't mind if API A uses one naming scheme and API B uses another, provided that we don't have a mix of different ones in the same API. Same for how something like object extension is handled. This falls into the realm of "we assume our developers will make the best technical choice", but so far it works.

There's always a complaint that specifying the braces, spacing, etc. is stupid, and if it required a lot of human intervention or was treated as a serious offense I'd agree. For us it doesn't, and it's not. The purpose is to limit the amount of visual friction when switching from one file to another. What the code is doing is the important part -- presentation should be as uniform as possible to limit distraction. Add in the fact that we've got an Eclipse profile with all the spacing, etc. setup the way that we do it, and it's pretty easy to keep things tidy.
> The programming editor Atom by Github is also a "traditional" desktop app with Node.js at the core.

Nope, Atom it's based on electron[0] itself which use io.js and Chromium as a core.

[0] https://github.com/atom/electron
I am not sure it can be called 'very lightweight'. The runtime itself has a large disk footprint, my node_modules is often 100s of MB, and the memory usage is quite heavy too (idle Ghost.org blog takes around ~100MB RSS).

Some of the APIs are not very portable either, such as fs.watch. Many npm libraries implicitly depend on Linux or OS X.

It's convenient though, sure.
Reddit has something like 3m active accounts and 150m unique visitors in a typical month. The Blackout2015 sub has 37k subscribers. Make no mistake: this and the fatpeoplehate protest are an absolute drop in the bucket in terms of Reddit's overall user base. It's only notable for how easy it is for a relatively small group to completely control the narrative on /r/all.

These people are trying to organize a blackout for July 10th-12th. I hope they do. You know what will happen? Reddit will return to normal. For two days no one will talk about Pao or Victoria and they'll realize literally no one cares about their protest.
In my experience[1] code is available maybe half of the time, if you really search for it: checking the academic and personal pages of every author, and scouring the code of every framework mentioned.
You're lucky when the code is in C or C++ using a framework nobody uses (e.g. MegaWave), but half of the time the code is in MATLAB. All uncommented, using single character variables and under some restrictive or just weird license.

And then it only works on grayscale images. Maybe because it's easier to get funding for medical images. Just applying the algorithm to each color channel separately leads to color fringing when they get out of sync.

Finally, usability, distribution, and performance are afterthoughts. I don't disagree but it makes a huge difference.

[1] https://github.com/victorvde/jpeg2png
I don't know how common my definition is among the CT community. Frustratingly, few researchers operationally define the term (cardinal sin in Education research!) and establish graded metrics based on it. I haven't met any other researchers who have resisted our definition, but there are other definitions. Repenning has one that is particularly... distinctive from my own:

http://www.cs.colorado.edu/~ralex/papers/PDF/SIGCSE10-repenn...
So on a tangent, does anybody have a nice article on numerical methods with Haskell? I've used Haskell for other things, but I've never endeavored to try doing any sort of heavy number crunching because it seemed a bit weird.

My standard test is implementing GMRES. I gave it some thought once and I couldn't come up with a non-awkward way to do it in Haskell. Mostly I get caught up on how to do the Arnoldi process as it requires lots of manipulation of submatrices. I couldn't ever seem to find a library that was nice for matrix manipulation. What do people mostly use? Also, what's the idiomatic way to do nitty-gritty matrix operations? Entrywise manipulation of a matrix doesn't seem very Haskell-ish to me, but it's not something you can really avoid in this application.
DM = ?
I'm not sure that grabbing yourself a slice of the hype-pie is necessarily a bad thing. Learning is good for the soul, right?

I do get your point, if you had one. It does feel like there's a must-have new shiny thing to prod every other day. However, React seems to be even shinier than others as of late -- I know this because I even read the documentation and played with the tutorial! I do admit that I can't really come to any solid conclusions about how shiny React realistically is because I'm not much of a sample size.

I do find the React docs to be excellent though which means I'm more likely to keep playing with it. Nothing turns me off faster than awful documentation.
If we aren't expected to write new, different, useful quality code that solves real problems, then there's no reason anyone should start programming in the first place.

Everyone needs to start somewhere and maybe for a complete beginner expectations are low, but if you're not veteran enough to solve real world problems then you are in no position to be giving advice like "code every day" on the internet.

The nice thing about solving real world problems is that you'll inherently learn something new, not just to you, but to humanity.

And lets be clear here: you didn't learn how to write a scanner/parser from scratch, at least not a good one. To do that you would have to read literature and/or look at production code. It's unlikely that you've figured out decades of parser research with your lexer/parser--it's much more likely you've just reproduced a bunch of mistakes that were made and solved in the 60s without even realizing they were mistakes. You could actually learn how to write a good lexer/parser by reading a handful of academic papers or reading through the code of, say, PLY or working with a parser toolkit that exposes its workings like Parsec.
For me the big win with 80 is that I can easily do a side-by-side diff in my IDE without needing to expand the diff window at the expense of the outline, package, and other views. And horizontal scrolling in a diff view sucks. A lot.
I tried to build an online community of youths interested in politics and failed for lack of people. (We did have a very narrow target group: German youths who were both interested in social matters and enjoyed writing. That probably killed us, since we didn't (yet) manage to spread our advertising net wide enough to attract enough people for a snowball effect.)

So I think you're first problem isn't going to be how to keep your community, but how to grow it. I'd like to hear what ideas others here have on that?
Said every developer who's never had to "just speed up" an application written with a framework that makes development/debugging easy, but has fundamental performance issues that cannot be overcome without a significant overhaul.
Absolutely disagree.

From the get, Paul is depicted as a petulant, unthoughtful child with no desire to move off-planet - which is the exact opposite of who he is in the books.

The fact that Paul is mature for his age is precisely why he takes the courses of action he does in the books.

David Lynch nailed that aspect.
America.create
Timecop.travel(1776, 7, 4) do

a = create(:america)

expect(a.people).to respond_to(:overwhelming_force).with(:patriotic_guerilla_warfare)

expect { a.subjugate! }.to_raise(UnconqueredException)

expect(a.independence_day).to eq a.awesome_bbq

end
Sounds great!

You mentioned to Akumma that "the pre-test before the trial project depends on the position. For Data Wranglers it is very different from the one you had."

So, given that you're hiring both data scientists and data engineers, do you give a different pre-test, depending on which role the candidate leans more towards?
Have you ever heard of "talk to the duck"? It's the idea that you're so close to a problem and tied up in the details that you haven't stepped back to see the whole picture and truly understand what's going on. Or alternatively, have you ever been struggling with a concept and someone comes along and says "oh, you're building a [design pattern]" and suddenly it all makes sense?

While I'm not sure I agree with the Tolkien assessment above, I understand the sentiment of being too close to one's work.
Holy "shiny new tech buzzword compliance" batman!
This is hipster dev certified!
To me, the tag box has incorrect UX. I would personally expect that hitting the spacebar would end one tag and let me enter a second tag, especially since it is clear that you do not permit spaces in tags. I would also expect the "enter" key to conduct the search. Instead, spacebar adds a space that will get converted to a hyphen anyway, and enter ends one tag and lets me create a second one.

Good job overall; I like the idea. It will be an interesting challenge to capture meaning from these raw text posts. For example, I tried to search for jobs in Florida, but typing in "FL" gives a lot of false positives. That will be the
“[A] quotation is a handy thing to have about, saving one the trouble of thinking for oneself, always a laborious business."
Lets say, theoretically, that a similar ruling were found for some of the Reddit moderators. Wouldn't it be in Reddit's best interest to immediately terminate their employment and find a way to bring in more cost-effective moderators?
It's usually a bit more specific than that. Something like "Disguising an unfounded or ludicrous belief as science by using the right vocabulary, just in nonsense ways."
The ACA was passed with zero republican votes - so it's hard to say their love for insurance companies is the reason it is the way it is.
Or to continue the train of thought, what about things that it did ship with that could have been excluded? :)

Personally I'm starting to dislike index operations since they can panic (and are the shortest way to access), and I rather use the explicit Option based APIs. Though I'm not too worried about those, since a lint disallowing them shouldn't be too hard.
2-4 times is a spectacular speed-up, of course the inner loop of an interpreter is important but you're implying the rest of the code-path is only 3-4 instructions long (otherwise you can't get that kind of speed-up) which I find hard to believe. Even the inner loop of an interpreter usually calls routines that are longer than the inner loop itself. Is there a particular benchmark you have in mind for that 2-4 number?
I just can't get over how shitty a human being Armstrong seems to be. When you offer health benefits to employees by self-insuring, paying for premature babies is just part of the obligation you took on. Complaining about it publicly is not only shameful and illegal, it's an admission that you're an asshole that doesn't want to hold up your end of business dealings.
So, basically, pull out the pocketbook and we'll hook up our vacuum to it.

Attempting to outscale a DDOS (the primary mitigation method presented by Amazon) is going to DDOS your bank account. Personally, I'd rather see some more recommendations along the lines of the "VPC can minimize potential attack surfaces".
I wonder, is 2 premature babies in one year in a 5,000 person company very unusual? Did their actuaries just do a horrible job? Or is that really a truly extraordinary event for a company their size?

Reminds me of when I balked at my home insurance company trying to bump my rates 20% one year- they said it was because of the 2011 Japan earthquake (I'm in Canada). I laughed and walked right out.
It's only a negative benchmark if you chose to perceive it that way. I think it's a valid data point, it doesn't say anything (that I perceive) negative...unless you're really worried about javascript performance of the framework versus relative to straight javascript.
Trolls defined internet culture.
Absolutely. All these attempts at reinventing email into a new instant messaging service are fundamentally flawed, even if they only intend to use email as bootstrapping. I /don't/ want enter to send the message -- I want enter to create a new line. I /don't/ want you to hide the reply field for noreply@ emails, because sometimes I use draft responses as short memos to a specific email.
The insurance companies lobbied heavily in favor of the ACA as written. After all, millions of people would now be required to buy their product and if the person couldn't afford it, the government would cover some portion of the gap.

The real bill - total liabilities - will be paid later by the next CEO/management but the current people got their bonuses.
Google trends data for Bitcoin points to German apathy
No love for Creatures of Light and Darkness?
Show HN: A Deep Learning Network “hallucinating”
> The eerie thing is that as far as we can tell, our brains are no more than models of consciousness, and yet they are conscious.

Wow. That is an extremely good description of the problem of consciousness. Is this your own formulation? If not, where did you run into it?
> “This is what we do in the US. We blame the sick people for being expensive, but the same sick people everywhere else – in the UK – they wouldn’t be causing excess costs to the system,” said Peel.

This line bugs me.

Regardless of who pays for medical care, the costs just don't disappear. With a bigger pool, they're spread across more people so the marginal costs might be lower but the total cost remains the same.
This is easily solved by an email service that makes creating aliases take 5 seconds, and offer a very large maximum number of aliases.

Address exhaustion is a real issue though, so you will need to acquire many email-worthy domains for this service.
NodeJs' non-blocking IO makes it a great choice for near real-time communication, like streaming editors, messaging, reacting to high freq events (like metrics). See: http://socket.io, http://en.m.wikipedia.org/wiki/Surespot and https://github.com/etsy/statsd

It is also great when you want to prototype a REST backend, and get it up and running in no time. The simplicity of javascript along with nodejs' module ecosystem make it a breeze (Ruby equivalent would be Sinatra).

What nodejs isn't good at is, parallelism. Concurrency is handled for you for free by the underlying libuv eventing framework. Pseudo-parallelism is achieved using 'clusters' but communication between node processes is costlier than in other languages that support parallelism out of the box.

Read https://news.ycombinator.com/item?id=4305486 for aphyr's excellent commentary on clojure vs nodejs (you can also find Ryan Dahl defending nodejs in a few cases there)
Best URL Shortener for Social Media Sharing
I stopped reading at:
"Moreover, shifting from evolutionary biology to quantum physics [...]"

https://xkcd.com/1240/
I read this and this that it's a lot closer to what RSS intends to solve, especially the read-only streams. Two-way streams is mainly providing a method to post back into that feed. It's a little more real time (rss feeds are typically cached and refreshed), and a real-time implementation would e more of an collection of entries that are pushed to the server presenting the stream and ultimately to the client.

What I think
With that in mind, I feel this concept is very close to a lot of the p2p or decentralized content distribution systems being tested out these days, like aether[1] or matrix.org[2].

The backend implementation that matrix.org uses is rather ideal. It's Federated JSON over HTTP(S). The clients out today are heavily focused on chat, but it is data agnostic. You could have client that writes rich media content and a client that displays this as a blog. Going back to the streams concept, you could have a client subscribed to multiple streams (rooms in matrix vernacular) and as people post their messages - rich media or simple "how are you" comments, it would get federated out to each home server, which can present a web client interface like in tonsky's mock-ups.

For the concept of amazon providing sensitive order information as a stream/matrix room, there would have to be an add-on concept built into the client of some sort of security token. I'm not talking about a losable gpg keypair, but something amazon generates and provides to you (like they do with their AWS services already) Amazon would then create a personalized stream for you, using that security token to encrypt. Since amazon provides the content and the key, they can replace your key at any time.

[1]: http://getaether.net/
[2]: http://www.matrix.org/
Well, I think the author's point is that the conventional hive mind wisdom in the community that uses this product has been that DOM manipulation causes performance problems and the framework is wicked fast and not a source of performance issues... which may lead naive or new developers to never both to consider it as a potential source of problems. This very clearly illustrates it may be possible that you shouldn't always disregard the framework as a potential source of problems...
Most classic sci-fi is deeply anti-liberal. Liberal utopian stuff like Star Trek is the exception. Dune is loaded with implicit acceptance of aristocracy and religion.
Node on desktop is still in early stage, there are some projects but node shines on server side, not only for web/http (mega simple), but also any other application protocols or lower. It's not hard to make socket and do whatever you want + async = win.

On the other hand it's javascript, so :-)
Some website a few years ago said that Lynch's Dune is great if you cut out all of the speaking parts. I'd like to see an edit like that.
I think under this context, a student asking about node’s uses, drawing the distinction between io and node isn’t really relevant, especially since there are plans to merge the two.[1] But thanks for the link, didn’t know about Electron, seems really cool.

http://www.infoq.com/news/2015/05/nodejs-iojs
Ditto. Information on topic-specific subreddits is really useful, and not always subject to rapid bitrot.

(Context: I'm a filmmaker. There's plenty of writing about filmmaking from 30+ years ago that's still very useful. And filmmaking is a comparatively tech-driven, fast-moving interest.)
I think most presidential candidates actually believe, that they are the best choice. As a programmer you know where you took shortcuts. I think I would not honestly rate any software I wrote to be perfect, because such software has not been made yet. On the App Store I would probably just lie and give it 5 stars anyway :)
“I live in a rather special world. I only know one person who voted for Nixon. Where they are I don’t know. They’re outside my ken. But sometimes when I’m in a theater I can feel them.” — Pauline Kael (this is what she actually said) http://www.vanityfair.com/culture/2012/10/The-Fraudulent-Fac...

This is why Nate Silver, who after all mostly does his work by taking polls as a whole seriously, continues to surprise some people: They live in a bubble. They don't see who the majority is actually supporting. They are actually surprised by election results, even if the polls have largely been pointing one direction consistently for months on end.

(Silver ignores some polls and applies correction factors to others. This is due to those polls' demonstrable idiocy and/or bias, as empirically demonstrated by how far they are from reality when the real events happen.)

Wang does pretty well, too, and his models are simpler: http://election.princeton.edu/

My point is, polls work, statistics is real, and numbers remain the primary way to determine which of two things is larger. Enter echo chambers if you want to, but don't live in one.
Ubuntu Snappy in Action – New Generation of Software Management in Linux
We’ve finally hit the breaking point for the original Internet
Alternative guide, use CloudFlare and hide origin address.

Most of AWS advices (like autoscaling) will help only a bit, but can cost a lot (lots of ec2 machines serving bogus requests).
So, the obvious question is this: why aren't we seeing a massive influx of Usenet users from Reddit right now? And why didn't everyone move to Usenet rather than Reddit after Digg fell apart?

There's clearly something, or somethings, that are preventing Usenet from being terribly useful at present for the "Reddit-like" use case.

(I used to be a heavy Usenet user back in the '90s. Haven't touched it in more than a decade, though.)
Health care is famous for being one of the primary examples where the structure of the "market" makes competition impossible.

Firstly, when you need healthcare, there is likely to be little warning, and it's a "care NOW or death" situation. Corporations feel that's exactly the time to ask for a million bucks for the "service" and people naturally feel like not paying for it.

I side with people.

The counterargument is essentially malthusian[1] : if we do that, eventually the whole economy will be healthcare (because evolution means the cases of the sick will become more and more expensive until the system fails).

The huge problem with malthusian arguments is simple. Since their invention in 1798, not a single person has died due to a malthusian cause. No state has been devastated because of the effect described.

The malthusian argument itself, however, can be argued to have killed more than 100 million people in the 20th century, and was used as justification for dozens of massacres, genocides and wars. I doubt it was ever the "real reason", but ...

So malthusianism, which is the main reason we can't just decide to guarantee healthcare for everybody, is a theoretical argument that (so far) has proven entirely wrong. Everytime we moved in the direction of a malthusian catastrophy we compensated effectively without disaster. But the theory itself has been used as the justification for a number of catastrophies. It is the poster child for the idea of "the cure is worse than the disease".

And you hear people advocating it directly too : privatising healthcare is much more expensive than just curing everybody (to the extent modern medicine can do so).

[1] https://en.wikipedia.org/wiki/Malthusianism