Exoplanets in Pictures - <AUTHOR> http://www.slate.com/articles/health_and_science/bad_astronomy/2012/11/exoplanet_pictures_astronomers_have_photos_of_alien_planets.html

<comment><AUTHOR> This is about a month old, and completely passed me by, though the oldest image is actually from 2004. Growing up, this is something I was told we would never, never see - planets are simply too small, too dim, and too far away. We were told we'll never really know if they're even there.

So now we have pictures. Perhaps some day, if telescopes can be positioned sufficiently far apart in the Solar System, we can build an array that could image nearby exoplanets in fine detail. As for signs of life - that may be more tricky than a visual inspection - unless we see the glow of cities...

<comment><USER2> Space missions to detect Earth-sized planets had been planned for the middle of this decade:

<http://sim.jpl.nasa.gov/index.cfm>

And higher-resolution interferometers to take images of such planets for later in the decade:

<http://exep.jpl.nasa.gov/TPF-I/tpf-I_index.cfm>

Both missions were cancelled a couple of years ago. It's a budget problem, not a fundamental technology problem.

<comment><USER3> It's both. Both SIM and especially TPF kept slipping farther behind schedule, more over budget, and with increasingly questionable capabilities. The fundamental problem is that NASA is averse to iterative and competitive development styles, which is absolutely necessary in this case.

As a case in point, look at the JWST, which will end up costing around $10 billion (more than 1,000% over budget) and over a decade behind schedule. The TPF is easily an order of magnitude more technologically challenging than JWST and would require putting 4x as much hardware into space. If it were managed the same way as JWST it would end up costing perhaps $100 billion and not launching until 2030 or later.

<comment><USER2> You have a point. I think SIM didn't have significant tech problems, but too much of its work became do-able from the ground during the interval when its problems were being solved. That's the reason it got a lower priority in the National Academy report that determines astrophysics mission priorities. And since SIM was a pathfinder for TPF...

<comment><USER3> A lot of it comes down to the way NASA is organized. Generally it's big budget missions with a single spacecraft as the culmination of the mission. Rather than ongoing development programs. Also, NASA has this tendency to want to skip technology generations even though the end result tends to take longer to deliver and cost more than it would have if they would have just explored the intermediate technology space to start with (see: JWST and VentureStar). While we're talking about JWST, that's another big part of the way things are at NASA these days, that program has eaten most of the unmanned NASA budget and put a significant crimp on space science missions. It'll probably be worth it, but the cost is pretty extreme at this point. Also on the topic of JWST, I remember back when they were planning to have a flight demonstrator (Nexus) in the form of a Hubble class Earth-orbiting telescope using some of the NGST/JWST technology. Such a mission probably would have brought the risk of the JWST program more under control but for whatever reason they ended up cancelling it.

TPF is another example of planning farther ahead than is fully justified. As the program advanced the design became less and less fixed rather than more and more refined. This is an indication that they were designing something that was beyond their expertise and needed more intermediate research to figure out, but with the budget crunch and the lack of vision nobody could come up with good enough ideas to do so. NASA set their sights on deep nulling interferometry and it sounded like a really cool technology that might be capable of doing what they needed, but more and more it seems like that may not have been the best technology choice, and it led to a far too expensive system to fund.

If instead of JWST and SIM and TPF NASA had instead hitched it's wagon to a more incremental development approach, of launching Hubble or Kepler class telescopes in the $1 billion budget range every 2 or 3 years or so and using that program as a test bed for new technologies and new scientific investigations I think we'd be in a much better state right now and probably a lot closer toward having the capability to directly image exoplanets routinely. But who knows if that would have been the case.

On the plus side, the impending drop in the costs of orbital launch due to SpaceX et al will probably force NASA into a model such as that, so maybe we'll see if it generates better results.</comment></comment></comment></comment></comment>


Is HN adding pop-up ads now? - <AUTHOR>

Seeing keywords double-underlined with a pop-up window on hover. Is this just me? Have I caught something or is Chrome responsible? <comment><USER2> I think you have malware. I don't see any ads (underlined or else)

<comment><AUTHOR> Actually some crap called Yontoo. Removed. Thanks.</comment></comment>


Why Eating Fat Doesn't Make You Fat: Sources - <AUTHOR> http://blog.massivehealth.com/post/16592941482/why-eating-fat-doesnt-make-you-fat-sources <comment><USER2> Carbohydrates are the most accessible source of energy for your body, but they aren't the only one. For those interested in the mechanics of how fat can be used as an energy source instead of carbohydrates I recommend looking up Ketosis.

It is a huge misconception that "the more fat you eat the more fat you get." Simply having excess energy intake (from any source) will gain you weight -- although the energy requirements for body maintenance is different for everybody. Having a deficit will lose you weight. Of course it is a little more complex than this, but generalising like this makes it simpler to understand and follow.

Personally I keep a moderately low carb diet (I eat most of my carbs before strenuous exercise) and eat high protein/fat.

\- <http://en.wikipedia.org/wiki/Ketosis>

\- Alternate infographic about drinking carbonated drinks: <http://imgur.com/w6C0s>

</comment><comment><USER3> Sand.

Interestingly, I was recently on a diet that (along with some basic points system that reflected glycemic index/load goals) utilized some innocuous looking pills... which had, as a main ingredient, silica.

