skysight-inc/HackerNews huggingface dataset:
Waiting until you feel pain is waiting too long. Every runner, from day one, should learn enough about running dynamics and injury causes that they can recognize and do something about bad form (even if it's only "bad for them" form) before it gets to that point. That's where the article missed a chance to help. A paragraph or two about foot landing and body angle, why they matter and what to do about them, would have done a world of good. It doesn't take much. Instead we get "neither is better" and "don't worry about pronation" and no mention at all of anything above the knee. While it's true that not everyone runs the same way or should - I'm a bit of a supinator and I'm not likely to change - it's still important for people to understand right from the start that different running styles will have different effects.

"Whatever you do is OK" will just lead some people to be miserable even if they're not actually injured. Like every skill, there's knowledge involved in running. I personally would not have kept running past that first day if I hadn't learned enough to know that my misery might be because I was doing it wrong and that running differently might be worth a try. The way to get people into running is to coach them into it and make sure their early experiences are positive ones.
There was a span of a year or two when I could literally write 68000 machine code by hand, without needing an assembler, due to an obsession with sprite blitters culminating in a bit of code which would generate arbitrary custom blitmask functions as part of the image-loading process. I had very little understanding of "abstraction" at the time, so it pretty much just built instructions from the bits up via shift and mask operations. I would never do anything like that now[1] - but I'll always be proud of the day I dropped into Macsbug, picked out a section of memory, wrote myself a minimal Tetris implementation, moved the PC (aka IP register) into it, and played. It crashed, of course, but the fact that it even sort of worked felt pretty good.

1 - possibly not strictly true in the literal sense as I still have a soft spot for these sorts of hacks
If you're running a vanilla Django site with no esoteric libraries with special requirements (like numpy/scipy that need compilers etc. to get installed), this is definitely the correct way to go. But if you do have non-standard requirements that fall out of the rails of your PaaS, you need to consider other solutions.
I think, the only difference between Puppet/Salt/Chef and shell scripts, is that CM tools already have a collection of common building blocks for stuff like "check that package uwsgi is installed" or "check that uwsgi config for application 'mywebsite' matches this template", plus dependencies between those blocks (including dependencies on config file templates and automatic reloads on changes). I tried both approaches and can say that I feel that Puppet and Salt actually save a bit of time, by not having to inventing grep/sed/awk invocations to manipulate files.

They're a bit more verbose than `scp ./files/nginx.conf $HOST:/etc/nginx/` or `ssh $HOST sed -ie 's/.../.../ file.conf' for most basic stuff, but way less verbose for anything even a bit more complicated.

I don't use Docker or Kubernetes, so no idea about those. But I think configuration management tools can save time. But their usefulness is debatable if, say, all you need to deploy is to scp and untar a simple archive then poke init system to spawn or reload a daemon.
Probably because that's how screen did it before tmux
It helped that the allies managed to kill a large proportion of the "difficult" people in those countries. The surviving population were left in devastated cities with starvation rations and the memory of a brutal invasion. Hardly an environment that makes people want to resist an occupation.

The shock and awe approach in Iraq allowed huge numbers of soldiers to survive the war without ever really being properly defeated. It is hardly surprising if they switched to an insurgency when the new country offered little in the way of jobs or opportunity.

We need to realise that war is about violence. It is naive to believe you can defeat a country psychologically without defeating them physically first. The West is understandably reluctant to face up to that reality.
> But why can he vouch that libX11 is any more secure? The library that runs complex input method code on every key-press, that has had CVEs in it? [0] [1]

GTK (at least the 2.x series, I don't know if that's changed in 3.x) uses libx11. There's a good chance that, if there's a major flaw in libx11 which can be exploited, a GTK-based program is vulnerable to it. GTK is pretty massive, so it likely introduces issues of its own.

E.g. this bug: https://bugzilla.gnome.org/show_bug.cgi?id=722106 in GTK triggered this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1064695 .

> Not to mention that I can still write a keylogger that bypasses jwz's xscreensaver. [2]

You can write a keylogger that bypasses pretty much anything that's X-based.

To, uh, to put it bluntly, ditching X11 for something saner would be the correct approach. Stacking stuff on top of X11 makes the problem worse; not stacking anything leaves it pretty bad. I'm not overly optimistic about Wayland, but I guess we'll have to wait and see :-).
Slugging Percentage vs. Batting Average: How Loss Aversion Hurts Seed Investors
> It is not the software writers' fault that your distro can't be arsed to keep its package system up-to-date.

