I've only been using Linux for ~2 years. and funny enough I've already experienced the same thing. The first 6 months using Linux was just trying every different distros/windowing system combination possible. When I finally found my most optimal setup, they changed it into some horrible thing called Unity. So for a short time I went back to Windows, until I lost my mind over loss of functionality, and came back to Linux-land.

The second most frustrating thing is lack of decent graphics drivers. It took me weeks to figure out the optimal setup for the stupid nvidia optimus card.

I'd love to recommend Linux to my friends and family but I can't until they can do things like run Photoshop, play video games, and not have to use the command line when things go horribly wrong.

I emailed someone from project honeypot about this same thing. They said they would setup a service where people could submit unauthorized login attempts automatically. (right now my honeypot just emails the result of logwatch --service sshd to an account)

It it useful information. I've used it to contact some providers (e.g. aws, linode, etc.) about the machines making unauthorized attempts. Usually it's from a server hosting a website that hasn't been updated in years.

Thank you for posting this. I've been programming JavaScript since 2007, and it's the only language I've ever really took the time to understand. So I can't comment from your vantage point. But what I can say is that once I had a full appreciation for JavaScript inheritance, first-class function, and the other things that make JavaScript great, it has been extremely easy to work with. Of course there are parts that will kill you if abused, but doesn't every language?

I won't disagree that the majority of web developers do things like load jQuery, before they even know why they need it. Usually because they're a novice trying to create a blog for their cousin and never had any actual web development experience. But please remember that not all web developers are like that.

When used properly JavaScript can enhance the overall security and experience of the site. For example, I like to SHA1 my user's passwords before submitting them to the server. Then I'll SHA1 that with a random seed and store it in the database. Or I'll add simple encryption algorithms to encrypt sensitive data. Of course it all runs under HTTPS, but never hurts to have a little more security.

Unfortunately the masses of web developers who "have gone suck fucking heavy" with JavaScript drown out the few of us who know when and how to use it.

What you're not taking into account is the complexity of State laws. States have a wide range of gun regulations that vary greatly. Let's look at Gun Homicides specifically. In California, which is the most restrictive State, is the 4th highest at 4.82 per 100,000. While Utah, which has some of the most lenient laws, has 0.93 per 100,000. If you take the time to graph out all the data you'll find that there are States with very restrictive gun laws, which have both high and low death rates per capita. Same with lenient States. What you'll find is low statistical correlation between gun restrictions and gun deaths.

In the end the statistics plainly show that it is impossible to say either way whether gun restrictions prevent deaths.

This is hardly going to affect Google. DNT basically says you can't be tracked by third-party cookies. Meaning, a third party can't set a cookie on your browser from some other website. Since Google can set a cookie on your machine when you use their search engine to find something, it's not in violation of DNT. And if you're logged in to your Google account, they can still cross-reference all your search history, +1's, etc. to get you personalized results. It's mostly going to affect companies like AdClickMedia.

No straw-man here. You're original comment was just all inclusive. All you said was "supporting code [...] necessary to run". So you would have to include all supporting code. If you had excluded OS level instructions, then I wouldn't have had a problem. Because if Tron had been written in Java, you would also have to include all the source for the JVM. Now, a C level program that compiled down to machine code, then cool. But you didn't specify the scope of "supporting code".