skysight-inc/HackerNews huggingface dataset:
This isn't super unusual for very old code.
Cool! What did you do to diet and eat better?
Ironic can be called story trolling then.

Not sure that it matters even if it is real though.

It's close enough to what you believe might happen. I see many more things that are even much clearer in terms of potentially being made up (even posted here on HN frequently) [1] that it reminds me of back in the day contests to see who could get 'Dear Abby' to answer some letter (that was something that was done by college students many many years ago).

[1] Always the same theme "here is something shitty that happened to me don't they suck what should I do".
Maybe one of the reasons demand for local programmers has increased is the strong protectionism exhibited by the Swedish department of labor. My application for a work visa for a summer internship in Stockholm was just denied because I'm "not experienced enough", although I have three years of relevant experience in the field and a year and a half of university education under my belt. For a three month internship.
Unfortunately it's not as simple as a UBI. Give the average person money without structure, instruction or necessity and they cease to be productive in any sense of the word. We'd ironically have less equality, with a minority of motivated individuals at the top doing meaningful work, and a large majority of entitled "dolists" with little dignity at the bottom.

Instead I'd propose guaranteed civil service that paid a basic livable salary, such as publicly funded infrastructure projects. But whatever the method, resources should be tied to productivity in some manner. Otherwise we just create a bunch of lottery winners, and many lottery winners sadly don't have the wherewithal to keep their winnings for long.
There's also a decent monoculture concern. Everyone running off Linux isn't necessarily really a good thing. We should strive to have multiple independently developed solutions to computing problems.
And 0.124 s with sqrt(n) and -Os & 0.02 s by interrupting the for... Let's go further than 100000 :)

664579 primes between 0 and 10000000
Time taken = 11.319
Introducing Base1
I don't think generics would result in a compile time slowdown relative to the alternatives. If you don't have generics, programmers work around it with code duplication or they work around it with dynamic typing (interface{}, but also the runtime support for maps and channels fall into this category). Not coincidentally, these are the two main ways to implement generics in a compiler.
Is the story that Go, as a simpler language, is able to compile to decently fast code w/ fewer compiler optimizations?

Sort of. But it's also that you're making bad comparisons. C++ has an include based compilation model and heavy reliance on template specialisation that means it'll never be fast.

What you should instead be comparing it to is Java, which is also a simple language, only slightly more complex than Go. However, that comparison is rarely made, because it'd show that compiling fast is not so special a trick ... Java also compiles extremely fast at every level, that's why it's possible to use a JIT compiler with it at all.

Given that "compiles fast" is Go's number one claim to fame, the reluctance to compare to the most popular compiled language is the elephant in the room.
Thank you! And please let me know of ways I can improve it. I already have a couple of ideas that I've indicated in the conclusion, but more the merrier. :)
It would be interesting to break down the US number by state. Here in Massachusetts, we consume a _lot_ of ice cream.
your right, my version number just went up while i wasn't looking :)

$ cat /etc/debian_version
8.4
I think that entertainers and therapists will be the absolute last. Ironically I think 'CEO' is going to be one of the first (although the biz dev and product design might still be human). Manufacturing with motor skills may also be in high demand for a very long time, because the human hand is a miracle. In fact I can see AIs and humans being quite symbiotic: they mine the asteroid belt, and build habitats for us, and in return we build them new and better bodies. Seems fair.
I don't (ever) link my own psychotic blog rants on HN (not because I value anything close to a reputation, but because I don't want to inflict my stupid on others) but I wasted an hour last evening on an exceedingly long tirade fairly congruent with this debacle.[1]

On topic though, nobody wants to develop the way distributions want you to - basically maintain branches of every release you make for the lifetime of the distros where you backport bug fixes but not feature additions. Very little software, even libraries, is ever developed like that, and it is part of the reason why Linux desktops are a Mess™. And practically, you often cannot even do this. Your feature additions will optimize code that your bug fixes interact with, and trying to keep them separate is an exercise in masochism.

The TLDR answer is the sooner we can get a community software repo with open signups that developers push new releases to that supports appstream / xdg-app infrastructure the better. Distributions can still freeze the world and maintain all the stability they want, but we need to also let developers take responsibility for their own software on desktop releases.

https://zannyland.wordpress.com/2016/04/02/software-rants-23...
If we're talking about databases specifically, it's either a really easy problem to solve that it's difficult to charge a lot for (i.e. just a Postgres/etc running, with some way of modifying the config), or it's really difficult and requires a lot of resources to get right (i.e. scaling to many nodes, still not really solved well in Postgres/MySQL).
Why was the Go compiler not based on SSA form originally? Isn't that kind of an embarrassment? All industrial compilers I'm aware of completed their transition to SSA ~15 years ago ... it seems bizarre that a compiler for a language started in 2009 wouldn't have been that way from the start.
Can you expand a bit on how you still end up with non-reproducible environments? Not that I doubt it! Just would like to here some details, or a specific example.
I think the problem isn't so much how you strike, but what happens after you strike: if you find yourself pulling yourself forward with your knee joints after you strike, then that could cause knee injuries (and pulling tends to happen more with heel strikes). The focus should be on pushing yourself forward with the back foot, not worrying so much how your foot lands.