That's it. Ubuntu releases every six months, it's not upstream's problem that an up-to-date version of your stable distro is using the program released in September 2014 (17 months ago). As XScreenSaver 5.32 was released in November 2014 and Debian stable was released in April 2015, you have to wonder why in those five months why it was not 5.32 which was released, or even 5.31, but 5.30 which was released seven months before.

Does anyone remember July 2002 to June 2005, almost three years between Debian releases? I do. You can point figures for why that happened, but it makes little sense to point them at the upstreams who make your distribution possible.

At the end of the day, the message jwz put in the code is crystal clear - if you are unhappy with the message and don't plan to keep your distro somewhat up to date, he'd prefer you just rip out xscreensaver from the distro and use an alternative. It doesn't make sense to compare him to a terrorist setting bombs as someone did in the thread.

It goes back to the initial reply. For all the gnashing of teeth and finger-pointing and name-calling and effort to deal with this and other issues due to old packages - if Debian channeled all of that energy and effort into a shorter, saner release cycle, it would be much more beneficial to everyone. If stable Debian was as current as the last release of Ubuntu or Fedora or OpenSuse etc., this discussion would have never taken place.

P.S. One good reason to download XScreenSaver 5.34 is the additional Android functionality. XScreenSaver 5.35 will possibly have much-expanded Android functionality when it is released (or if not, then 5.36 or one soon after). If you have Android Studio and an Android device (or emulator), compile it and give it a whirl. Once it gets into shape more for users, an APK will probably be put up, and possibly even a Google Play app. So if you're an Android developer, give it a whirl. Send an e-mail to the folks in the android/README with any bugs, questions, comments, patches etc. Probably best to e-mail first before doing the work on major patches. Give it a spin.
And then the CPU itself is a bunch of wires running in parallel with careful synchronization to pretend to be a serial or barely parallel (multicore) machine. ;)
Users flagged it, which is the most frequent reason why stories drop in rank on HN, especially when the drop is precipitous. That's what happens when flags reach a critical mass relative to upvotes.

We sometimes turn off the flags when the article is unusually substantive. I'm not seeing that here though.
These will be awesome once the newer kernels and LLVM versions that they need are widely available. I am really looking forward to it.
> The candidate can't remember what the "str" type is called, or how to find substrings in a string, or the difference between "==" and "is" for objects. They ask you to remind them if "join" is a method on sequences or on strings. They write "length()" when they mean "len()".

If you're going to disqualify people for these kinds of errors, you're going to lose a lot of great and experienced candidates, and only hire the ones who have taken considerable amount of time to practice memorizing library functions and language quirks for whiteboard coding.

At any given moment, I can probably go back and forth between 2 or 3 languages.
I can probably "whiteboard code" in one language only.
Anything other than that has a few days of ramp up until I'm back to where I used to be.
This doesn't mean that I don't know a certain language. It means that in order to be a good programmer, my brain needs to temporarily forget a lot of things. Especially if I go back and forth between different languages.

Memorization isn't proof of internalization. Especially when you're neglecting the fact that programs work with IDEs, and are used to typing code with keyboards (and not pencils and whiteboard markers).

Someone mixing up length() and len() doesn't prove he isn't experienced or productive in python. It proves that he isn't experienced or productive in whiteboard coding.
Why Does Windows Think My Keyboard Is a Toaster? (2014)
I think that's basically how all the X11 screenlockers work, sadly.
I upvoted the submission, mainly because Debian doesn't get the publicity and the recognition it deserves. Debian deserves a little love once in a while.
Keep in mind that the Middle East is increasingly less important to global oil supplies, particularly the US.
Very similar things to today (just with a few of them mundane things removed):

