skysight-inc/HackerNews huggingface dataset:
> 7 years later he died of a heart attack while jogging at the age of 52.

> His death doesn't mean running is a bad idea - a single anecdote is statistically insignificant - but perhaps it can remind us that nothing we do can guarantee a long and healthy life.

Or one could see it this way: His father had a heart attack at 35 and died of another heart attack at 42. Jim Fixx, who had a genetic condition, was a heavy smoker until age 36, etc., might very well have bought himself an extra ten years or so.
That assumes that hostile takeovers are good, even relative to entrenched and entitled management. It could amount to one fox keeping another out of the hen house.
How does this compare to RabbitMQ?
Khosla loses battle to keep Martins beach access closed
Why is it a bad idea?

I work together with a bunch of developers on a website that renders its HTML output with XSLT. What you address is architecture.

What we basically did is we have one XSL file for each "element". Elements are: button, image, headline, etc. Each of those elements inputs "our own" XML syntax with wisely chosen defaults (some HTML attributes like class,id,style get just passed through) and outputs Twitter Bootstrap HTML. Writing responsive websites in our framework is extremely easy. So each element has a XSL file where the magic happens, an XML file with documentation and tests and additional files like scass/css/js files with the same name. Accessing them is extremely easy when you use something like Sublime Text (what we all do).

All those different templates get written into just one XSL file automatically with the help of node.js' gulp.

The website gets delivered in Apache Cocoon which has a pipeline concept similar to gulp. Once a page got rendered, it is cached until the next update (except for pages with dynamic content of course).

The whole frameworks documentation is basically a website written in this framework with automated tests.

We use XSLT 1.0 + EXSLT and have written around 30 (EXSLT) functions to make sure everything works like we expect.

Everybody in our team loves it.
Read.As much as you can.I too live in a third(or maybe a two-and-half?) world country.You have the internet with enough number of things and articles to read.Start with small novels if you want(Enid Blytons,Franklin W Dixon etc) and move your way up.
That is especially scary. Several years back, I could get decent news from yahoo, and they had a balanced group of opinion writers....., then poof! After reading this article I am guessing Vidra might have orchestrated that change too.
Mouse vs. Keyboard (Plan 9 Wiki)
For me it's that the odd-numbered nomths have 31 days, and the even-numbered ones have less, in the first half of the year, and vice versa for the second half.

That's better than the poem in that you can't mix it up, AND it's faster than audiating all of that.
The way to go is nuclear desalination. The nuclear industry needs to be incentivized, and is badly in need of a SpaceX type company.
Why Elders Smile
lot of the comments sound fatalistic, almost seems like they are invalidating and refuting healthy lifestyles.
Rabbitmq is AMQP and mostly an "enterprise-class" thing. MQTT is more of the IoT messaging protocol, don't think they're trying to do the same thing?
The point is that the concentration of energy in lower frequencies (i.e. the reason you see sparseness in the wavelet domain) is separable from the issue of using IFS. After all, using IFS means you encode an operator, not the signal.

