skysight-inc/HackerNews huggingface dataset:
This is an amazing story - and pretty much my worst nightmare. Not necessarily cancer itself, but the feeling and anxiety that you're not being treated and taken care of properly and that someone might be missing something. That doctors are (rightfully) unable to pay proper attention to everyone and everything just due to the sheer number of patients they must see. I know I'm prone to hypochondria, and it doesn't help to read things like this.

I can't wait for a world where we can constantly monitor the body easily, and abnormalities can be detected quickly and unequivocally, and even have software that can aid doctors in diagnosing.

I've read articles where doctors approach such ideas with skepticism, saying that more data isn't necessarily better, which surprises me very much. How can you look at two data points on a curve and guess what the curve looks like?

Anyone else feel similarly?

----

edit: I see false positives and the cost of dealing with them brought up often in the replies - I think this is an issue exactly /because/ we suck so much at diagnosis.

The argument that what you see may be wrong, therefore you must close your eyes just blows my mind. So you'd rather base timely detection of true positives on random chance?

Maybe if we saw these false positives much more often then we could observe the false positives properly and know how to identify them and improve diagnostics. Or maybe we'd be able to know better when intervening would be more harmful than not intervening. That an intervention would be harmful should not affect the choice to monitor.

And then there is also the issue of the diagnosis itself being potentially harmful (full-body CTs etc) which is equally terrifying and even more conflicting. We can also improve there too.

In any case, this was supposed to be more about the nondiagnosis anxiety, but I'm not unhappy with where this discussion went.
I wish I could have a foreignkey within that json.
I don't think this is anti-competitive at all ! I think that they are competing really hard! The Saudis can open the taps at any time (for the next 20 years) they are just reminding everyone (especially the banks and equity markets) of this fact and ensuring that it is part of everyone's calculations in the future.
The author hit the nail on the head for me: "The biggest problem for many front-enders seems to be that Angular forces you to work in one specific way."

I'm opposed to opinionated frameworks. which is why I don't use Rails. And why with Python I use pyramid/flask instead of django.

And with JS/node, I've found the commonJS+modules approach a far better means to structure my code than any monolithic framework.
Android Unit Testing Part I: What Makes Strong Test Automation
Restating your points:

1. Don't be poor

2. Don't be busy

3. Be able to have a time machine to undo previous mistakes.

Problem solved with snark.
I don't know, it still feels alien to get a response from the server w/ an incomplete page and then wait for it to be completely rendered. https://groups.google.com is s a good example of this.
I'm curious - what don't you like about $http?
I don't think I agree. It's quite possible to make a single-page application with server-side rendering. Just create API endpoints on the server for rendering partials, and then the client-side router/controller need only be capable of replacing pre-rendered sections of pages with new ones. If these partials are caching-friendly, then you save a lot processing both front- and back-end. Sure, rendered partials might be more expensive over the wire than JSON, but that's pretty negligible.
If you look closer at them you'll notice most of those rants are "feels wrong" type rants that could be levied at almost any framework the author doesn't particularly like. The only solid complaint he has is a performance test which, again, both Angular and Ember perform poorly on, and in the same breath he admits these issues are easily mitigated but laments that they aren't mitigated by default. He uses it as an opportunity to praise Backbone which further fits his "large frameworks are bad" premise which is what the article should have been titled. But hey, based on how quickly this article shot to the top of Hacker News it appears his more link-baity title was effective.
I Almost Let My Failed Startup Destroy Me
Well this is disappointing.

I wonder if they extended the study to include Markdown would that tilt the balance somewhat. The overhead associated with LaTeX might come from the fact that there's a compile cycle to get the formatting right, although they mention Kile as an editor so that's not clear.