Sports/Prostitution/(non-sexual paid)Companionship/Parenting/Baby sitting/Dog sitting (will never be automated).

Gambling/Consumption (will never be automated). With a large basic income compared to cost of living ratio, these might actually be people's day-day 9-5.

Politics/War (because ofcourse that isn't going anywhere in the next 35 years) - By 2050 we may see the first AI Senators though.

Creative endeavors: Dancing, Stage Performances, Movies, Books, Music (while computers can write, or make art, potentially any of the above, there will always be a higher appreciation for human creativity).

Writing and maintaining all this software (until that is automated - not by 2050 though).

Data-analysis to ensure these ML systems are doing the correct things (until that is automated - not by 2050 though).

Apart from that my bet is on academics. Humans will be full-time students (my personal career of choice). Hopefully more scientific research/advancement. Primarily theoretical endeavors, like philosophy, mathematics, theoretical physics (i.e. abstract thought - things that are not exclusively based on previously aggregated data).

Exploration/colonization. We are still the most adaptable machine/energy efficient machines (it is still unclear if curiosity can be built into a machine's "personality").

Note: I'm sure there will continue to be Amish 19th century societies, alongside the new Amish 20th century societies that will start to pop up.

Note: This is all given that we do not destroy civilization first. Automation / increased productivity isn't all good! It doesn't just mean you need fewer people to make more money. It means you need fewer people to attain your goals. Even if your goal is to hurt other people!

Note: This is also given there is a separation between humans and machines in 2050. Given the adaptability of our brains, it is conceivable to give it new input/output streams. For example, what happens if I were to implant a calculator-chip into my brain? Once I was trained to use that implant, could I multiply/divide arbitrarily sized numbers as quickly as a computer? If so, instead of implants, can we collectively edit the human genome to have these bio-chips grow into our bodies i.e. such that no future generation has to worry about "implants"?
It's hard to say what he was trying to accomplish, but he probably could have written something like this.

auto index = std::distance (begin(replicas),
std::find(begin(replicas), end(replicas), my_ip));
return (replicas.size() == index ? -1 : index);
I do the above as well with 1 addition, any of the virtual tabs on my remote host can also run a screen themselves. To control this I use Ctrl-Oo to control the outer screen and ctrl-a for inner screens. This is useful when you have a remote dev server for a particular app and want need multiple connections to it, such as running nodejs server and tailling the output in one shell while using the editor in the other. I only started using this recently but it has worked very well.
You highlight my exact point: To you design is purely functional. To the overwhelming majority of people it isn't. That's the reason Google's Design initiative (Material Design) was started in the first place. Good design practices across all Google Services.

You want bad design, try most of the AWS tools. You can have both functionality and appeal. Pretending they are mutually exclusive is silly.
3d Math sucks sure, but you can't just use an engine and expect to not have to deal with it. It's just the reality of the situation. Also I'm not denying the volume of work gone into Unreal, but I am saying that roll-your-own approach is still possible, because many of Unreal's features are available online. It's just it's up to you to integrate it all. Of course writing a C++/OGL renderer from scratch is not nice, I've done the same myself and I promised myself never again :-)

These days C# + Monogame solves all my Language, API and Platform distribution problems and allows for fast iteration during development.
The absolute best way to keep yourself running is to find a race, sign up for it, pay for it and put it on your calendar.

I've wasted a lot of money thinking this way. Unless you're cash-strapped and it meant a lot buying that ticket/software/tool/book/etc, you just shrug it off and move to the next target. Money doesn't buy discipline. YMMV.
2) A little bit of stretching wont hurt, just don't do it too extensively. Stretching relaxes the muscles and increase range of motion, witch can have a positive effect on your running. It can also help the muscles "warm up". If stretching was so bad, you wouldn't see elite athletes do it, or cats and dogs.
>Statistics jargon will sadly not make AIXI work. It's problem is very deep.

It's not that deep. It's, at worst, dealing with the Curse of Dimensionality because it has no notion of randomness: when the inputs it receives are noisy, the prior probability of Turing machines with the noise bits pre-encoded will drop exponentially with the length of the noise. Hence why compactness and other assumptions about the real-line tend to help in real-world statistics: they make it easy to notice noise and operate with imperfect precision.

Philosophy jargon about "self-awareness" isn't necessarily going to yield more insights than it always has (ie: Chinese Room, ie: very little).
Maybe this is a gross over-simplification, but isn't the tl;dr that VLIW architectures require significantly smarter compiler backends, and compiler writers were having none of that?
Naive questions to people in the know: is it the case that ebpf/bcc are the standard for Linux tracing? Are they the Future(TM)? Or is the long-term vision a pluralistic world of Linux tracers?
I cannot recommend Hal Higdon's programs enough. He has free training programs for every level and various distances. We used a modified version of the advanced program in high school XC and won state championship twice in a row.

5K: http://www.halhigdon.com/training/50932/5K-Training-The-Most...
As for learning to land properly: some training barefoot can do wonders. Only the most stubborn people keep slamming their heels into the ground, when there's nothing at all to cushion the blow.

If you want to get into barbell exercises, get a coach or at least look for good guides online (or in book form). Don't do half squats.
Here is another example:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811273

https://bugs.launchpad.net/ubuntu/+source/nethogs/+bug/15433...

It doesn't work at all and bug is fixed upstream, but fix only goes to unstable.
I did not say that. You did.
Yes. But xscreensaver only use straight xlib to paint any UI elements. JWZ's argument is that this reduce the chance of bugs vs using the likes of GTK or Qt to draw password prompts etc.
I got i7 2600K @ 5Ghz with water cooling. Very hard to find replacement. Test run 16.05s
Isn't democracy the rule of advertisers?
If they implement dri, alsa and evdev (without subtle implementation bugs), then Windows would be a decent development platform for Linux games and such games could run on both Windows and Linux. If Apple joins the party, it would be write once, run anywhere. :)
And at least OpenSuSE and Slackware just patched the warning out already -- probably after getting hit by it in the past.