I've had long conversations on this topic with a podiatrist, but it's still not certain.....
For what reason would it have been taken down like that? Is politics not allowed here?
It probably doesn't require a security clearance, but all Federal jobs require the employee to be a US citizen.
I like it. But today I got the message that the chrome has disabled it and that I should contact you and ask for extension to be published in the chrome web store.
It's called 'unstable' for a reason. New stuff breaks. Often.
It's not "common knowledge" especially for people who don't run, which is who the article is aimed at. It's also still a debatable issue. I'd say for new runners the key is to get into a routine and worry about stride only if it's causing you pain until you get to a more advanced stage.
Obama was all about "pulling-out" too, and yet it seems that the US is still meddling in the middle-east. At first I was in disagreement with the root-poster, and generally I am opposed to the entire notion of war and paying people to do it. But, on some other level I really wish that politicians would either just go all in or pull-out completely.
Eh, you cut off the second part of what I said.. What I mean is, if you go down the route of writing your own graphics engine, then everything Unreal has is available in bits and pieces for free online, but you have to have the know how to stitch them together - which isn't particularly hard, and something you should know if you are going into gamedev anyway as it's the basics.

Note I'm only talking about the graphics aka shader side here, not the whole engine.
I would recommend looking at NixOS. We're not perfect either, but we generally do a much better job at keeping our shit up to date:

https://github.com/NixOS/nixpkgs/blob/master/pkgs/misc/scree...

If there's something you need that's outdated, a fix is as trivial as opening an issue on GitHub, or sending a Pull Request with the revision and SHA256 bumped.
Right - I saw that.

The problem I have is that most people feel like theyre doing 'serious work' so they need a serious solution when the reality is that it really is just a small percentage of companies - not usually even successful startups, for instance - that require this sort of automation.

Mostly, it adds complexity rather than reduces it.

I know that sounds like we're getting into the weeds, but if you consider that most companies are taking on additional complexity because of this, it becomes a problem.
Why would being written in Go make anything easier to profile?
I didn't say busing for students, I meant take a bus with everyone else.
agreed it's a great career choice especially if a career is what's being chosen. simply "learn to code" as "literacy" is where things seem to get shaky.
but here's a counterpoint (I'm just thinking out loud here) : to an artist making street art using coding skills to build out pieces of the scene, coding is a tool. or maybe coding is part of the medium. but it's not a career in that case.
Spot on. I was always puzzled why some software just can't come statically compiled. I suppose not all apps can be distributed like that, but most of them can.

I can't even remember how many hours I wasted on trying to compile a new version of some program, just to learn the infinite tree of dependencies, newer versions of existing libraries required, build prefixes tweaking etc... Most of that time could have been saved.
Nope, it's accurate (and a shame). We've split up our SSL termination for this exact reason. Instead of doing SSL and HTTP/2 on our application servers themselves, we put a box with Debian Stretch in front of it doing just proxying and stapling on HTTP/2 + SSL. Since the box has just one very limited responsibility that's easy to test we can afford running unstable software at that point.
The willful ignorance of the assumption that everyone using your product is a happy, well-off individual with no sad/traumatic events in recent history is akin to the willful ignorance that nobody will try passing in a negative number to a method which takes an integer as an argument.
Go wins at compile time in part because its import system avoids a ton of the redundant work that C++ includes bring with them. So, yes, go would compile lot faster than C+l -O0, but that's a language difference, not a compiler difference.
Yes, in the mid nineties one of Delphi's killer features was super fast compiles. Partly possible due to a single pass compiler but it was just a very fast language to compile.

Really, most compiled languages except C++ are fast to compile. In the other thread I pointed out that Java compiles very fast, but nobody in the Go community likes to talk about that, it seems. Actually Java does have multi-tiered compilers, so the frontend is very fast as it doesn't optimise, and then the JIT compiler has a fast-but-low-quality compiler and a slower-but-higher-quality compiler, meaning you get the developer benefits of instant turnaround but the code still gets heavily optimised to GCC/LLVM quality in the hot spots.
The best way to affect this is to post more good stories yourself. You can also add a first comment to the thread explaining what you think is good or important about the story.
How to get quality content quickly
Personal swipes are not welcome on Hacker News.