Markdown also has fewer features---therefore a smaller learning curve than LaTeX)---and as a frequent user of Word (and lowriter), I know I interact directly with fewer features of the wysiwyg editors, given that many features are implicit or default, whereas I must manually invoke all features that I use in a LaTeX document (those I haven't placed in a .sty file anyway).
There's usually two three-person crews on the station at any given time, so two capsules are kept docked and ready to serve as lifeboats.

Since the Soyuz is the sole means of transportation to and from the station, they simply put the capsules into a rotation. When a new crew arrives, they leave their capsule docked and the departing crew rides the oldest capsule back to Earth.
IBM invented rendering on the client in the 3270 terminal... In 1971.
Of course you would.

Of course you are. I'm sure you don't believe there are any social issues that cannot be solved with the healing power of the holy market.

I don't understand your condescending attitude or why it's preferred by voters over a regular argument.

Especially when you believe that the issue is the cost of education. Auctioning off work permits would allow the country receiving immigrants to pay off the government which paid for their education.

You talk about social issues and then pick the one easiest to address with a market solution. This is the least problem here.
5 Insider Email Marketing Predictions for 2015
Trust me… Agile just won’t work here…
When Einstein met H.G. Wells
Yunus Bülbül- En mutlu günümde
Now that browsers are starting to be compatible, lets make js on the server incompatible...
How Sampling Costs Impact the Design of Social Systems
Show HN: I Done These Then Gratitude
Regular expression resources
> I feel that Angular’s fundamental proposition blurs the line between front end and back end.

Sorry?

> Angular is aimed at large enterprise IT back-enders and managers who are confused by JavaScript’s insane proliferation of tools.

Wait, seriously?

> When AngularJS was first created, almost five years ago, it was not originally intended for developers.

When I started using Angular 3 years ago (ver 0.9) it was already mature enough for serious web development and better (better structured, better documented, better for large web apps) than a lot of other frameworks (like Backbone). Back then it was developed by three Czech guys, that Google employed in the meantime and funded their project.

> Enterprise IT managers also like the fact that Angular closely mirrors the preferences of their back-end developers.

This just pisses me off already.

> Many front-enders, on the other hand, who have worked with JavaScript and browsers for years and have developed their own coding style, tend to have their doubts about Angular.

Yes, because their old code used to be utterly crap compared to something written in Angular. Angular does not let you write such messy code as you could without a framework.

This article is all FUD. I have never imagined that I'll ever see such a bad piece written about Angular.
No that is relatively easy to circumvent by creating the keys offline. The cold storage key never needs to get in contact with the internet.
Robots in 2015 (2011)
Why do people care about the arbitrary names used to classify custom solutions?
Frameworks tend to be more tightly coupled than libraries. They impose more opinion onto your code and make it harder to achieve modularity. They also tend to show up in languages which lack critical features for achieving proper modularity.
loosely defined, frameworks call your code

You're interpreting the poster by pulling the definition past the breaking point of any utility to this conversation.

Either air your grievances with the word "framework", or try and read what the author meant.
Toy Story 3D Animation Zoetrope [video]
Interesting article, glad the operation was successful.

The most interesting part of the article is not the advance in technology (nothing new, we've been using 3d prints as models for complicated fractures / bone tumours or even custom prostheses for years (academic centre)) but the low use rate of this technology by most hospitals.

The trick with overlaying follow-up scans is called image fusion and is easy and can be done by one-click applications (for example http://www.blackfordanalysis.com/) but outside of lung noduli i know of little clinical use. I've seen these types of mistake made before and trying to introduce it locally. Image fusion is also an awesome surgical procedure analysis tool (both for research and clinical applications), complimentary to the standard PA examination.

The patient education part is enormously helpful in practice. Cost per patient is however still high quite high for large models. For example a cardiac tumor model was printed with transparent plastic for around 500e. Our bone models luckily are a lot cheaper (non-clear plastic). When the price comes down i hope acceptance will improve.
The space station would stay in orbit quite a long time without being boosted, that only happens once in several months.

Based on past experiences, it's possible to salvage even badly damaged space stations. This has been done before in the US Skylab program and the Soviet Salyut and Mir programs, although never in the same scale as the ISS.

Skylab had problems with solar panels and heat shielding which was fixed by spreading a huge blanket of reflective material.

In one of the Salyut programs, there was a loss of power which caused the station to freeze over. It was eventually recovered by cosmonauts who entered the dead space station wearing gas masks, and slowly melted the water reservoirs and eventually recovered the station.

The Mir station suffered a bunch of problems, including an onboard fire and a collision with an incoming supply vessel. The station persisted despite all these issues as well as the fall of the Soviet union.

In the case of a serious accident on the ISS, some kind of contingency plan would certainly be improvised. The exact details would depend on the damage, but it would most certainly not be abandoned without serious attempts at fixing the issues.
This article could be right; I don't know the domain enough to say. And it did clarify for me why some people find Angular so contentious: different tribes. But at a number of points where I was expecting explanation, I got bare assertions.

For example, "These languages have their place in the web development stack — but on the server, not in the browser." Why's that? Personally, I'm looking forward to seeing languages that pay little attention to the divide, so that you can easily move code from one execution context to another as needed.

Or the already noted bit about client-side vs server-side rendering.

Or "Google aims to conquer the enterprise market, and Angular is one of its tools." Do they? I live in San Francisco and know a bunch of people who work at Google, and I have never heard the notion that they are aiming to own a lot of enterprise-developer mindshare. I'm certainly having trouble seeing how increased Angular usage leads to some billion-dollar revenue stream.

Or this, criticizing Angular's origin as a prototyping too: "I don’t think that a rapid-prototyping framework should be used for complex, enterprise-level production code." This from a guy whose favorite language was created for some light mouseover animation and form validation? You could say that Rails fits his description precisely, and it seems to be doing ok in the enterprise.

So I wish this had had more meat. As it is, it seems more like a dressed-up version of "Angular does not match my tastes," than the serious examination it wants to be.

Also, fussy language note: please nobody ever say "pulled straight from the horse's mouth". If you're going to use a metaphor, use it fully and well. Pulling something from a horse's mouth is going to be a disgusting and possibly dangerous operation. One hears something straight from the horse's mouth.
Go's compiler was entirely C until just recently... What does it matter? It's hard to write a compiler in a language that doesn't exist yet, and one you have the language, why bother with a rewrite?
This makes me doubt the reliability of cancer diagnosis:

>They were understandably terrified, but neurologists who read the radiology report seemed unconcerned, explaining that such masses were common among women, and suggested Scott have it checked again in a year.

Yet at the end of the article they say

>if she had waited six months, she would have had severe, and possibly permanent, degradation of her sight.
This should be posted once a year for review. It's incredible how many boneheaded decisions in Javascript's design are still with us. I used to hate JS for that reason. But you eventually internalize all of the pitfalls, and find out, possibly after reading the brilliant Javascript Allongé (http://leanpub.com/javascript-allonge), that the language has some brilliant aspects as well. It's abundantly clear at this point that we're stuck with it, so read your JavaScript Garden and make the best of it!
He could have replaced the Angular code with Ember code and levied the exact same complaints. Re-read the article and try to figure out which complaints aren't also valid for other large JS frameworks. It's clear he's a libraries > frameworks guy, which is a perfectly valid viewpoint to have, but it's cowardly to frame such a debate as a thoughtful criticism of a specific framework because it won't draw rebuttals from nearly as many people who might otherwise feel the need to chime in.
> A large contributing factor is the military industrial complex spewing out death tech at an absurd rate, and with nobody to blow up with it all it just goes to police forces at auction.

Sometimes not even sold, but given. There are government programs where police departments can ask for used military gear and get it at no cost (i.e. no impact to their budget). This makes the departments especially eager to acquire as much "death tech" as they can.

> So you end up with towns of a thousand having swat teams and tanks and you wonder why the culture shifts from protecting and serving to war, death, and extortion.

This makes me very sad. I was born in the 70s so I grew up during the coldest part of the cold war. We were taught in school that (sorry to Godwin) Nazi Germany was pure evil, Stalinist Russia was pure evil, Italy under Mussolini was pure evil, China under Mao was pure evil, and so on. Yet here we are becoming just as militarized on a local level as those regimes, giving our police forces nearly carte blanche to oppress the citizens at will. It's disgusting and disturbing, and I say that as a former law enforcement employee of 14 years.
I'm a huge fan of Fez, and picked up Monument Valley for Android. It was fun, but extremely easy and super short. I decided to pass on the DLC, figuring it'd be more of the same. Does Forgotten Shores step the game up to the next level? Worth buying?
Pivotal Podcast Episode #11: So What Happens When I Push an App Anyway?
Many Startup Cultures Cannot Match the Market Pace
It depends what you're developing. If you develop a product (startup) that will change the world, you spend a lot of time, you put your heart into this product, you should understand every line of code, so you develop a product not framework. If you create site by site every week or day for your clients, you need a framework.
I would buy gold as an insurance against an economic crisis. In an economic crisis, drastic measurements by the government seem likely.

For example recently in Greece the exact thing happened that people always worry about: home ownership was suddenly being heavily taxed, because those house owners have little way to hide their assets.

In general governments try to prevent the population from using alternative currencies (usually it is illegal). So if in an economic crisis gold would become too much of a live currency, countermeasures by the government seem very likely.
Well done! Just one thing I noticed, the speed is mph and the distance unit is meters. Would be nice to change speed to km/h.
If you are looking at a start-up trajectory, plan to take on additional money, etc, treat his money like a third party investment and value it separately from his role (and equity) as a co-founder. To properly do this, you'll have to come up with a reasonable valuation for your company. It should be somewhere between 100k and 200k if you are starting from zero.

If you are looking to bootstrap, then treat the money like a loan.
Deep Learning Tutorials
The world does not end at trade. There's a huge difference between a company from my country setting up a division somewhere else and people from another country moving into my neighbourhood.

You may be fine with either one, both, neither, and even some combination depending on the particular good or person. Conflating them is disingenuous.
I didn't see anything from the demo video that I can't already do in Gmail.
Unless of course you yourself have created the hardware, OS, and layer upon layer of userland software that you're going to rely upon, you really need to acknowledge that your code is 99% dependent upon frameworks.

On the contrary, if the only connection between my code and the kind of "framework" you're describing is the entry point, my code is 99% not dependent upon frameworks. I am free to structure the remainder however I wish and to incorporate libraries on my terms wherever reusing their code is helpful.

Even if those libraries might encapsulate some functionality that calls back to some OS API, they do so when I want to use that functionality, not when the OS requires me to make that API call. So for practical purposes I don't think your analogy between system/platform software and frameworks holds at all.
I suspect it is a matter of taste.

As for the pork thing, it is not just muslims. Strictly speaking christians should not touch it either as it is part of the old testament.

My personal take on this is that back then someone observed that people that ate pork often ended up sick and died.

While we now know that is is because of an illness passed from pig to human, back then it may well have been interpreted as divine punishment.

But then those days religion and law was one and the same, and so the declaration of pork as unclean may well be seen as a health and safety regulation.

Supposedly you can find passages from nearby cultures that line up very well with the old testament, with one crucial difference. While other cultures makes violations an offense against society, the bible makes them an offense against god. Meaning that what others deemed a social or secular matter, suddenly became religious.
I wouldn't be at all surprised if the loading problems with Google Groups are a legacy of Deja News code still floating about in there somewhere. There's no good reason why a single page app has to look horrible while it's loading data - a well written app should display a nice looking holding page that gracefully adds content as it's received over the wire.
I wonder if they might put it on a subdomain. Facebook is blocked at my company. That might make using Facebook@Work a little harder.
When you're working on large teams it's no longer your global namespace alone. I've worked on quite a few projects that abused the global namespace and it's very painful to try and recover from.
PPK - search for PPK JavaScript
Not sure how practical canned tuna would be - seems to me you would need a lot of storage?

In general I agree. Only storing guns seems even more difficult than gold. I live in a country where it is not a normal thing, and statistics seem to point out that gun ownership increases risk of being shot. But in a doomsday scenario, I suppose having a gun would be a good idea :-/
Personal attacks all the way because your pet golden hammer was attacked

Neither is Bitcoin my pet golden hammer (I don't even know that metaphor), nor is my statement a personal attack.

It's merely pointing out that your claim is so fundamentally wrong that you can't have a good understanding of the design.

If you don't want to learn the protocol then maybe think about it this way: Energy consumption is not an exponential factor in bitcoin simply because miners have to pay for their energy, too. And the number of miners does not grow exponentially.
I've done this. I've done Angular. I've done Ajax calls to templates on the client side. I've done Knockout.

Give me client side data binding (2 way!) any day of the week vs sending the partial back from the server side. You invariably end up with a bunch of shitty glue code that's dealing with the actions AND the display.

Using a framework (Angular, Ember, KO, Backbone) all allow you to separate this spaghetti nightmare into manageable chunks.
Exploring Rails' ObjectSpace
>Well go ahead and copy any paste any of the ones you are unsure of here and I'll reply.

I said "all of them", but who has time for that? Just take another statement of yours as an example:

>"2014 Was meant to be the year of Bitcoin" based on the claims of all the leading people in the bitcoin world outside of Gavin.[1]

"All" the leading figures in the Bitcoin world, except one, said 2014 would be the year of Bitcoin? Really?

I'm sure "some" of them said that, or some kind of bullish statement of that sort, but even if you'd claimed that, you'd still run into an argument about who are "the leading figures" anyway.

It's the way you frequently employ these sweeping generalizations and broad exaggerations to support your arguments that makes me more and more inclined to discount any statement you make.

Probably some of what you say is true. But basically you seem to spew out assertions without checking them. You have a terrible habit of stating your opinions as facts. I suspect you may even be twisting the facts to better support your claims, in the heat of an argument. So how can I trust you? I don't have time to sort out the truth from the half-truths and exaggerations.

[1]https://news.ycombinator.com/item?id=8884950
> That's good news from a bandwidth point of view, an environmental point of view, and, if you're clever about how you code it, a rendering speed point of view because you only have to replace the content in some DOM nodes rather than repainting the entire template.

It's just intuition on my part, but I think the environmentally friendly option is probably actually sending a couple extra packets (server-side rendering) vs cooking the CPUs of however many clients you have with JS (client-side rendering).

Also, never experienced an application where parsing a blob of JSON and manipulating the innerText and values of HTMLElements with JavaScript was more efficient than setting innerHTML.
US and EU politicians use Charlie Hebdo attack to call for more surveillance
It does, but it only points to the websites of FEC, SSA and Wikipedia, without really mentioning what data was used. That's barely more useful to me than "Source: Internet".
The as_slice situation was acknowledged to be deplorable, and is being vastly improved in the runup to 1.0.

As for speed, please file a performance bug! We love to know where we're missing out on optimizations.

https://github.com/rust-lang/rust/issues