pmr_

72k can keep you alive on sub-standard living conditions, but it will not keep a team of 6-7 talented programmers and artists alive for very long. Not even for way below market pay and working in a garage.

And a single person just cannot turn out something close to a AAA title.

How do you know that? Have you had any practical experience with a large code base using new style (e.g. post-C++11) Concepts? People have been using Concepts in some form for a very long time and even properly documented they can still be a major hurdle to less advanced or interested users.

The Wikipedia article linked in another reply to parent confirms that. The months in which the worms were harvested were named after the worms.

I just went clicking randomly on Vimeo links and I didn't find a single auto-playing video.

You are right about YouTube and I actually think they should handle visitors that come from outside YouTube differently than visitors from inside the site. In the first case auto-play is annoying in the second it is what is wanted.

As others I had a totally different expectation given the title. I thought it would be a piece about how Wikipedia had some message or lesson that we should listen to. I think the author had no bad intentions and what he build is probably worth looking at. I was just pointing out how a mistake in web design made me completely ignore this website because I felt it violated my control over my computer.

Why should I adapt my usage patterns to accommodate the shitty behavior of a few websites? Also, are you sure you are in position to tell other people how to use the web? I certainly don't think I am.

Starting to play sound without user confirmation is a default tab-close. I wont even take the time to look at it. Bonus point for not being flash that hijacks the browser shortcut.

That much should be clear, my (unfortunately) implicit question is: how can we instruct a machine to optimize for the very intangible things everybody seems to love so much about this chalk? What about the more subtle economic things (like signals of economic climate and value of quality).

I think the statement following this is much more important and interesting to HN:

> The tendency has become more and more prevalent under electronic auction systems.

While incidents like this are often used as examples of the failures of technocracy, I think the problem is elsewhere. A decision process has been out-sourced to a machine that is not smart enough yet to make a good decision. The decision might be good in a very localized and easy to measure sense (cheap), but lacks an understanding of other economical signals.

You are not quoting the part where he shows his benchmark results, analysis of the problem, and suggested solution. I don't necessarily agree with Linus' tone or choice of words, but what you are doing is far worse. I'm not even sure if you are trying to be sarcastic, but that does not even matter: You are not contributing anything either way.

Even if your tax is paid automatically you can still recover taxes but it is hard and the laws are confusing. In Germany a special profession with a state exam (Steuerberater) as well as special associations (Lohnsteuerhilfeverein) exist or have been created to help individuals. For self-employed or people interested in recovering part of their taxes using those services is almost unavoidable.

At first I thought "a build system which automatically figures out what to build and how to build it purely based on the source code" included figuring out library dependencies. It looks like I was wrong though and you still have to set linker and compiler flags yourself. I think actually understanding your dependencies (minimum versions, different build configurations and all) and handling them in a unified manner without too much special casing for the peculiarities. CMake already does this quite well, but there is still lots of room for improvement.

You are saying that you actually need to read and understand code you are refactoring. Hard to disagree.

I can't follow. The code I showed is already processing masterlist and decides if it should process masterlist[z].list2 for every z: 0..masterlist.length.

I fully agree that the code in my post is very bad, I took it from the article.