See for example the patch in Slackware:
https://slackbuilds.org/mirror/slackware/slackware-current/s...
Ok, first I am always in awe of people who have the skill to disassemble, fix at the component level, and reassemble modern electronics. I am also not surprised that both the independent repair folks get told they aren't as good as Apple, and that Apple isn't doing anything more or less magical in their repairs.

I do however take a bit of issue with generalizing from one or two instances. Just as there are "bad" independent repair techs, there are no doubt "bad" Apple repair techs. And bad techs make sloppy repairs, period. The reality is that the "best" your electronic device will be, is likely just after it comes off the assembly line and passes QA, that entire assembly process and the components used are tightly controlled so you get the best possible outcome. Rework inevitably it hard on components, traces, and often has to use materials that differ from the ones usable in the original manufacture.
I don't know if it is a "really bad" idea. I've run stacks on both AWS and GCP, and used both RDS and CloudSQL. They are good solutions and I definitely agree that looking at them first is sensible. They will fit the bill for a lot of applications. However you can get a pretty high level of fault tolerance using kubernetes services mounted on persistent volumes. You don't get all the advantages of a containerized solution but you do get dependency management and fault tolerance.
> There was never any runner's high, just excruciating pain.

That's pretty normal. I run a lot, and runner's high is a very rare thing for me to experience. I think most people confuse it with the sense of accomplishment one often gets after a run.

I've only felt a real high after very hard workouts. Very hard workouts. Workouts where my heart beats hard enough to break capillaries in my lungs, and the aerosolized blood gives a metallic taste.[1] The high feels like a weird mix of THC and opiates, and takes a couple of hours to wear off. During that time, it's definitely not safe for me to drive.