If you know more, use your superior knowledge to teach people, not put them down. Explaining what can be improved—simply, without snark—would help many of us learn, and would likely evoke an interesting discussion from others.
Even if it wasn't life or death, they still determine the outcome of your physical well being, future and livelihood. Giving them access to lethal force with practical impunity is the icing on the why-give-them-so-much-power cake.
jwz here seems to be arguing that distros shouldn't be allowed to freeze his software, even if they do it themselves and maintain the branch themselves. He wants only current versions of his software shipped, and old versions disabled once they reach a certain age. I don't think this is an entirely reasonable demand, at least for open-source software.
That only saves disk space, though, not memory.
Heel striking is not really what we evolved for as you can only do it comfortably in heavily cushioned running shoes. If you run barefoot or in lightly padded shoes you are forced into a more forefoot first style.
Given that most academics have, almost by definition, previously prioritized their work environment over their salary, one shouldn't even assume that an academic receives an (immediate) multiple factor raise by making the transition.
Wrap up on build 2016
I've only been using Arch for a few months, but my mental model of AUR is that I shouldn't expect anything to work.

(this isn't out of frustration, I read early on that it was for sharing preliminary packages and discarded all expectations)
Ugh, there is so much wrong with this article.

First, the statement "More and more, "learn to code" is looking like bad advice." Okay, in the context of "it will guarantee you employment", yeah, true. Except that that's a straw man. Nothing will guarantee you employment. Will it make you more employable? Yeah, in pretty much any profession that doesn't entail pure physical labor, since even if your job description entails no coding, having learned to code will let you automate some things your competitors (including coworkers), are doing by hand.

"This trend is bound to increase" with regard to outsourcing: is it? Outsourcing as an economic model is based upon trade agreements and tax law. That can fluctuate. But even aside from that, more and more companies are learning that outsourcing is actually a bad idea; having development taking place in isolation from the business introduces new challenges. A different culture, different values, different schedules...outsourcing takes all the difficulties of working with a consulting company, and all the difficulties of remote work, and adds in even more. As this person even indicates, projects are just getting more complex. Those obstacles will add up.

Finally, as others have noted, automation can reduce the need of far more jobs than it provides. This is not a bad thing. What's bad is our perception that people must work to earn. -That- has to change (as others have indicated).
I agree with this, but there's one more aspect: you learn something. Deeply. "Oh, I didn't realize that would do _that_..."

It's also taught me just how much we can guess incorrectly the first time. It's a skill you can get better at. "Profile first" is a good heuristic, but "guess first, profile second, _then_ do the work" means you train yourself too.

I'm still very much a noob at this.
I am not even at an intermediate level of Python and I knew all of the content, either I am better than I thought I am or this cheat sheet is a joke. I'd say it's the latter.
> (a += b) == a + b

Solution: b == 0
No I think high speed trading bots that use sentiment analysis based on news articles is more likely to create skynet.
Location: Lahore, Pakistan

Remote: Yes

Languages/Framework: Ruby(Ruby on Rails), Python(Djnago, NLTK, Scrapy), Java(Android, Apache Solr, Apache Nutch, Spring ), JavaScript( AngularJS, Jquery )

Resume/CV: http://haidrali.com/blog/wp-content/uploads/2015/11/haider-r...

Email: alihaider907@gmail.com
Do you want Crappy Agile?
There's no policy against backporting bugfixes, it just doesn't always happen due to lack of developers. If upstream doesn't provide backported bugfixes, it requires someone else to volunteer the time/resources to do it. For some packages, companies sponsor long-term maintenance branches, or particularly interested volunteers take it upon themselves to do it. For other packages, nobody steps up to do the work, so it doesn't happen.

I've found BSD ports pretty similar (mainly pkgsrc is the one I use). Some are very actively maintained, and others are much less actively maintained. Resources are limited, so pkgsrc maintenance happens only to the extent that someone makes it happen.
Again, I don't generally disagree with you. But as our team is growing at my day job, I am finding more and more that we're getting bitten by some developer's "It works on my machine" or a random npm failure at deploy time. And this makes me believe that having a prebuilt (immutable, hermetically sealed) artefact that I can later deploy is the way to go.

Containers solve this problem nicely.

And once you're going down the container route, you need something like a Kubernetes to easily schedule and network them.

My personal site -- the one you're reading the article on -- is literally just a static nginx server on an old Linux box (with the files copied in by rsync). Even the curmudgeon in me now thinks it makes sense to use solutions of different complexity for different situations.
> Give the average person money without structure, instruction or necessity and they cease to be productive in any sense of the word.

Is there research that backs this assertion? It doesn't match my (anecdotal) observations.
Give the average person money without structure, instruction or necessity and they cease to be productive in any sense of the word

I don't think you have evidence to make a statement this strong. We have no idea what would happen because it's never been done before. I think you're projecting an idea you have of people on the margins of productive society onto society as a whole, and I think this is a fundamental mistake.

People are status-seeking - that's what people in groups do. Capitalist consumer society measures status in a large part based on how much money you can spend. Remove money from the equation and a substitute marker for status will be found. It could be power, art, popularity, charity, science - anything. What it is we don't know, but it will certainly be something.
The selling point to the provider would be that it increases stickiness with their clients - that's big - they don't have to charge more.
This one is available too, with 90° FOV: https://www.metavision.com
> Reddit doesn't send emails for comment replies, or for anything, pretty much.

You can get them as RSS, though, and there are third party tools that will turn an RSS feed into email. See:

https://www.reddit.com/r/ChangeMon/comments/32zmji/get_email...
Having used Gobolinux for some years now, i find the xdg-app thinking a case of shooting twee twee birds with AA guns.

*nix already have a mechanism called soname in place that allow versioned libs to live side by side. Gobolinux makes good use of it, along with symlinking, to allow multiple versions to be installed side by side.

You find similar, tho more elaborate, systems in place in NixOS/Guix.

xdg-app on the other hand comes out of the RPM/DEB camp, where there can only be one canonical version of every package installed at any one time. So to get around that they device a system where you basically build a new system for each and every "package".

What that effectively does is replacing dependency "hell" for dll hell (hello Windows).
To be fair, there are some limitations around stack maps that make certain things difficult (see [1] for an example), but I agree that there's nothing stopping them from just providing patches or feature requests to LLVM to improve stack map support for their use case (as [1] is doing).

[1] http://lists.llvm.org/pipermail/llvm-dev/2015-July/087832.ht...
So much bad advice.

(1) Actually it does matter how and where (relative to your body) you land your foot. Contrary to the article, many people do need to fix their "natural" form and/or get shoes that help them avoid pronation, both to avoid injury and to increase the enjoyment that will help them stick with it.

(2) Similarly, the article's advice about stretching is way out of date. It's now consensus that static stretching can not only reduce performance but increase chance of injury. The author weakly hints at some of this, but never actually recommends against static stretching like most would.

(3) Lastly, there's a pervasive assumption bordering on encouragement of people wearing headphones while they run. I realize there's a lot of controversy about this, but a responsible author would at least have mentioned that it's a safety issue as well as an aesthetic one. If you run all alone where there's no traffic - including pedestrian traffic - do whatever you want, but if you're running in crowded times or places it's irresponsible to deafen yourself. I've know runners who have both been injured and have caused injury to others because of this, so I'm not inclined to let that pass.

I'm sure many people could follow this author's advice and be fine, especially if they're young enough and slim enough that they've never had to overcome the barriers that face older/heavier runners. Good for her and good for them, but that doesn't mean her experience can or should be generalized to everyone. There are better sources. Just search for "beginner running advice" and pick anything, especially one of the articles from Runner's World. With all that was already out there - it's practically an industry - this one just doesn't cut it.
Common knowledge? If anything, the preference seems like a fad to me. Plenty of elite runners heel-strike.

I've been running for... a while. In high school, I was captain of the XC team. I finished 5th in the state and our team won the state meet.[1] The spring after that, I ran a 4:18 mile and a 9:07 two mile. In college, I competed in Division I NCAA XC. None of my coaches cared that I was a heel-striker. I've since switched to forefoot, but noticed no difference in times or injuries.

If you're just getting into running, forefoot will be murder on your calf muscles and Achilles tendon. As the article says, It's best to just go with what feels comfortable. As you run more, your form will become smoother and more efficient.

1. 2002 Washington state AAAA boys results: http://www.jcrawford.net/boys4a02.html
You could have a great job until you hit about 37. At that point no one will hire you because your now officially an old fart. My company is guilty of this as well. We had a guy come in the other day and interview for a NodeJS position. He was about 40 - 50 years old. Everyone was wondering why this guy is even still in the game. At a certain point software developers are expected to move into management or more of a architect role. Software development is a young man's game.
First-mover is an advantage, sure, but it hardly means that anyone who isn't first to the gate is wasting their money.

Anyway, I see downthread that VonGuard has made the silly claim that "Hololens can do everything Magic Leap is supposed to do", so I think it's safe to say that the "wasting money" thing is just a throwaway line that's not based on a lot of actual knowledge in the field. I feel kind of trolled.
Not linux but close https://en.wikipedia.org/wiki/Xenix
More charitably, he thinks the distro choice to freeze something should result in 0 headaches for him.

The idea that the freeze should be done without carefully taking responsibility for it is probably a pretty stupid norm, so I can understand the lack of patience.
Is the wink because of the 502?
The longest I've ever run in one go is 6 km. There was never any runner's high, just excruciating pain.

For a good fraction of the population, running is fucking awful.
Sign up and deliver a good tech talk.