One way to demonstrate this (which was shown around the time of Davis's paper, if I recall correctly) is to do the IFS codec in the wavelet domain hierarchically (on quadtrees in the case of an orthonormal wavelet basis). This gives you a similar advantage of spending your encoder bits (which should still be handled by an entropy coder, regardless of method) primarily get spent where the image energy is, but does not truncate information as hard as, say, a zerotree approach.

The problems Davis points out with IFS codecs done on blocks in the spatial domain are issues with block/patch operations and with operating in the spatial domain, not with IFS per se.

The fundamental idea behind IFS codecs is that you encode a transform whose fixed point approximates your signal, you don't encode the signal directly.

The real problem is the difficulty in embedding them, and the need to iterate a few times to converge the result.. which is what you allude to I think.

[note, I really should revisit Davis's paper before discussing , because I'm operating from memory here...]
But is that better or worse than lets say TV advertisement?
Owl swimming in Lake Michigan, caught on camera
The credit card company charges the shop a transaction fee for using the card. The retailers allow this as it increases the chance of someone making a purchase, especially bigger purchases.

The credit card company sets out in it's terms of business that the shop must not have a surcharge, and must charge the list price for good paid for by credit card. This is so that using a card is attractive to the customer.

The card fees can be quite high. High enough for there to be more money than the transaction really costs, and the credit card company can then offer some of this money back to customer to entice them to use this card rather than some other card that doesn't offer cash back.

The end result is that customers who pay cash are subsidising the prices of those who pay by card.

It's hard to break the cycle because if a shop doesn't offer payment by card, not many people will shop there as people don't carry much cash.

Amex have the highest fees. I don't know why shops even allow amex.
I agree with you, and I see that you agree with me in that it's inappropriate to conclude that "Leaving X" implies that a person was at X 'for some time.'
The plateau seems to happen once a technology is no longer the winner, and research moves on to the next.
>If we eliminated everything where implementations have had obscure bugs or security vulnerabilities, there would literally be nothing left.

The point is that by eliminating this data format you get rid of those obscure bugs and security vulnerabilities and you lose nothing of value doing it.

>This is so incredibly wrong, on every level, that it belies belief and reads like something you would come across on a "beginning programmers" forum.

I wouldn't find this quite so pathetic if I didn't have to school you on XML parser vulnerabilities.

>As others have said, JSON/YAML thus far have seen limited usage

What are you smoking? JSON is everywhere these days. More commonly used in new web APIs than XML for sure.

>But as it grows people are starting to ask questions like "Gosh, wouldn't it be nice if my perimeter or the source system via a metadata file could validate the JSON passed to us". "Wouldn't it be nice to be able to convert from what JSON form to another."

The first I hear occasionally, but it honestly isn't ever a problem. You can put validation in the code that parses the JSON. Invalid date sent? Return an error when your javascript/python/java returns an error parsin it. Name too long? Ditto. You don't need additional outside validation if your programming language doesn't suck.

The second question isn't one I have ever heard in 12 years of software development. Generally you want to do something useful with JSON input. That useful thing isn't normally "make more JSON that looks slightly different".

>And the exact same complexity is arising

Nope. Ain't no billion laughs vulns in any JSON parsers that I know of. No subtle parser bugs causing fucked up behavior down the line either.

>I mean some of the comments are incredible. Like "JSON is simple enough that errors aren't big" -> Hey, sorry that those bank transfer got lost, but it turns out that we mistyped the account number and the destination system just ate it. Json.

If you mistyped the account number on your banking system and it got caught by an XML validator your systems must be fucked.

That's the worst excuse for XML I've ever heard: that your systems are so terribly programmed that you must find user errors via validation of your data interchange format. Jesus.

>Sorry that the dates are completely wrong, but all of those years of discovery about time zones and regional settings...just make it some sort of string and they'll figure it out.

Essentially, yes. ISO 8601 and you're done. Where's the problem?
I gather that the idea is that stock prices a manipulated to follow a sawtooth pattern -- plummeting with the big bath of the new CEO and rising during the CEO's tenure. I haven't seen the evidence that this is so, but it would explain why CEO compensation exceeds returns on investment.
I think you just described every discussion medium on the Internet.

As a reddit refugee, I was hoping for a little more on HN.
Given the revelations by the person who hacked Gamma, they aren't omniscient
I'm a designer, can't read code, and I'm trying to see if I should evangelize this at work. Its better if you could communicate with us non-technical folk and post an answer that the previous guy asked so that we other designers can also understand.
A "product" with no prices listed, just the shady practice of forcing you to contact them and having them work out a "quote" for you.

I really hate it when companies feel they cannot be transparent about pricing, it is such an obvious strategy to work out how much they can squeeze out of each potential customer. How are you meant to trust a company like that?
Why Growth Hacking doesn't work
It can, but there's a time and place for everything
Setting up posgtres database for django development
Josh Freed: Crimes are way down and I know why
Batteries are extremely expensive / inefficient for that.
How Overcast asks for reviews
Teknik: FOSS email, repos, file hosting, blog
One could argue that a block chain fork could invalidate an arbitrary number of blocks at any time, and therefore the Bitcoin protocol does not by itself have this property of being able to tell which transactions really happened.

To limit the number of blocks that could be invalidated in this way, the bitcoin reference implementation contains checkpoint hashes. These are indeed decided centrally.

If you accept the core assumption in bitcoin that an attacker will never control a majority of the hashing power, then there probably isn't a problem and the checkpoint s aren't needed.
Watson refers to the technologies used in the Jeopardy system, yes. Specifically, it refers to the Watson API, which consists of all the NLP and AI algorithms used in the Jeopardy system repackaged (with additions) and hidden under a simpler, query-based system. The Watson API is becoming the basis for most of IBM's Bluemix services which are described by IBM as "cognitive" (as you phrase it, "semi-intelligent systems" - referring mainly to NLP and related applications).

IBM is working on a number of applications to use the Watson API, as well as inviting other developers to use the API. Watson Analytics is just one of these applications, but it doesn't run on Watson alone. It is probably better to think of these applications as fitting within the overall framework of IBM's bluemix services, which includes Watson but also other technologies less geared towards NLP.

https://console.ng.bluemix.net/
RabbitMQ is originally an installable package that can support a wide range of behaviours -- you still need to be mindful of which you choose. Depending on your settings, you can see orders of magnitude changes in throughput.

Disclaimer: RabbitMQ belongs to Pivotal, the same company I work for.
Yes it does. People dismiss conspiracy theories cause they're unbelievable. When previously unbelievable becomes true it lifts bar of unbelievable. Previous conspiracy theories now become possible even probable scenarios we must guard against.
[¡Hola desde Argentina!]

This is an English speaking forum, so your submission will probably be killed or ignored. There were some successful submission in other languages (including Spanish) but they had unique information that has no equivalent or similar in English.

I think that you should try to submit some information about your experience in an English post.

Another possibility is a press coverage. I read the Techcrunch article, but I think it cover a lot of Colombian strtups. Is there an article only about yours?
A much more interesting question indeed.

There's been numerous (human and animal) studies showing benefits of strength training for elderly. Ergo-log covers [1] those [2] all [3] the time [4].

Then there's evidence [5] suggesting that higher calorie burning is directly associated with reduced death rate.

And a specific quote on muscle mass:

"A recent theory suggests that developed muscle mass results in considerable emissions of anti-inflammatory and life-extending signal substances. That's why muscular strength is believed to protect against cancer and why strong men are thought to live longer."

(links to studies confirming those claims are in the article)

The thing about running (if we're talking about traditional jogging) is that it does poor job at burning calories. It's a movement that becomes "familiar" very quick (and so becomes easier, according to Principle of Adaptation) and the one in which it's difficult to increase intensity. You also don't develop muscle mass when jogging, which would contribute to higher metabolic rate and reduced chance of injury.

Everything suggests that strength training (whether it's bodyweight, yoga, suspension trainer, or barbells and kettlebells) combined with proper supplementation is the best bang for your buck.

[1] http://www.ergo-log.com/over-seventies-benefit-more-from-pow...

[2] http://www.ergo-log.com/combination-strength-training-green-...

[3] http://www.ergo-log.com/over-nineties-still-react-to-strengt...

[4] http://www.ergo-log.com/cholesterolmuscles.html

[5] http://www.ergo-log.com/caloriemortality.html
I'd guess worse because there aren't much TV's playing to empty spaces.
>JSON is currently deceptively simple precisely because its wire representation (with simple types) is equivalent to its type definition which can be directly evaled in js to produce a memory instantiation.

It's not deceptively simple. It's just simple. The fact that it can be evaluated in JS is incidental to its use as a general purpose format for serializing data structures.

>Try for example marshalling a JSON object with a tree structure.

I've done this lots of times. I don't see any issue with it.
Mercury (1998).
Few questions and thoughts on top of my head.

1. Why a Subset of HEVC Still Picture Profile? Why not just a use HEVC Picture instead?

2. Since JS sources are readable and being interpreted by VM ( Free Speech ), patents issues should not be a problem?

3. I am assuming the quality of BGP still has Lots and Lots improvement to be made? Since all H.265 encoder hasn't had the time to be tuned. ( Compared to x264 )
Strictly uninformed logic hear, but it seems considering "excretion" and "detoxification" mutually exclusive concepts is not correct. If you were putting toxins (of any definition) into your body, slightly faster than your liver/skin/lungs could remove them, they would slowly build up. Perhaps they would make you feel sick before they killed you. Or perhaps the filter rate is proportional to the current level, so you reach an equilibrium at a point that makes you feel ill, but doesn't kill you.

If all this is in any way valid, then we might hypothesize that simply stopping putting "toxins" into your body for a period would allow a daily net loss as your body filtered them out. This would not require any special "cleanse", but simply living strictly on foods/drinks that did not contain whatever stuff you were trying to eliminate. This might allow them to decrease to a level where you felt better. Perhaps after that you would go back to your old life-style and let the "toxins" build up again, or you could input them at a level that your body could eliminate them.

Apart from aversion to the now coopted phrase "cleanse", could someone with actual knowledge say whether any of this conjecture aligns with actually physiology/metabolism?
Nice trollin'.
The World Cracks Down on the Internet
Does anyone have a link to a copy of this email?
This isn't the 60s. What an embarrassing display of technology.

We could have the Space Shuttle 2.0 but we get this rehashed waste of money instead.

So disappointing.
But I think you're making the same argument. A CEO is a "stakeholder". When the CEO makes decisions with an eye on the very short-term (to hit share price or EPS targets) he or she potentially destroys capital.

It might even be the case that shareholders today aren't really any better than other "stakeholders" in terms of alignment of incentives. If I'm just arbitraging a stock, do I really care how the company actually performs in real life? Probably not. I care about the popular perception of the company in the market at the point at which I want to sell (or buy, I suppose, depending whether I'm long or short, but whatever, same difference).
Penicillin tactics revealed by scientists
This isn't a new story :D
This is really neat, but I'm not really getting why it's here. Owls are known to swim from time to time, particularly when they are injured. This isn't unobserved behavior or anything.
XML is very simple. Maybe YAML is simpler but both are very simple. XML is tedious to write, verbose and repetitive, but not complicated nor complex. XSLT is also conceptually very simple. XML, XML schema tools and XSLT make a very powerful combination that has proven to be useful in a myriad of real world problems.
That is more of a butterfly stroke than a breast stroke.
Solving Problems with Sets and Comprehensions in Python
Show HN: MessageFormatter implementation for .NET
HN's commenting policy is a barrier to diversity in tech
jslinux cool. I tried it; running Emacs in it - https://twitter.com/jouborg/status/541252302309715968
This is an analysis of adoption from 2000-2010.
It's funny how just from the description - "toughest, ugliest" - I knew exactly what warplane it was. As a kid thirty years ago, I probably put together five different plastic models of the A-10 Warthog.
The law is rooted in "[objectively] reasonable expectation of privacy." Someone who is technically ignorant can't see past the layer abstraction presented by the software: a file on cloud storage appears in the photo viewer alongside files on the local flash memory. But the technical reality is that cloud data is exposed to potentially hundreds of people at the ISP and service provider. Not only that, but potentially data-mined on top of that. Only if you're technologically ignorant of this fact could you reasonably expect that the data is really private.

Look at it this way. If your pot growing operation is visible from your neighbors window (just one person!) we say you can't reasonably expect privacy. Dillon v. Sup. Ct. How can we say data visible to your hundred closest sysadmin friends at CloudCo is private?
Good point: consistency in funding is pretty important, and to manage projects for the long term...also in industry. It would be tough not to know what your budget would be for 5 years on a 5 year project.
Last week I went mountain climbing (a 19,900 feet mountain) and one of the people there was a 71 years old man.
I think this is interesting (ok, not very interesting, slightly interesting). Where I live I never had seen an owl swimming. For me it's interesting because they don't swim like ducks.

Nevertheless I think that it's better to submit the original video than an empty blog post: https://www.youtube.com/watch?v=UvrAGHGJIpE
Strange: JPG is, when compressed, order of times smaller than uncompressed, so if the graphic card would accept the compressed image, the amount of used memory bandwidth can significantly decrease. I also believe that the graphic card can achieve more parallelisation and therefore handle much bigger JPG images, which we produce all the time with always bigger cameras.

I believe that some browsers actually keep in RAM all the images uncompressed, that can acually be the reason that makes the potential for optimizations less obvious.
I would check on the shoes and then have a running store look at your stride. I used to hate running because in general it hurt. I tried a bunch of different shoes, settled on Brooks Ghosts, and running is actually a pleasure. I also focus on my stride and work on foot strike, length of stride, etc...

Since you're doing the C25K I'm assuming you are not super athletic to start. If you are overweight, you may want do some other cardio until you get your weight down a bit. If it hurts obviously don't do it and find some professional advice. Re-doing days in a training program is fine, everyone has their own pace.

Good luck!
Russian interest in Bitcoin soaring
While I agree with your sentiment, 30 years seems unreasonably long to me. At that point, you might as well just require the stock be put in a trust for the CEO's heirs.
What this is really about, to me, is trust and its tendency toward self-fulfilling prophecy. This isn't about a major change in the philosophical concept of a business. It's about CEOs no longer being trusted to make long-term decisions (and the culture of moronic short-termism trickles down to programmers dealing with "scrum" and "sprints" and shit.)

When people are trusted, most will keep the self-dealing to a minimum in order to continually earn that trust. But once they sense that their organizations or managers don't trust them, it's just natural to conclude, "I don't care for them either" and maximize for short-term personal yield. At scale, this leads to macroscopic underperformance and everyone loses.
if they don't know/want to use SQL and rely on ORM mapping alone, then they can as well do away with SQL databases too.

Until that whole leaky abstraction problem kicks in.
No this matters for even more complex things like CMS or web applications or forums.
iPod classic  is currently the most expensive iPod
Not helping matters is the fact that the Lightning II (or as I like to call it, the Littoral Combat Ship of the Air) is at least as ugly in functionality as the Warthog is in looks.
That is an issue, but it's more of an education/naming issue since it is, after all, intentional.

I think it's really dumb that most YAML libraries have a load() and a safe_load(). If they had a load() and a dangerous_load() then the problem basically wouldn't exist.
I suspect that troops on the ground don't get a say in this.

Edit: I suspect that US troops on the ground don't get a say in this. In other words, it doesn't further some politician's (or politically motivated general's) agenda to champion this plane over something less effective.