I like to run, but honestly, I think enjoying running is a little masochistic.

1. Vulnerability of pulmonary capillaries
during severe exercise: http://geoff.greer.fm/files/Vulnerability%20of%20pulmonary%2...
It needs the equivalent of the PC desktop environment. An abstraction that makes sense for how to interact with it, and a way for it to interact with your surroundings.

Maybe IoT plus some connectivity / control standard similar to DLNA would make for a good base, where for example you could look at devices and bring up their menus to control them.
That's a bit harder to read isn't it? I think finding the location in first line and using distance in the ternary operator makes it more readable.
Don't listen to music while training. Especially not as a beginner. Relax. While running.

Personally I think some form stretching is useful - just my personal experience. I'm having a break for it at around 2km.
You should flag stories like this. Lots of users did, which is what buried it.

If there were fewer comments, the software would have killed it as well (i.e. closed it to comments and made it visible only to users with 'showdead' turned on in their profile). But we don't do that to ongoing active discussions.
Whenever I see an article like this, I think of Michael Crichton's "Why Speculate." [1] It's a fantastic read, and really helps put speculative pieces like this in perspective.

[1] http://larvatus.com/michael-crichton-why-speculate/
In the cases of Germany, Japan and other European countries post-WWII, I'd argue there were three factors:

1) An overt plan and programme to erase and supplant the then present nationalistic cultures (particularly in Germany and Japan)

2) Military superiority and occupation

3) Gradual economic improvement, due to significant US aid and technical advice (the latter was particularly important for Japan)

The first reason is the most important, and probably the most politically unfeasible now. You have to remember, WWII propaganda was intensely focused on de-humanising the enemy and de-legitimising their ideologies. The public would have been very supportive of efforts to stamp out Japanese and German culture, and 'give the savages' something better.

https://en.wikipedia.org/wiki/Denazification

https://en.wikipedia.org/wiki/Occupation_of_Japan

https://en.wikipedia.org/wiki/Marshall_Plan#Effects_and_lega...

'On September 6, U.S. President Truman approved a document titled "US Initial Post-Surrender Policy for Japan".[10] The document set two main objectives for the occupation: (1) eliminating Japan's war potential and (2) turning Japan into a western style nation with pro-American orientation. Allied (primarily American) forces were set up to supervise the country, and "for eighty months following its surrender in 1945, Japan was at the mercy of an army of occupation, its people subject to foreign military control." At the head of the Occupation administration was General MacArthur who was technically supposed to defer to an advisory council set up by the Allied powers, but in practice did everything himself. As a result, this period was one of significant American influence, having been already identified in 1951, that "for six years the United States has had a free hand to experiment with Japan than any other country in Asia, or indeed in the entire world."'

It should be noted that MacArthur pursued pretty humane and rational policies for the most part. Also, on the technical advice side, see: https://en.wikipedia.org/wiki/W._Edwards_Deming#Work_in_Japa... . You can see the seeds of TQM or the 'Toyota Production System' in Deming's management philosophies.
Wait, wait, did you say incremental compilation? As in, instantaneous compiles of individual functions like LISP or my old 4GL? Or cached, one-module-at-a-time compilation like most 3GL tools? Really hoping it's the former.
http://gizmodo.com/5902625/tupac-hologram-wasnt-a-hologram
I wouldn't move from a package system to an "everything has to be statically compiled" system. But it would be a nice option to have when most of the software in your distro it's ok but you want to run some app without upgrading your whole distro/OS.
The dignity of work is a Protestant myth.
This is solid advice! Learned some of 'm the hard way haha.
You did a nice job on this walk-through, so thanks for the effort! I was interested to see that you ended up in the same place I have in the past when deploying databases to kubernetes clusters. A container mounted on a PD is a bit of a hybrid but it works well in practice. Hopefully something like glusterfs or flocker will end up giving us a better way to manage and deploy data volumes.