These pills worked... when I ate them regularly, I ate less without effort. On reflection this makes sense... perhaps our overly-cleansed (and refined) diet lacks a very basic ingredient that our digestive tract had evolved to utilize (not unlike birds' gizzards) and is now lacking?

<comment><USER4> Wait... really? My instinctive reaction is that sand would not be good for your digestive system, but I guess I don't really know. Was (ahem) excretion an issue?

<comment><USER3> Can't remember, it was a couple of years ago. I don't remember anything extraordinarily different other than I didn't eat as much.

</comment></comment></comment><comment><USER5> This is the same thing UCSF Professor, Dr. Robert Lustig, says in his presentation, "Sugar: The Bitter Truth" (<http://www.youtube.com/watch?v=dBnniua6-oM>).

There is also a New York Times article on this entitled "Is Sugar Toxic?" ([http://www.nytimes.com/2011/04/17/magazine/mag-17Sugar-t.htm...](http://www.nytimes.com/2011/04/17/magazine/mag-17Sugar-t.html?pagewanted=all)).

<comment><USER6> > Is Sugar Toxic?

When an article is written in this form, the answer is nearly always "no", as it is in this case.

If sugar were toxic, nothing that eats fruit could survive.

<comment><USER7> According to that presentation sugar is toxic, but remember that the quantity matters, too. Alcohol is toxic as well, but a glass of wine won't kill anyone, whereas a barrel might put you in a coma.

</comment></comment></comment><comment><USER8> Whenever i read much of this anti-carb stuff, i'm always concerned about how different carbs affect the body. Taubes always blames the whole lot, but people like Lustig distinctly go after fructose. I get that carbohydrates probably affect the body in a negative light, but I certainly wish they would study sugars independently.

<comment><USER9> Lustig goes after fructose but points out that fructose and sugar are metabolically equivalent. I believe he does so because fructose is more prevalent in processed foods (cheaper, subsidized, and other policy-driven historical accidents behind this).

<comment><USER10> Slight correction: sucrose (table sugar) and fructose are not metabolically equivalent.

There's an enzyme in your duodenum which cleaves the sucrose molecule into one fructose and one glucose molecule semi-instantly. In both cases, your body ends up with a bunch of fructose. However, if you're eating table sugar, only half of the resulting calories are from fructose; the rest are from glucose.

<comment><USER9> "Fructose" in Lustig's case is HFCS. HFCS is (depending on the formulation) ~45% - 85% fructose, with the remainder being glucose, and a typical formulation being close enough to 50-50 that it's a wash. Sucrose is a bound molecule, HFCS is free fructose + glucose molecules.

So, while there are some differences (and I suspect there actually _are_ significant differences between HFCS and table sugar), for the most part, eating a lot of foods formulated with HFCS is very, very similar, metabolically, to eating a lot of foods formulated with table sugar.

</comment></comment></comment></comment><comment><USER11> Excellent to see this, it's a western myth that eating fat makes you fat. It's carbs.

Carbs are cheap, carbs are bad for you and carbs are often marketed as health food.

We don't need carbs. We evolved eating meat and veg. Meat, veg and water is the perfect diet. It's hard to stick to that diet though as carbs are so highly accessible.

<comment><USER12> Vegetables are mostly carbohydrates, so I don't know how you can say we should eat vegetables but not carbohydrates.

<comment><USER13> Refined carbs / refined sugar seem to be the problem with most foods these days. With the fear of 'fats' many food producers replaced the 'fat' with refined sugars to add the flavour with less fat (on paper).

\- [http://www.globalhealingcenter.com/sugar-problem/refined- sug...](http://www.globalhealingcenter.com/sugar-problem/refined-sugar-the- sweetest-poison-of-all)

\- [http://lowcarbdiets.about.com/od/nutrition/a/fructosedangers...](http://lowcarbdiets.about.com/od/nutrition/a/fructosedangers.htm)

<comment><USER14> "Sugar" isn't the problem. It's fructose. Hard on the liver, can't even be used by muscles.

<comment><USER15> That's only partially true, and would still be useless if it were totally true. When people say "sugar", they're referring to sucrose, which is half fructose. Even glucose on its own will spike your blood sugar, which will make it harder to burn fat.

<comment><USER12> Also, your body converts starch into glucose, so starch can spike your blood sugar the same way. Fiber makes your body absorb glucose more gradually, which is why it's important to eat starch and sugar as part of whole foods, rather than in refined form.

</comment></comment></comment></comment></comment></comment><comment><USER16> While Fat may not make you fat, all fats are not alike and some fats may be responsible for heart disease and cancer while others may actually be beneficial. This post by Kurt Harris does a good job of explaining why lumping together all fats is not a good idea: [http://www.archevore.com/panu- weblog/2011/1/29/there-is-no-s...](http://www.archevore.com/panu- weblog/2011/1/29/there-is-no-such-thing-as-a-macronutrient-part-i-fats.html) (PS: Unfortunately, he doesn't cite studies, but with some googling you can find most of the studies).

Obesity itself is a complex topic and blaming it all on carbohydrates seems too simplistic. Over at whole health source, Stephen Guyenet has written a series of articles on the current state of research on insulin resistance - [http://wholehealthsource.blogspot.com/2011/11/what-causes- in...](http://wholehealthsource.blogspot.com/2011/11/what-causes-insulin- resistance-part-i.html) Worth a read if you're interested in this topic.

</comment><comment><USER17> For those who have not seen it, I highly recommend the documentary "Fat Head (2009)". It covers a wide variety of these issues in great detail but in very entertaining way!

Here's a Youtube link to it: <http://www.youtube.com/watch?v=UVEiYwFvKvU>

</comment><comment><USER18> East Asians who eat two bowls of rice everyday must be the fattest people in the world then.

This article is so ridiculous.

<comment><USER19> It's a common misconception that there are few overweight east Asians: <http://www.hindawi.com/journals/jobes/2010/868573/tab1/>

Further, much of the population of east Asia lives in poverty or near-poverty conditions. Their portion sizes are small (i.e., total daily carbohydrate intake is nowhere even remotely close to that of developed nations). In fact, half a billion Chinese are living on less than $2 / day: [http://en.wikipedia.org/wiki/Poverty_in_the_Peoples_Republic...](http://en.wikipedia.org/wiki/Poverty_in_the_Peoples_Republic_of_China)

Also, east Asians eat whole grain brown rice, not the fried, bleached, processed, white rice that Americans typically eat, which is largely devoid of nutrients and fiber.

For far more detail, visit page 226 of Gary Taubes' 'Why we get fat' book.

</comment></comment><comment><USER20> _sigh_ yet another chapter in "X is bad for you! No, wait, X is good for you! it's actually Y that's bad for you. No wait, it's actually Z!"

After decades of this I've decided they're all full of shit until someone can come up with extraordinary evidence to the contrary.

<comment><USER21> I don't think there's been much change in this area, it's been "eat in moderation, eat a balanced diet and exercise" for as long as I can remember.

<comment><USER20> Yes, but what is "moderation"? What constitutes a "balanced diet"? They've been moving targets for as long as I can remember.

Meanwhile we've gone through endless cycles of "cholesterol is bad", "cholesterol is good", "only bad cholesterol is bad", "sugar is bad", "fat is bad", "fat is good, but saturated fat is bad", "carbs are bad". Eggs have gone through two complete revolutions of being bad for you and good for you. And now the new pariahs include white bread, white rice, and potatoes. Madness.

<comment><USER21> Here's the message I've been given, maybe it's changed without my noticing but I think it's remained consistent -

balance means giving each variable in an equation similar weight. Eating only one or two food groups is not optimal for health.

Moderation - not eating more calories than you burn throughout the day.

edit - I agree with you about the ever rotating axis of nutritional evil. It's BS. I think part of the reason we go through it though is people ignoring the basic advice I mentioned earlier that's held for so long. Why eat broccoli when I can eat McDonalds? Exercise is hard. ETC

<comment><USER20> It's not just that; it's the temporal nature of what constitutes a balanced diet (i.e. what the variables are, and what amounts are "correct"). Here's a short history of the USDA Food Pyramid, for example: [http://www.healthy- eating-politics.com/usda-food-pyramid.htm...](http://www.healthy-eating- politics.com/usda-food-pyramid.html) (note: this is from a site pushing the low-carb diet, and is suitably slanted in that direction, but is useful for illustrative purposes)

And that's just in the USA. Every country has their own ideas on what is "balanced".

</comment></comment></comment></comment></comment><comment><USER22> It's ridiculous to claim that you can eat as much protein and fat as you desire and not gain weight.

<comment><USER23> What's your evidence for this? I've definitely lost weight going on a low carbohydrate diet, and I ate as much protein and fat as I wanted. (I tried to keep the fats mostly "good fats".) Maybe if you don't eat any carbohydrates, you just don't end up wanting to eat as much.

<comment><USER24> Did you track caloric intake (accurately) on a daily basis? Do you have a base line estimate of how much you burn?

Eating as much as you want can be different things for different people. I know if you gave me a rib eye and eggs cooked in butter or eggs and bacon I could more than eat my fair share of calories burned for the day in that single sitting. No problem. I've done it, multiple times.

I found I got fatter on a too high fat diet. The amount of food, in quantity/volume, not calories, was less since fat has double the calories of carbs and proteins and I always could fit in more.

<comment><USER23> No I didn't track caloric intake. Why would I do that? One of the selling points of these low carb diets is that I wouldn't have to track such things -- that all I would have to do is not eat many carbs and that I would lose weight.

I'm certainly not claiming that this style of diet would work for everyone, but it certainly seems to work for many people. One thing I noticed is that when I wasn't eating carbs, that eating a rib eye with eggs and butter and bacon didn't seem nearly as appealing in large quantities as it otherwise would have. The diet did take away a lot of the pleasure of eating, which may be in part why it worked. I just ended up not being terribly excited by foods without carbs in them and consequently perhaps didn't over-eat. I would have killed for a saltine, though.

Another thing I noticed is that I wouldn't lose weight if I ate lots of nuts. It seems likely that the reason for this fact is that nuts are just too high in fat to eat in large quantities and continue to lose weight. But the diet warned against eating many nuts.

In any case, I think the point is not that you can eat _any_ amount of fat and protein and lose weight, but rather than you can eat as much as you will end up _wanting_. (With the exception of nuts.) And that you won't end up feeling hungry.

</comment></comment></comment></comment><comment><USER14> Technically, it is energetically easier to store dietary fat as adipose as opposed to carbohydrate.

The problem most people have is that they eat enough carb to satisfy their daily energy demands, and the fat they've eaten will be stored. Keep in mind that almost all muscle tissue and the brain prefer glucose (which usually comes from starch) over anything else, although some vital organs run mainly on fat, particularly at night.

Our digestive system is very efficient. The bottom line is this: if you eat more calories than you expend, you will gain weight.

<comment><USER25> The hidden assumption here is that your body puts forth the same amount of effort to store fats vs carbs. This isn't borne out by the evidence. Cells uptake nutrients in response to insulin. Your body produces insulin in much greater amounts in response to carbs vs fats. This is necessary: free floating glucose is toxic to certain organs. Fats on the other hand can exist in your bloodstream without any acute damage.

<comment><USER26> are you sure? [http://www.empowereddoctor.com/eating-fatty-foods- inflames-b...](http://www.empowereddoctor.com/eating-fatty-foods-inflames- blood-vessels-fat-cover)

<comment><USER25> Informative, thanks!

</comment></comment></comment></comment><comment><USER27> We've known fat isn't fattening for years.

Its nonsense.

</comment><comment><USER28> Insulin.</comment>


Check out preview for a new innovative data analysis tool in cloud - <AUTHOR> https://censusanalyzer.com <comment><USER2> I am a product manager of this tool, if you have questions or are interesting in working for us (we have offices in Cambridge, Munich, Saint-Petersburg and Moscow and can offer remote positions), just ask.

<comment><USER3> Can I connect a SQL data source? Btw, I am a happy user of another JetBrains product - DataGrip. Just wish DataGrip was online and shareable with my colleagues and had charting and graphing built-in..</comment></comment>


Back to the basics – Persevy - <AUTHOR> http://blog.persevy.com/back-to-the-basics/

<comment><USER2> Why you can't choose a username when signing up via Facebook/Google+ and why when you change your username, your profile URL does not update accordingly?!</comment>


Association of dairy intake with cardiovascular disease and mortality - <AUTHOR> https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(18)31812-9/fulltext <comment><USER2> Title should be changed to something like the interpretation section: "Dairy consumption was associated with lower risk of mortality and major cardiovascular disease events in a diverse multinational cohort."

The study does not, and does not purport to, show a causal relationship.

EDIT: It appears that the title here has been changed, but to the article title, which is a bit less than ideal since it implies a positive correlation when the study shows a negative correlation (or at least it reads that way to me).

<comment><USER3> The condition "diverse multinational cohort" is very important. The primary driver of population level variance in dairy consumption is lactose tolerance. For example Northern Europeans have much higher lactose tolerance than Aboriginal Australians.

So, we have to be really careful that dairy consumption isn't just proxying for ancestry. Because there are huge genetic variations in CVD mortality across different sub-populations. For example African-Americans have signficantly higher CVD, BP and diabetes risk because of higher rates of APOL1 polymorphism.

[1][https://jasn.asnjournals.org/content/26/2/247](https://jasn.asnjournals.org/content/26/2/247)

<comment><USER4> I suspect lactose intolerance in the US is inversely correlated with wealth -- so this could just be another study showing that wealthy folks live longer.

<comment><USER5> > actose intolerance in the US is inversely correlated with wealth

I'm not well informed about the causes of lactose intolerance. Is this correlation diet-induced/environmental? Or is it a congenital/racial thing where white people be rich and everyone else is genetically intolerant?

<comment><USER6> Lactose intolerance is the norm. Tolerance is unusual in adult mammals.

In humans, it appears to be a very recent mutation, probably associated with the domestication of livestock.

[https://en.wikipedia.org/wiki/Lactase_persistence](https://en.wikipedia.org/wiki/Lactase_persistence)

</comment></comment></comment></comment></comment><comment><USER7> lol. Everything food and health related comes full circle, doesn't it?

Never did like semi-skimmed milk or margarine, so I just kept on with full fat milk, butter and everything my whole life. Which occasionally has been difficult when in a shop with endless reduced and half fat choices...

<comment><USER8> It's funny to go to high end health food stores and see 0% carb, all fat and protein foods on the shelf next to 0% fat, all carb foods - both with labelling professing their health.

</comment></comment><comment><USER9> They mentioned funding. I looked on scihub. As far as I can tell it does _not_ have dairy industry funding. Instead it has unrestricted grants from some governments and pharmaceutical companies worldwide.

</comment><comment><USER10> FYI: [https://sci-hub.tw/10.1016/S0140-6736(18)31812-9](https://sci- hub.tw/10.1016/S0140-6736\(18\)31812-9)

</comment><comment><USER11> _" Dietary intakes of dairy products for 136 384 individuals were recorded using country-specific validated food frequency questionnaires."_

These questionnaires are not very good methodology. This is why you get so many contradicting dietary recommendations. Dietary studies tend to rely on them because they are the cheapest option. But they make okay headlines.

<comment><USER12> I think it depends on a type of question asked.

I think low fat or normal fat dairy preference is a pretty conscious choice and eventually is habitual.

Most people would be able to answer with good accuracy what type of dairy they prefer.

</comment></comment><comment><USER13> If you believe in keto, then it's the consumption of whole fats, not necessarily dairy, that "lowers risk of mortality."

You don't need to consume dairy to be on keto.

<comment><USER9> ....the people in the study were not on a ketogenic diet. Ketosis vs. non- ketosis is a big step change. The central premise of keto re: fat is "fats are good....because they lead to ketosis"

You're reasoning wildly outside of the study here.

<comment><USER14> Keto (and a lack of surprise) came to my mind when I read the title too, but your point is important for anyone learning about the ketogenic diet - keto is a binary state, you're either in it or you're not (and you can do a urine test at home to tell).

There are still benefits to cutting carbs without going full keto, but not because you'll be '50% keto' or anything, just because there are other health improvements from lowering carbohydrate intake other than possible ketosis.

<comment><USER15> Most of the longest living people eat a high (complex) carbohydrate diet. What benefit do you see in lowering carbohydrate intake, unless you're conflating e.g. processed white bread with sweet potatoes?

<comment><USER16> These are very short, low IQ populations though, and i'm not. (Kitavas,Tsimane,Okinawans which again they have one of the lowest IQ & Height levels per prefecture in Japan)

>What benefit do you see in lowering carbohydrate intake, unless you're conflating e.g. processed white bread with sweet potatoes?

Being able to control my weight, my appetite, much improved HbA1c, lower LDL/TG levels, increased energy levels, no more food cravings, and fasting as part of my daily life. whereas none of these was possible on my high Complex carbs years, and i'm not talking for white bread but whole grains, beans and legumes.

</comment></comment></comment></comment></comment><comment> open-source-ux The NHS website have a good summary and analysis of this study.

 _Moderate dairy consumption may help heart health_

[https://www.nhs.uk/news/food-and-diet/moderate-dairy- consump...](https://www.nhs.uk/news/food-and-diet/moderate-dairy-consumption- may-help-heart-health/)

From the intro:

>An international team of researchers looked at dairy consumption among more than 136,000 people in 21 countries worldwide.

>They found people who had more than 2 servings of dairy products a day were 16% less likely to die or have a heart attack or stroke during an average of 9 years of follow-up.

...

>Most of the benefit seemed to come from milk and yoghurt, and the effect was strongest in low and middle-income countries, where dairy consumption is generally much lower than the UK.

>The question of whether benefits come from low-fat or full-fat dairy products wasn't conclusively answered in the study.

</comment><comment><USER17> Interesting association: France is the single country with the highest saturated fat intake in Europe and the lowest rate of CHD deaths.

<comment><USER18> France has low obesity, too.

<comment><USER19> According to Wikipedia:

> the incidence of obesity in French women in 2014 was 24.0% and among French > men 23.8%. Overall adult obesity rates in France were significantly ahead of > the Netherlands at 19.8%, Germany at 20.1% and Italy at 21.0%, but behind > the United Kingdom and the United States at 28.1% and 33.7% respectively.

</comment></comment></comment><comment><USER20> One hypothesis I've heard is whole fat tends to be more satiating so you consume less overall.

<comment><USER21> Anecdotally accurate for me. I've tended to prefer higher fat foods - preferably things like olive oil and nuts, which helps keep my mindless consumption down.

<comment><USER14> +1. I feel like I consume less (a healthier amount) overall when I consume nuts, fruit and cheese as snacks versus high carb foods, even tho nuts and cheese are quite calorie dense. I just don't find myself feeling hungry again as quickly. I haven't been logging my food recently but I definitely _feel better_. Same with vegetables and meat vs, say, pasta.

</comment></comment></comment><comment><USER22> This fits in well with the data that cheese consumption is linked with death by getting tangled in bedsheets.

[https://www.tylervigen.com/spurious- correlations](https://www.tylervigen.com/spurious-correlations)

Sounds legit

<comment><USER23> Or that the divorce rate in Maine correlates with per capita consumption of margarine! (ibid)

<comment><USER22> Dairy is really bad for you.

</comment></comment></comment><comment><USER24> > Dairy consumption was associated with lower risk of mortality and major > cardiovascular disease events in a diverse multinational cohort

I am personally very pleased to read that, notwithstanding the need to not base anything on a single study.

</comment><comment><USER25> This summary only talks about the effects of dairy, rather than whole-fat dairy specifically. Does the article say more?

<comment><USER26> Yes, and interestingly, the effect is only statistically significant for the group whose dairy consumption was exclusively whole-fat dairy. The group with both whole-fat and low-fat dairy had lower incidence of the studied outcomes, but it wasn't statistically significant (and both groups were large: several tens of thousands of people).

</comment></comment><comment><USER27> Pass the butter, please.

</comment><comment><USER28> i can't see the funding unless i pay for it?

<comment><USER29> Try [https://sci-hub.tw](https://sci-hub.tw) or [https://gen.lib.rus.ec](https://gen.lib.rus.ec)

</comment></comment><comment> denton-scratch "Risk of mortality" is 100%, whatever you choose to eat.

<comment> yjftsjthsd-h Eh, just assume "per amount of time" and it works.</comment></comment>


How I built a fast JavaScript framework - <AUTHOR> https://medium.com/@marcisbee/how-i-built-super-fast-js-framework-faster-than-react-ea99f0d03150 <comment><USER2> I am often frustrated in this ecosystem by how people build things without any clear conceptual model, and then they document them by saying "it is so fast, it just works like magic". It is impossible to compare two approaches because there are no facts available to compare them on.

Like for this one from a peek at the source code it appears to try to parse JavaScript at runtime using regexes ([https://github.com/radi- js/radi/blob/master/src/index.js#L4](https://github.com/radi- js/radi/blob/master/src/index.js#L4)) which is great for demoware and not at all something I'd want to use in production, but that is not mentioned anywhere in the site or blog post.

I don't mean to just dump on this project in particular, which could just be a fun toy side project for the author, because this problem is endemic. (But then why go to all the effort to make all the marketing materials for it without actually writing any docs?)

<comment><USER3> Looks like the regex is only used to strip comments?

<comment><USER4> [https://github.com/radi- js/radi/blob/eace84e9b74c944b233f631...](https://github.com/radi- js/radi/blob/eace84e9b74c944b233f631de314a6869ed21f0f/src/index.js#L585)

It parses the source code of the view function at run time, matching parentheses, but ignoring whether those are present in strings or regexes. Likewise, the comment stripper will turn

        "/*whoops*/"

into the empty string...

In other words, the parser is buggy :-/

<comment><USER5> Having taken a closer look, it looks like the problems go even deeper than that: it rewrites `l()` calls in functions through a regex/replace on `fn.toString()`. This is similar to the mechanism that broke shorthand Angular.js DI in production. So code can break if it goes through some bundler than renames the `l` variable, or if a minifier does it, etc.

I'd imagine closures also break.

<comment><USER4> Closures will break, yes. It looks like it is intended to react to mutations to the properties of `this`...

I hadn't thought of minification, yes it pretty bad :-/...

It looks like the author is smart but has little JS experience (`var last = temp.splice(-1)[0]` where `temp.pop()` would do tells me that it may be one of his first JS project).

</comment></comment></comment></comment></comment><comment><USER6> They compared Radi to React Stack, not React Fiber. That's being sneaky.

If you run the React Fiber demo, you'll see it's just as fast: [https://claudiopro.github.io/react-fiber-vs-stack- demo/fiber...](https://claudiopro.github.io/react-fiber-vs-stack- demo/fiber.html)

</comment><comment><USER7> I'm not primarily a Javascript developer, but I seem to remember that attaching event listeners to Object fields and modifying the DOM in event handlers is how Javascript development was done 5-10 years ago. Am I missing something? Are we going full circle?

<comment><USER8> Yup. I find that most cases of "JavaScript fatigue" are really cases of "I want tools custom tailored to my use case, but don't want to do the legwork to figure out what they are".

The only thing wrong with jQuery is that it's perfectly fine until it isn't. Conversely, if you'll never need React's power you don't need it's complexity either.

<comment><USER9> React's (or other SPA frameworks like Vue's) complexity is much higher than it should have is probably because of the tooling (Babel, Webpack, NPM etc) and additional build process required even for a simple hello world app. That coupled with the rapid revision of the underlying ECMAScript standard and the race by developers and framework authors to adopt them causing further chaos.

Another issue was the rapid deprecation of age old JQuery plugins and the lack of equivalent plugins in the React landscape causing confusion whether you should build it yourself or not etc. I had hoped WebComponents somehow got standardized as the underlying architecture for SPAs, just so that the plugin/widgets wont get fragmented further, but it looks like it wont be happening anytime soon.

<comment><USER8> > React's (or other SPA frameworks like Vue's) complexity is much higher than > it should have is probably because of the tooling (Babel, Webpack, NPM etc) > and additional build process required even for a simple hello world app.

I wouldn't frame it as excess complexity, I would frame it as power. My problem is not writing simple hello world apps, it's writing and maintaining very large production applications with 5 other developers. Two years ago I took a week to really learn the tooling stack and it's paid dividends ever since.

<comment><USER10> We are 10 developers just using vanilla Javascript here. No mess, and a joy to work with. We use good old design patterns like observer, proxy, composite and so on. We also use inheritance and template literals a lot.

The key is good documentation, having an onboard plan for new developers, keeping things stupid simple and stop being bleeding edge. We want our code base to just work, so we can focus more on new features and less on maintenance.

I'm planning on writing a deeper blog post this year about why and how we feel is a good structured simple way to do frontend development. I believe there are several frustrated frontend developers out there that just want to make their life easier but currently all the arguments they find just favor 'React'....

Our whole Javascript codebase is 50k + lines. But the clients only fetch what is needed.

<comment><USER8> > joy to work with

Color me skeptical. React is quite literally the only framework I've ever found to be enjoyable (and maintainable).

</comment></comment></comment></comment></comment></comment><comment><USER11> I'm not a frontend developer and don't know really know JavaScript frameworks. That said, it seems like something very well established like React would choose to have a virtual DOM for a good reason.

Surely there must be some tradeoffs that the author makes for his design to get better performance. Could somebody explain the cost/benefit of doing things one way versus the other?

<comment><USER12> Virtual DOM was invented not to make things faster than with jQuery, etc., but to make a better and less error-prone style of web app development not be intolerably unperformant.

I think if we could see a larger Radi example, say, the standard TODO app, the costs of its approach would become obvious.

<comment><USER13> That's not true. Virtual DOM was created to avoid recreating huge DOM elements each time a re-render is needed, which was the way apps used to be done in the days of jQuery.

<comment><USER5> Eh, not exactly right either. In the jQuery days, the problem is that you needed different procedural code paths to go from one DOM state to another depending on what action you took. For example, adding a row to a list would be `$('.list').html(html)`, removing would be `$('.list :last- child').remove()` and updating one item might be `$('.list #' \+ id).text(value)`.

Templating engines such as handlebars provide a declarative abstraction that represents how the DOM is supposed to look like given some rules, rather than procedurally specifying how to get from A to B. This is similar to how you write HTML declarative as opposed to how you have to write canvas code procedurally.

Virtual DOM is just an implementation detail of some templating libraries that have the same goal of providing that declarative abstraction. The problem was that popular KVO systems (e.g. Knockout and Ember) were notoriously slow and people were looking for alternative ways to speed up declarative rendering libraries. The community has since learned a lot about performance and is realizing that KVO systems _can_ be performant after all.

The main drawback of KVO systems is that their API bleeds into the data layer because they require you as a developer to manually register data as observable entities. In contrast, virtual DOM works with plain Javascript objects which are much more familiar and easier to manipulate and interop with. A third approach, called dirty checking and popularized by Angular also had the desirable property of working w/ plain js objects, but it was also very slow. Some systems (most notoriously Vue 1) tried to bridge the gap between KVO and POJOs by providing a POJO-looking data layer that has monkeypatched array methods etc that provide observability/reactivity under the hood. Without JS proxies, though, this still left some weird edge such as the ones handled by `Vue.set`/`Vue.delete`. Vue eventually moved to vdom because the way it mounted subcomponents didn't scale for recursive mounts (think comment trees such as the ones in HN or reddit). This is because it had to mount each level to find out what subcomponents needed to be mounted, and as well know, multiple repaints is a big no-no for perf.

With that said, virtual DOM is not perfect either. It's inherently memory intensive and can block the UI in cases with large DOMs and few changes. Various frameworks have various techniques to cope (such as shouldComponentUpdate and friends) but they typically require developer intervention, whereas a KVO system would not suffer from this class of problems to begin with. Another problematic aspect of virtual DOM systems is that they are "naked" js and thus, difficult to optimize as libraries from an algorithmic standpoint. This is why Svelte does better in benchmarks than vdom systems.

TL;DR: if you want to evaluate the performance characteristics of a KVO system such as Radi or Surplus, the main things you should ask about are API lock-in in the data layer and performance of recursive mounts. If you want to evaluate perf of virtual DOM systems, you should ask about diff latency for needle-in- a-haystack scenarios and ease of use for hooks to selectively diff a tree.

<comment><USER14> > It's inherently memory intensive

Even if we pretend that other architectures doesn't have any memory overhead, vdom memory overhead in a large UI app will be less than a single small decoded image. But in reality, KVO can be way much more memory intensive, especially when we consider cases that involve filtering items in large collections.

</comment></comment></comment></comment></comment><comment><USER15> Surplus [1] is the fastest framework in the big JS benchmark challenge, and it too uses the native DOM directly rather than a virtual DOM. Looking forward to seeing Radi.js added to that benchmark suite to really put it to the test.

[1] [https://github.com/adamhaile/surplus](https://github.com/adamhaile/surplus)

<comment><USER16> The problem with not using a virtual DOM is that you can't merge in changes to stateful DOM elements. For example, an INPUT field has state (its value, plus its scroll position). If you regenerate the INPUT field from scratch, you risk losing the state. In contrast, if you use a virtual DOM, the vdom mechanism can merge in any changes for you (the INPUT field will stay the object!)

Of course, you can recreate DOM elements with their complete state, but if you'd try to do that with e.g. a VIDEO element, then you risk flicker and reloading of the actual video.

<comment><USER5> This isn't quite correct. Modern rendering libraries aren't going to recreate an input from scratch unless they absolutely have to, vdom or not.

What's tricky about reconciling app state changes and dom state is dealing with things like cursor position if e.g. the input value change comes from a socket and the user had the input focused and the cursor in the middle of the text. But this has nothing to do with vdom

<comment><USER16> To prove you wrong, consider how DOM elements are created (remember in Surplus there are no virtual elements). Ignoring all dependency tracking, the code to show some text _has_ to be (eventually) of the form

        x = document.createTextNode(v);

Now, consider the dependency v changes. The only option is to run the code above again, in its entirety. And thus, the DOM node corresponding to the text is _new_.

Of course, a smart library will ensure that the amount of nodes that has to be visited is at a minimum. But that doesn't mean DOM nodes don't get rebuilt from scratch.

<comment><USER5> > The only option is to run the code above again, in its entirety

Not at all. The reactive pattern typically boils down to something like this:

        el = document.createTextNode(initialValue);
        parent.appendChild(el);
        reactiveValue.onchange(v => {
          el.nodeValue = v;
        })

Ironically, in this specific example, vdom libs typically do this when possible:

        parent.textContent = v

which does in fact replace the underlying text node, but they do so for the sake of performance

<comment><USER16> Yes, you can code like that, but ultimately that block will be contained inside a closure that will get triggered by some change. Of course, unless you are very careful.

<comment><USER5> The element creation part will be triggered if a creation is required. It won't be triggered by a prop update, for instance.

In the following example, I change the button id on click. It's still the same button element after the change:

[https://jsfiddle.net/dwn36aw4/8/](https://jsfiddle.net/dwn36aw4/8/)

<comment><USER16> But it's very difficult to prevent unnecessary dependencies from triggering in all cases. Consider a map (dict) with some values. Some outer code depends on the map. This code builds some DOM elements and sets values based on the values in the map. Now, if the map changes, all the elements will be recreated, even if effectively some irrelevant part of the map changed. Of course you can prevent this from happening by doing smart diffing on the map, but now you've effectively moved the problem from dom-diffing to map-diffing.

<comment><USER5> I wrote about that (and the drawbacks and alternative takes) here: [https://news.ycombinator.com/item?id=16540223](https://news.ycombinator.com/item?id=16540223) but yes, in a nutshell, "move the problem from dom-diffing to map-diffing" is basically what a reactive system is supposed to be taking care of.

You're absolutely right that reactive systems are not trivial to implement (let alone implement well), but inefficient DOM recreation under these systems is a symptom of poor granularity in the reactive layer (which may be a problem with the reactivity library just as well as it could be poor usage of its API), rather than a limitation of the rendering library itself.

<comment><USER16> Ok, that makes sense.

I'm also worried about debugging accidental dependency triggers. Imagine that suddenly the scroll-state of some div is reset; how do you determine which dependency caused the DOM element to be recreated? With a vdom you avoid the whole problem.

<comment><USER5> > how do you determine which dependency caused the DOM element to be recreated

Normally, I would toss in a throw and look at the stack trace. But yes, the stack trace gets noisy as hell.

</comment></comment></comment></comment></comment></comment></comment></comment></comment></comment></comment><comment><USER17> This looks similar in many ways to mithril[1] -- somewhat similar api - mount, view, r("input") vs m("input"). The counter example[2] looks similar[3] I'd be interested in seeing comparisons between the two.

[1] [https://mithril.js.org/](https://mithril.js.org/)

[2] [https://github.com/MithrilJS/mithril.js/blob/5956314e3655a3c...](https://github.com/MithrilJS/mithril.js/blob/5956314e3655a3c85f8425bffc2bd76c1c541a3b/docs/mount.md)

[3] [https://github.com/radi- js/radi/blob/master/examples/counter...](https://github.com/radi- js/radi/blob/master/examples/counter.html)

<comment><USER5> Hi, Mithril author here.

In terms of API, frankly all the frameworks are more or less similar. Mithril has been around for a while, so obviously all the common observations apply (i.e. it's been more battle tested, it has a more mature community, more libraries, etc)

Taking a quick glance at the Radi.js code, I noticed a few things that could still use some improvements (e.g. the comment regexp someone else had pointed out, the handling of attributes not accounting for things like SVG, etc)

I didn't see support for lifecycle methods in the Radi.js code, and it's not clear to me from the docs whether keyed lists and fragments are supported. Keyed lists are extremely important in cases like `someArray.unshift()` and any list containing stateful dom (e.g. inputs or link tabindex). Lack of fragments would not be a deal breaker, but IME they're super nice for building lightweight abstractions, especially in Mithril's case, where they can have lifecycle hooks.

</comment></comment><comment><USER18> I recently did a project with morphdom ([https://github.com/patrick-steele- idem/morphdom](https://github.com/patrick-steele-idem/morphdom)) using only ES6 template strings and a render loop that checked for changes to a global state object and patched a re-computed DOM string using morphdom. Couldn't have been an easier and more pleasurable experience.

</comment><comment><USER19> The reason diffing and virtual doms are used are to prevent unnecessarily repainting the browser window 1000 times a second. If I have 5 updates to make, I want to do those in one paint, instead of 5. So the process is change -> change -> change -> paint.

With this framework's model, the process would be change -> paint -> change -> paint etc. etc. Sure, you get nice FPS (because it's painting a LOT), but that will destroy battery performance on mobile phones and I don't need 60 FPS in my shopping web app.</comment>


The History of Email  - <AUTHOR> http://mashable.com/2011/06/18/the-history-of-email-infographic/ <comment><USER2> Email is universal, but the message of this infographic is that the history of email was limited to the USA and England.</comment>


Say Hello to Nest Cam Outdoor - <AUTHOR> https://nest.com/ie/blog/2016/07/14/its-a-big-day-for-security-cameras/ <comment><USER2> Nice to see, but before I buy another Nest product, I need to see the App and Website get some serious performance and usability updates. I'm more tempted to go with a Foscam at this point.

</comment><comment><AUTHOR> I'm surprised by the exposed cable. Depending on placement, this might not be a big issue but it's the first thing I noticed...

Also - no mention on the cable length provided. I'm assuming there will be a requirement to have an electrical outlet internally or externally within the vicinity.

<comment><USER3> It isn't a wireless camera? How is this news?

<comment><AUTHOR> to provide power afaict. data is indeed sent wirelessly.</comment></comment></comment>


A Picture Is Worth a Thousand Cookies - <AUTHOR> https://blog.halide.cam/a-picture-is-worth-a-thousand-cookies-8400efa3d650?source=user_profile<comment>---3</comment><comment></comment><comment>---- </comment><comment><AUTHOR> What I found particularly worrying that the Facebook SDK potentially can use the permissions of an embedding app to do its own thing.</comment>


Show HN: A Chrome extension that dims online distractions to help you focus - <AUTHOR> https://chrome.google.com/webstore/detail/beeline-reader/ifjafammaookpiajfbedmacfldaiamgg?hl=en <comment><AUTHOR> creator here — we just launched Focus Mode, which makes reading on the web more enjoyable by dropping a semi-opaque layer over online distractions. You can adjust the level of opacity, as well as the color of the transparency.</comment>


The Sunset HTTP Header Field - <AUTHOR> https://tools.ietf.org/html/rfc8594 <comment><USER2> I'm aware that the following is typical HN middlebrow matter, but I'm asking anyway. Does anyone know why RFCs are still formatted as if they were written on a typewriter in the seventies? I mean, here's a sentence quoted verbatim from this document:

        Sunset header fields will be served as soon as the sunset date is

        Wilde                           Informational                     [Page 9]
        </comment><comment></comment><comment></comment><comment></comment><comment></comment><comment></comment><comment></comment><comment></comment><comment></comment><comment></comment><comment></comment><comment></comment><comment>--
        RFC 8594                        Sunset  Header                    May 2019

        less than some given period of time.

What problem does this solve? How is this more useful than it is cumbersome? also, how do people write this? Do they manually space space space space align the footer and then copy it every 30 or so lines?

<comment><USER3> You can read it with any software you like, now and in 30 years when Microsoft Word is a quaint relic in a museum.

<comment><USER4> To be fair, I recall having conversations in the 1990s about how MS Word was such an evil proprietary format and that one day we wouldn't be able to read it. And here we are nearly 30 years later and Word docs (in a much evolved file format) are still here and still widely supported and easy to read using many tools, including open source ones.

Not saying that proprietary formats aren't still a bad idea for other reasons, but predictions of unreadability don't seem to have panned out for any common file formats.

<comment><USER5> How do you open word documents from the 90's?!? Do you have a Windows 95 VM or something?

Even with modern Microsoft Word, the formatting of old documents is often mangled.

To this day, up-to-date PowerPoint can't reliably display presentations made with up-to-date PowerPoint on a different machine, let alone OS!

<comment><AUTHOR> > How do you open word documents from the 90's?

LibreOffice

</comment></comment></comment></comment></comment><comment><USER6> Google could use this whenever they launch a new service!

</comment><comment><USER7> This RFC is really indicative of what I hate about certain standards.

This is all very abstract. No user agent will use this in the same way. You'll end up writing code _per application_ anyway. All this is is a convention that people will interpret a bunch into. This is not going to be interoperable.

The epitome of this is ActivityPub.

<comment><USER8> What does it matter what the UA does with the information? The point is that the information is supplied; the UA can provide whatever benefit from it that _the user_ wants from it.

For example, I was just thinking that forum software could have their backends scrape image links you attempt to embed; and, if they find that the link has a sunset policy (e.g. it was from an anonymous image upload service that expires posts after a week), then they could rehost the image instead of hotlinking to it. (Or, cache the image for now, and then rewrite the link from a hotlink to a cached link when the deadline hits.)

That's not something you would standardize behaviour on. But, once you have servers providing the _information_ —not to a particular client, but just spewing it out as an objective fact out into the world—clients can do all sorts of things.

<comment><USER7> Standardisation does nothing for this. The software could've always just used an X-Sunset header or just another field in their dto.

My point was that there will never be a client that will blindly read that value and understand what to do with it. Which is why the only difference to "X-Sunset" is that there's an RFC with suggestions on how it could potentially be meant there, along with a syntax restriction.

ActivityPub is the epitome of this because they supply a lot of vocabulary and syntax variation to express them (including very complex ways to normalise that syntax, JSON-LD is not fun to parse) but doesn't actually made the implementation commit to anything. It's setting up a bunch of arbitrary rules for nothing. Every single AP implementation still orients itself on compatibility with Mastodon.

<comment><USER9> >Standardisation does nothing for this

Sure it does. If the information is standardized then the community as a whole can innovate around it. Browser plugins and the like can be made that make use of the information, etc.

</comment></comment></comment></comment><comment><USER10> I'm kind of torn here, because I could see this being really useful for web archivists -- e.g. the people who jumped to try to preserve as much of Tumblr as possible as that seems to be "sunsetting" \-- but the sites that are actually likely to configure this properly are the very ones I'd expect to have some of the best already-existing archives of. If someone cares enough to set this header, they probably also care enough to try to preserve things reasonably well, or at least have users who do.

The other use cases listed in the RFC don't seem incredibly compelling. Anyone have one that comes to mind?

<comment><USER11> The most compelling use-case for me is the web-api deprecation. It very clearly tells you when a service will no longer be available. Currently there are no standard mechanisms for this and are mostly driven by documentation. If an api used this then a consumer could look for these and raise alarm bells.

<comment><USER12> There are also plenty of services that host user content, but only for a short period of time. Pastebin entries with a set expiration could for example set this header to inform clients about the expiration date. That way software can detect links to content that will expire and act accordingly.

<comment><USER11> Yes, and I think that's the smartness of this is they clearly came from a stance of Deprecation and realized they could make it more general. Good work, imo.

</comment></comment></comment></comment><comment><USER13> I am not sure if Sunset is the best term here. Sunsetting in such a context would indicate retirement:

[https://en.wikipedia.org/wiki/Application_retirement](https://en.wikipedia.org/wiki/Application_retirement)

However the example given is indicative of a session duration, not a sunset period.

> For example, a pending shopping order represented by a resource may already > list all order details, but it may only exist for a limited time unless it > is confirmed and only then becomes an acknowledged shopping order.

Admittedly, naming things is hard, perhaps this could have been called Expiry: or Unavailable-After: or Valid-Until:

<comment><USER14> Well, we already have Expires for marking responses as stale in cache, and it's also takes just a date string, so things could get confusing there.

<comment><USER13> Perhaps we could Sunset the Expires header first...

</comment></comment></comment><comment><USER15> I'm afraid this won't be useful in the real world. API consumers who continue to use legacy endpoints after being told not to are unlikely to update their code to listen to a new HTTP header. This strikes me as a great idea in theory, but unlikely to be useful to websites actually looking to deprecate endpoints.

<comment><USER8> I don't think this is intended to be about endpoints, but rather about the resources under an endpoint. E.g., "this image will be deleted from this image-hosting service in 30 days" or "this is a link to an item in your Dropbox Trash folder, and the Trash is emptied every 48 hours" or even "this is a temporary share link and will work for 24 hours."

Given these use-cases, I could also see the use of a version of the header that doesn't specify _when_ the retirement of the resource will happen, but just specifies that the resource is, by design, not going to stick around forever. E.g. the URL of a "previous version" of something, where the system only keeps around N previous versions (so as soon as someone adds enough newer versions, the version you've linked to will disappear.)

Another fun use-case is sticking this header on _everything_ on a given domain (by e.g. reconfiguring your web load-balancer to emit the header.) Archive.org could then use this as a signal to automatically prioritize archiving content from the domain, before any human being realizes the service is being retired and prioritizes that archiving.

</comment></comment><comment><USER16> At WS-REST 2015(I think), I did talk about this with Erik Wilde (@dret), and we talked about the fact that is no good way to deprecate bookmarked url or an url stored in an uncommitted transaction. The idea was to add information so clients and user agent could keep track of resources: you can check it before their sunset date. The resource then could change the sunset date or redirect you to the new url.

</comment><comment><USER17> I'm happy to see this is finally entering the RFC phase. I've already seen this used in the wild for an API (imgur [0]), and I was surprised when they linked to the proposal from 2017 [1]

[0] [https://apidocs.imgur.com/?version=latest#api- deprecation](https://apidocs.imgur.com/?version=latest#api-deprecation)

[1] [https://tools.ietf.org/id/draft-wilde-sunset- header-03.html](https://tools.ietf.org/id/draft-wilde-sunset-header-03.html)

</comment><comment><USER18> Terribly vague naming. As a non-native speaker I would've never guessed the purpose, and I've been in the English speaking tech sphere for many years. Does anybody actually say "this website will sunset in 5 years"?

<comment><USER19> I've heard the term used for deprecation before, but not in a long time. I agree it's not great. At least they spelled it right, though!

<comment><USER20> Tech is never really deprecated; instead, like the setting sun, it simply departs to rise again another morning (when a web developer independently re- discovers it).

</comment></comment></comment><comment><USER21> I really like this idea. I used to work in advertising/marketing and we were launching a lot of purpose built, short-lived landing pages, e.g. to collect entries in a contest, then announce the winners. These websites were live for a period specified in the contest terms, then usually archived. I could see myself routinely implementing this header in such cases.

Also, from the resource consumer point of vie this could help guide efforts like archive.org to make snapshots before it's too late.

</comment><comment><USER22> Was looking for a way to tell API client about endpoint deprecation and stumbled upon another RFC from Feb 2019: [https://tools.ietf.org/html/draft- dalal-deprecation-header-0...](https://tools.ietf.org/html/draft-dalal- deprecation-header-00)

Actually, "E. Wilde" is on of the authors there too.

<comment><AUTHOR> That is an early stage draft, not a RFC.

</comment></comment><comment><USER23> tools.ietf.org (and only that site) seems to be down for me at present, failing in the TLS handshake, PR_CONNECT_RESET_ERROR.

Here's another URL for the content: [https://www.rfc- editor.org/rfc/rfc8594.txt](https://www.rfc-editor.org/rfc/rfc8594.txt)

<comment><USER24> FWIW tools.ietf.org is working for me.

</comment></comment><comment><USER25> The header that inspired Evan Spiegel</comment>


Do Young Venture Capitalists Have an Advantage? - <AUTHOR> http://bits.blogs.nytimes.com/2009/06/08/do-younger-venture-capitalists-have-an-advantage/ <comment><USER2> The premise of this article is rather superficial. You could just as easily argue that firms with older partners know the best investments because they have been around longer. To reduce the success of a firm down to age seems rather dumb.

<comment><USER3> It would be interesting to see a truly data-driven study of VC decisionmaking outcomes.

Do dumb VC's (of less than average intelligence or academic performance) do better?

How does a VC's educational background affect their success rate?

Unfortunately we will never be able to ask these questions of a high-quality dataset, since only funds with better than average performance will want to participate and much of the data is not public record.

</comment></comment><comment><USER4> what are some VC firms with "young" VCs?</comment>


The Immigration Iliad - <AUTHOR> https://medium.com/matter/the-immigration-iliad-6727955ae085#.vk8ml1vbf <comment><USER2> >But I have many feelings, not all of them charitable, about those who scream that undocumented immigrants are not law-abiding. I challenge these screamers to fill out the same paperwork I've had to fill out for the past few years and experience the same anxieties and fears I've felt. I'm sure they would wilt under the pressure

With all due respect, the author's case is unique. The screamers are not talking about people like the author. Also, a perfectly legal immigrant from India/China goes to ivy league schools, does the same amount of paperwork and waits for the same time, all the while paying taxes like a citizen. You don't hear anybody helping their case.

<comment><USER3> How is it unique? It's the situation the DREAM act was supposed to address and plenty of screamers are about that.

<comment><USER2> It is unique because his parents over-stayed a visa and not jump a fence. It is unique because the author actively tried to rectify his situation instead of just expecting to be handed a citizenship. Also, AFAIK, a lot more people are opposed to giving citizenship to _every_ illegal immigrant than to giving it to people who qualify for the DREAMer act.

<comment><USER3> A significant percentage of undocumented residents over-stayed a visa - perhaps 40%. You think the people spending years campaigning for the DREAM Act are just 'expecting to be handed a citizenship'? They're more involved politically than almost any American citizens are. There are a lot of people who've made huge efforts to get themselves legalized, and I think your comments are made out of complete ignorance and you should spend more time researching and less time spreading uninformed opinions.

</comment></comment></comment></comment><comment><USER4> How is that possible - living in the country for years and even enrolling in a prominent institution of higher education, all the while being effectively non-existent as far as the legal system is concerned? I can't get my head around it.

<comment><USER5> You are not non-existent, you are just taking another path where some things are "easier"(from locals perspective, it's usually easier to get a spot at a good school) to achieve they are actually much harder to hold because you are out of the safety net. Other things are incredibly laborious and some things are effectively out of your reach.

From techie perspective, think of it as dirty and quick hack. You are basically quick fix at the system, you don't conform to predefined interfaces and you do not fell in any of the object categories but you still can interact with other objects. Because you don't go from all the checks, some things are easier to you and you can run faster but at the same time you are out of any error checking mechanism. If you fail, you fail dirty and you can't recover.

So when you are an illegal in a country, you usually have access to some things like education and healthcare(sometimes easier than the locals) but you may have incredibly hard time to open a bank account and anything that depends on you having a bank account(the things that are easy and hard depend on the country). It all depends on what paperwork is needed, sometimes you hack your way to obtain certain paperwork(I know a guy who is taking the metro for free, so he would be fined and they will send him a mail with the fine and he will use that mail as proof of address to open a bank account).

Being illegal in a country is very interesting beast. Some people, like the person with the most upvoted comment make it look lşke it's a privilege but it's not. Do you fancy to be an illegal? Burn your documents and pretend that you are somebody else.

<comment><USER4> Interesting metaphor but I still don't fully understand. I imagine it is easy to go around doing ordinary cash transactions, hard but possible to find a place to live and work (you have to find landlords and employers who are willing to engage in sketchy things). But going to public school? enrolling in Princeton? Do these institutions seriously not care who you are?

Also, if illegal immigrants are not non-existent to the state, why are they tolerated and not getting deported?

<comment><USER5> studying is probably one of the easier tasks for an illegal immigrant.

states don't want to have much illiterate and skilless people around and don't want to block those who want to get educated so usually they have all kind of exemptions to enable people get education. also, because the education on the planet is not uniform things like maths tests can go long way instead of paper work.

</comment></comment></comment></comment><comment><USER6> > The attorney patiently explained to me that returning to Santo Domingo was > far too risky. Because I'd overstayed my tourist visa as a child, I'd be > subject to a ban on reentry; it was also extremely likely that I'd be denied > a student visa.

Well, why can't we just fix _that_ , instead of completely ignoring the law for 20 million people (while in the meantime, millions more wait in line the legal way without the privileges that this guy's family took illegitimately)?

</comment><comment><USER7> It should be Iliad with one 'l', as the author spelled it in the post.

<comment><USER8> Ugh. Hate missing those. Thanks.

</comment></comment><comment><USER9> Not being offensive here -- but how about imagine if the author is a terrorist, and this terrorist is studying in an Ivy and pretending to be a student.

<comment><USER10> You could ask the same question of any student, immigrant or not.

<comment><USER11> Imagine the commenter is a reactionary, pretending to not be offensive.</comment></comment></comment>


Why healthcare companies need a responsive website? - <AUTHOR> http://www.artwebnet.com/services-website-solutions/ <comment><USER2> Is that a actual question? Because everything needs a responsive Website! Visitors are from something like 30-70% mobile users, depending on the sector.</comment>


Show HN: Faces – A people directory for your community - <AUTHOR> http://www.getfaces.com/ <comment><USER2> Love the simplicity and speed! Could totally see using this for our urban farm. However, the price point seems a bit high for these types of communities. I wonder if there could be other monetization strategies, such as "promoted profiles" within communities that members could pay for.</comment>


Working Remotely While Traveling: A How to Guide - <AUTHOR> https://packhacker.com/guide/working-remotely/ <comment><USER2> This is great. I love the idea of remote work. At the same time I am picky about my environment. I prefer to put my laptop on a clean surface and be able to work where it's quiet and beautiful. I am not sure that a café is that place for me, although I enjoy them a lot.</comment>


How to monetize a site with variable user content? - <AUTHOR>

I have a website http://www.aggreddit.com/ which allows users to select and quickly view the popular links from reddit subreddits. I was originally using AdSense, but serving was disabled due to the links (content from reddit which I have no control over).
Is there any way around this? People are after all only getting the content they request! Or can anyone suggest alternative advertisers?
I'm not looking to make big money from this, but visitors are growing and I'd like to be able to work on more ideas I have for the site. <comment><USER2> Wow, this is really a neat product. I see so much potential here! It might be an uphill battle. Heck, a lot of good ideas are an uphill battle. Keep going!

Now, as for monetization. AdSense is simple and certainly ubiquitous but it is not the only game in town. There are a lot of advertising networks that pay very well. I would imagine that if you got your user base up you could have some very direct advertising areas.

One thing I would push for quickly is a way to ingrain the advertising a bit closer to the content. If you can do so in a elegant way, I think you'll be onto something. I imagine a "story" at the top of each reddit feed actually being a paid advertisement. You can even mark it as paid, no need to try to trick people into clicking on things. If you can find a way to target the "lists" with content specific ads, I think you'll have a big win. It's not as hard as it seems.

I, for one, will be using your service.

</comment><comment><USER3> Could probably get a few bucks out of ; [http://projectwonderful.com/](http://projectwonderful.com/) (nsfw friendly) until you compartmentalize the content properly for adsense to not flag/ban you.

</comment><comment><USER4> Off-topic: You might wanna sanitize user input

[http://www.aggreddit.com/?r=%3Cscript%3Ealert%28%27xss%27%29...](http://www.aggreddit.com/?r=%3Cscript%3Ealert%28%27xss%27%29%3C%2Fscript%3E)

<comment><AUTHOR> Thanks! Should be fixed now.

<comment><USER4> It seems not:

[http://www.aggreddit.com/?r=%22%3C%2Fa%3E+%3Cscript%3Ealert%...](http://www.aggreddit.com/?r=%22%3C%2Fa%3E+%3Cscript%3Ealert%28%27xss%27%29%3C%2Fscript%3E)

<comment><USER5> Yikes. :)

OP, you might want to check out HTML Purifier (if you're using PHP) and htmlentities().

</comment></comment></comment></comment><comment><USER6> I didn't think I'd find this kind of site very useful, but after playing with it for a couple minutes I quite like it. Once you've implemented a few more features (e.g., options for filtering, combining, hiding, etc.), I could actually see myself using the site and paying a small amount for the privilege — say, $5/year.

I don't know how many other people would be willing to pay for such a thing (probably not enough for it to be your full-time income, I'd guess) but you could give it a shot and see.</comment>


Immigrants' Babies Taking Over? - <AUTHOR> http://economix.blogs.nytimes.com/2010/09/01/immigrants-babies-taking-over/?src=twt&twt=nytimeseconomix

<comment><USER2> Hot Dog! The best Americans (US Citizens) are the children of immigrants. I wish I had a way to prove this, but for now take it as my opinion. By and large immigrants (legal or no) have a rather minimal impact on US culture, and tend to occupy the extremes of the educational and economic spectrum. For most, integration is difficult and can never be fully obtained.

The children of immigrants on the other hand have a foot in both worlds. They have heard their parents tell them about the opportunities that our country provides, and see in their parents how hard one must work to obtain them. They also have the advantage of full unquestioned citizenship (until the Tea Party messes thing up) and cultural acclimation that their parents lacked, along with social networks that extend beyond the immigrant community.

My experience is that the children of immigrants are more political and socially active then their peer with more established ties to community. They are better at taking risks and working for their own success. Most important, they understand the value of the opportunities, and the personal responsibilities that come with them, far better then other Americans who feel entitled by their birth to all that the country can give them.

Say what you will about immigration and its effect on jobs and the economy, but make sure to keep the children. They are worth every penny spent on their education, health care and other social services.

</comment><comment><USER3> So what? That's how America has always grown. Tempted to flag this posting just for playing into the ugly anti-immigrant narrative. And, to another comment, while I wouldn't call the NYT right-wing (in the sense of say, the Washington Times or Fox News), they are definitely defenders of the status quo when it comes to waging unnecessary and illegal wars or maintaining the growing incoming inequality in the USA (excepting their Editorial pieces).

</comment><comment><USER4> Flagged for right-wing fear mongering.

<comment><USER5> While, it does cast a certain perspective. I would be hesitant to call the NYT a right wing publication. Most, in fact accuse it of a leftward bias.

<comment><USER4> I didn't call the NYT anything. I called the article out for what it is.

<comment><USER4> Any of the downvoters care to explain themselves?

"Immigrant babies taking over?" has a negative ring to it for me. My counter- question would be: So what?

Why doesn't the headline read "Outlook on future population heritage"?

<comment><USER5> Just a FYI I did not down vote you. I thought your response to mine was valid.</comment></comment></comment></comment></comment>


Visualize your iPhone's location tracking map in 100% client-side Javascript - <AUTHOR> http://markolson.github.com/js-sqlite-map-thing/

<comment><USER2> Interesting.

For me, the data shows a lot of where I've been, but with only the sort of accuracy (and errors) you'd expect from tower triangulation.

It also misses some places that I frequent entirely (eg: it has almost no hits near my weekend house or some of the local places there my wife and I visit). Similarly shows no hits in the Pacific Northwest for me, but did seem to track my Vegas and Santa Barbara trips pretty well (though again with highly scattered accuracy).

Maybe it's just me, but I'm having trouble feeling very "violated" by this. If you were to look at my map, I think you could tell the area of the country where I live/work, but probably couldn't pick out my house or office with much accuracy (unless there are underlying timestamps the map doesn't show).

<comment><AUTHOR> Yes all the points have timestamps and an accuracy estimate, and there is wifi fix data too that this script doesn't show.

There is often erronous data in there too - that's not this script, that's just that location fixes are inexact.

The _real_ violation is that you just drag-dropped your whole iphone backup to a script written by people you don't know and running on servers you don't control... but don't worry, we don't _care_ to profile you or sell you data... ;)

<comment><USER2> _The real violation is that you just drag-dropped your whole iphone backup to a script_

Yeah, I guess. I just did a quick strings on the backup files, and you could extract a fair bit of info, but it didn't seem like there was much in there that was truly juicy.

</comment></comment></comment><comment><USER3> What amuses me is that people complain that this information is being recorded and then proceed to upload the database to anonymous applications to visualise it, thus compounding the problem.

<comment><AUTHOR> You can inspect the code - even run it locally.

But point taken, many will use this bit of power js without wven thinking of the consequences...

We wrote this for fun, and to show clientside js apps can do fancy things like parsing sqlite btree dbs raw, _despite_ the obvious privacy implications.

<comment><USER3> Sorry, I wasn't insinuating malicious intent. It's a cool app and I used it, it's much better than the openstreetmap version that was released!

My comment was more of a reflection of people's amusingly conflicting views. One thing this has made me realise though is that if Apple were to just ask their customers rather than operate with subterfuge then they could have avoided this whole thing being a problem.

<comment><USER4> Just think of how many sites ask for all your demographic info like ZIP when you sign up.

</comment></comment></comment></comment><comment><USER5> Nice! I didn't care enough to bother with anyone else's visualization tools.. This one lowered the barrier of entry enough for me to actually use it.

</comment><comment><USER6> It didn't work for me when I dragged only my consolidated.db file. That functionality might be a nice addition.

Not everyone backs up their phone regularly, but those with jailbroken phones can easily grab the database file over ssh.

<comment><AUTHOR> I think I added support for this, but I don't have the means to test it myself. Do say if it doesn't work to drop consolidated.db files now.

<comment><USER7> Doesn't appear to work with firefox 3.6.16 on Linux.

</comment></comment></comment><comment><USER8> What do these points actually represent? Mine shows a tremendous number of points in the regions where I've lived and been, but no points within about 1/4 mile of where I actually live and I have definitely used the GPS there. Also it shows some points near Las Vegas, which I'm pretty sure I haven't been to with iOS 4.

Some points even show up in the middle of the San Francisco Bay, which doesn't make sense if this is showing cell towers.

</comment><comment><USER9> For a Windows 7 machine on a domain, the file is: C:\Users\<User- Name>\AppData\Roaming\Apple Computer\MobileSync\Backup

<comment><USER10> Or better yet, %APPDATA%\Apple Computer\MobileSync\Backup.

</comment></comment><comment><USER11> It doesn't seem to show everywhere I've been. I put the whole folder in, about 2k files, and it only showed points near San Francisco even thought I've travelled with my phone to the East Coast many times this year.

Is there a limit on your plotting points? If so, I'd do a geographic sampling to get a good representation of my phone's life.

<comment><AUTHOR> Only one of the files you dropped was the location log.

The script shows what's there, and isn't trying to be the _cleverst_ visualizer I'm afraid

</comment></comment><comment><USER12> It didn't work for me... still shows it's loading

<comment><AUTHOR> Noscript, or using an old browser, or using IE, might cause that symptom</comment></comment>


Why Writing Your Own Search Engine is Hard - <AUTHOR> http://acmqueue.com/modules.php?name=Content&pa=showpage&pid=143

<comment><USER2> Is it just me or is this a silly article? I'm not really sure what the point is. There's the overweighted focus on hardware which isn't what makes writing a search engine hard. Then there's the pseudo code towards the end which really made the whole things bizarre.

<comment><USER3> It's silly in that the author means, by search engine, a clone of Google's architecture:

"A crawler gets the Web pages off of that pesky Web and onto your beautiful disks. You'll need lots of disks.

Then you need to index these pages--say which page has which words. This will tell you that Janet Jackson was found on the www.superbowl.com page. Usually, indexing happens locally on the disks where your crawler dumped these Web pages. Hey, why move them?"

It's just one possibility. An alternative (not necessarily the best one, though) could be a personal spider that starts somewhere and is intelligent enough to find what you're looking for without crawling the entire web. Or a peer-to-peer search engine, to share the infrastructure between the users. Or a search engine that only crawl in the subset of the web you're interested in (i.e. you manage a list of domains per user profile).

<comment><USER4> A peer-to-peer search engine sounds good. The difficult part is convincing users to donate the resources for your cause.

<comment><USER5> How do Skype and bittorrent achieve that?

</comment></comment></comment></comment><comment><USER6> Its seems that search (at least text search) is more or less a solved problem. Trying to innovate in the search space today is more or less as futile as trying to innovate in the operating systems space about 10-12 years ago. Noone really cares given that the state of the art works quite well.

<comment><USER3> Just because operating systems all look the same from far enough nowadays doesn't mean no innovation is possible. As an example, we are slowly moving from the old file/directory organization of files to a less hierarchical system (tagging). Or maybe we could destroy the notion of files completely?

The horse and carriage worked quite well, too.</comment></comment>


The Genius of MIT's Football Team - <AUTHOR> http://online.wsj.com/articles/the-genius-of-mits-football-team-1415663452

<comment><USER2> The team is in a great superposition to collapse into a winning eigenstate. Its interference pattern is constructive. The phase they're in is totally coherent. Their offense has got this great duality going, that you simply can't measure without screwing up. They've got this non-classical strategy that I don't understand. However I'm not going to comment on their position at this time; I don't want to alter the team's momentum going into the game.

</comment><comment><USER3> I was expecting to read about a "genius" plan they had for winning games, like moneyball or something.

<comment><USER4> Me too. Maybe they try sqrt(-1) percent.

</comment></comment><comment><USER5> Maybe it's because i'm not american, but that article is completely and utterly nonsensical to me. Is there some kind of injoke going on i don't understand?

<comment><USER6> It's not nonsensical, but it is a random collection of facts with no explanation. The article doesn't even attempt to answer the obvious question: what changed? _Why_ are they successful now?

<comment><USER7> Unless something changed with regard to the crew (rowing) program (which historically had more mindshare amongst MIT students), it's likely largely random. In Division III sports, you tend to have high variance in performance, since athletics are seldom the top priority of any of the students. It's probably a combination of solid coaching with luck off the field (which athletes the team was able to recruit) and luck on the field.

Next year, the football team will have a recruiting advantage over the crew (rowing) team, and you may see a long-term shift in football performance relative to crew performance. On the other hand, most US high schools have football teams but no crew teams. Incoming MIT students who didn't play on their HS football teams (most of them) perceive they're at less of a disadvantage competing in crew vs. competing in football. At least, these were my perceptions as an MIT freshman almost 2 decades ago.

</comment></comment></comment><comment><USER8> School: Chicago; year: 1939; achievement: eliminated program.

We do take it as a point of pride. We also had the first Heisman winner ever.

</comment><comment><USER9> Is it just me or does it seem like there's an outlier in the table that accompanies the article?

<comment><USER10> Just a note for those who don't know;

 _The NACDA Learfield Sports Directors ' Cup is an award given annually by the National Association of Collegiate Directors of Athletics to the colleges and universities in the United States with the most success in collegiate athletics._

So Stanford has been the successful collegiate sports program across all sports. Its also held that title for 20 years.

<comment><USER11> Just what college athletics needs, more fake awards designed to only be winnable by a few parties.

</comment></comment></comment><comment><USER12> From the chart, Stanford and Duke looks like they're in a class of their own..

</comment><comment><USER13> A bit of an ominous sign, isn't it?</comment>


First Class Statements - <AUTHOR> http://blog.jle.im/entry/first-class-statements <comment><USER2> This isn't exactly true. For example, the article names declaration and assignment as among "statements", but such statements are not first class in Haskell. Nor are type, data, type class statements, etc. It is true that Haskell manages to accomplish many things with expressions that you'd use statements for in other languages.

<comment><AUTHOR> Agreed, but there's a pretty straightforward distinction between statements amenable to becoming values and those that aren't. Essentially, those which control and define the type theory are out of scope as well as those which introduce bindings.

<comment><USER3> I hope that "not amenable to becoming values" is a transient state...

<comment><AUTHOR> I'm not sure how I feel about it honestly. I suppose in a dependently typed language there'd be some allowance for `IO Type`.

</comment></comment></comment></comment><comment><USER4> Somehow this doesn't seem correct. If statements were truly "first class", one should be able to programmatically put statements together and execute them (without using the loophole of simply calling the compiler).

<comment><USER5> > one should be able to programmatically put statements together and execute > them

I'm not sure I understand. In Haskell, you _can_ programmatically put statements together. You can't execute them willy-nilly just like how you can't try to execute an integer in python. You just create make a statement called "main" and the program is compiled so as to execute that statement.

<comment><USER6> Apparently Haskell does have a plugin that lets you eval expressions at runtime... from a string, though; is there a way to build an AST? (And what's the performance like?) Lisp of course would let you do something like

        (do-something-with '(+ a b))

and do-something-with could do any arbitrary transformation on the AST, possibly ending up passing it to eval, possibly optimizing it and compiling it to some other language... while Haskell's a leap in this regard compared to imperative languages, I think only something like Lisp can call its code truly first-class.

<comment><USER3> There's two ways in which I'd like to address your questions here.

First, directly addressing the question you asked:

There are a number of libraries for assembling and manipulating a Haskell AST - I would recommend looking at haskell-src-exts and Template Haskell. Unfortunately, there doesn't seem to be a way to exec any of these directly (at runtime). You could obviously pretty-print and then eval that, which may or may not be a good fit depending on your problem space.

Separately, I would like to suggest a different perspective, in line with the thesis of the article.

(Pardon me if this gets a bit rambly, and feel more than free to ask questions if it gets confusing - I've been meaning to expand on this in a blog post...)

Haskellers are fond of monads. Lispers are fond of S-expressions. Lisp programs are S-expressions. S-expressions are either an atom, or a list of S-expressions - a structure also known as a "rose tree".

It turns out, a rose tree is a monad. In particular, a "free monad", which means there's a unique function turning a rose tree into any other monad in a way that preserves structure (in math terms, a "monad homomorphism"). Getting slightly speculative, I think the homomorphism from Free to IO has to be Lisp's eval.

So in a senes, when Haskellers write functions that operate on "Monad m", they are writing functions that can operate on Lisp programs, and also on many "partial interpretations" or "restricted forms" of Lisp programs. This is why Haskell programmers get about as excited about monads as Lisp programmers do about macros - there's a deep connection.

The big thing that Haskell lacks, in this context, is a mutable global namespace - which keeps a few things compile-time only (and hence the need for Template Haskell for fuller coverage of metaprogramming).</comment></comment></comment></comment>


Powers Boothe of 'Deadwood' and 'Agents of SHIELD' has died - <AUTHOR> http://www.slate.com/blogs/browbeat/2017/05/15/deadwood_s_powers_boothe_has_died_at_68.html <comment><USER2> Although I was never a fan of Powers Boothe, I can highly recommend The Emerald Forrest, a movie that never got enough attention. R.I.P. Dah-day from my dreams.</comment>


Ask HN: What blogs/sources do you read? - java-man

I am developing a news personalization service (won't mention the name, it's not important) which currently scans about 300 sources: tech, security, science.
I would like to query the collective wisdom of the HN community.  What blogs or sites do you find insightful?  interesting?  original?
Thank you. <comment><AUTHOR> \- [Lobsters]([https://lobste.rs](https://lobste.rs)) \- [Hacker News]([https://news.ycombinator.com](https://news.ycombinator.com)) \- [Reddit]([https://reddit.com](https://reddit.com)) \- [Product Hunt]([http://www.producthunt.com/](http://www.producthunt.com/)) \- [Designer News]([https://news.layervault.com/](https://news.layervault.com/))

<comment> java-man Thank you. The problem with HN-like sites is that they are nearly impossible to analyze, since they function more like crowdsourced link aggregators rather than original sources.

An example of a "good" (in my opinion) source is Sean Carroll's blog:

[http://www.preposterousuniverse.com/blog/](http://www.preposterousuniverse.com/blog/)

</comment></comment><comment><USER2> "News" is awfully broad. Nevertheless...

For me it means:

www.nakedcapitalism.com www.eschatonblog.com asserttrue.blogspot.com thinkprogress.org www.scoop.it/t/news-that-doesn-t-fit

<comment> java-man Very interesting, thank you.

"News" is indeed broad, since blogs do not qualify for news. something that you want to read and follow, I guess.

</comment></comment><comment> java-man Partial list:

Aaron Toponce [https://pthree.org](https://pthree.org)

Abduzeedo [http://abduzeedo.com](http://abduzeedo.com)

ACLU [https://www.aclu.org](https://www.aclu.org)

adafruit.com [http://www.adafruit.com](http://www.adafruit.com)

ae911truth.org [http://www.ae911truth.org](http://www.ae911truth.org)

aeon.co [http://aeon.co](http://aeon.co)

aerospaceprojectsreview.com [http://www.aerospaceprojectsreview.com](http://www.aerospaceprojectsreview.com)

A Fistful of Euros [http://fistfulofeuros.net](http://fistfulofeuros.net)

AirlineReporter.com [http://www.airlinereporter.com](http://www.airlinereporter.com)

akihabaranews.com [http://akihabaranews.com](http://akihabaranews.com)

Al Jazeera [http://www.aljazeera.com](http://www.aljazeera.com)

AllGov [http://www.allgov.com](http://www.allgov.com)

AlterNet [http://www.alternet.org](http://www.alternet.org)

American Forces Press Service [http://www.defense.gov](http://www.defense.gov)

amusingplanet.com [http://www.amusingplanet.com](http://www.amusingplanet.com)

AnandTech [http://www.anandtech.com](http://www.anandtech.com)

Android Police [http://www.androidpolice.com](http://www.androidpolice.com)

aNewDomain [http://anewdomain.net](http://anewdomain.net)

anonhq.com [http://anonhq.com](http://anonhq.com)

AntiWar.com [http://original.antiwar.com](http://original.antiwar.com)

APOD [http://apod.nasa.gov](http://apod.nasa.gov)

ArchDaily [http://www.archdaily.com](http://www.archdaily.com)

Architizer Blog [http://architizer.com](http://architizer.com)

Arms Control Wonk [http://armscontrolwonk.com/](http://armscontrolwonk.com/)

Ars Technica [http://arstechnica.com](http://arstechnica.com)

astrobites.org [http://astrobites.org](http://astrobites.org)

astroquizzical.com [http://astroquizzical.com](http://astroquizzical.com)

Autoblog [http://www.autoblog.com](http://www.autoblog.com)

AvaxNews [http://avaxnews.net](http://avaxnews.net)

Aviation Safety Network News [http://aviation-safety.net](http://aviation- safety.net)
</comment>


Here's how you can spot if you're working with a micromanager - <AUTHOR> http://www.slideshare.net/weekdone/do-you-lead-or-micromanage-6

<comment><USER2> Being completely honest (although with a limit) with your team/employees goes a long way.</comment>


There is a will there is a way read your email on iOS even if IT don't like it - <AUTHOR> http://www.systemajik.com/blog/faking-imap-for-exchange-email/

<comment><USER2> >even if IT don't like it

Fuck cooperate security, I want my iPhone cake and to eat it too!</comment>


Register for do-not-call list. Cell phone numbers go public this month - <AUTHOR> https://www.donotcall.gov/register/reg.aspx

<comment><USER2> Searching for "cell phone public" brought me to this:

[http://urbanlegends.about.com/od/business/a/cell_directory.h...](http://urbanlegends.about.com/od/business/a/cell_directory.htm)

Cell phone numbers have been going public this month for the last 6 years. =(

</comment><comment><USER3> I've always had issue with the fact you had to go on a list to say you dont want to go on lists.

<comment><USER4> I too have felt its a bit strange to write down your name, phone number, maybe some other piece of contact info and submit it in order to say I want to retain my privacy and not have my contact details released to marketers.

How long until printouts of this list are found in a dumpster somewhere.

</comment></comment><comment><USER5> This urban legend will never die it seems.</comment>


IPad Developer Makes Thousands Because Apple Didn't Include An Alarm Clock App - <AUTHOR> http://www.businessinsider.com/sourcebits-iphone-android-2010-5 <comment><USER2> That's a stupid title. Is it really an omission on Apple's part? What other software did they "not include"? That's like saying "iD Software made millions because Microsoft didn't include a first person shooter in windows."

How about "clever man makes money providing a simple but functional program for a new computing platform"?

</comment><comment><USER3> _...we asked about the relatively weak Android sales. Rohit blames it on Google's lame Android Market, "Google does not provide web links that we can link to app -- they have no web store".._

There's an opportunity! Someone get an Android app-store going, quick!</comment>


The Life of Dustin Curtis - <AUTHOR> http://dcurt.is/the-life-of-dustin-curtis <comment><USER2> This is the exact use case for why we built StoryApp.

<comment><USER3> Mind dropping a link so interested people can check it out?

<comment><USER2> Sure, I just didn't want to be spammy. Have a great weekend it, here it is:

StoryApp](http://www.itunes.com/apps/StoryApp">StoryApp)

Not sure if these HN comments pick up HTML. If not, apologies!

<comment><USER3> No, straight URL. May want to retry that (and thanks)!</comment></comment></comment></comment>