Amazon and Google are acting like spoiled children, and behaving in a poor, customer-unfriendly way. However, this has absolutely nothing to do with Net Neutrality. If Amazon doesn't want to sell Google stuff in their store, you can go to Walmart, Best Buy, or literally a thousand other places to get it. If Google doesn't want to support Youtube on FireTV, you can use Roku, Google devices, or literally every single Smart TV on earth. You have a ton of options. This is an annoyance to customers, but that's it.

With Internet access, most people have one, maybe two viable broadband offerings. If your provider screws with you or abuses you, you have no recourse. They are often no alternatives. There is no market competition. Additionally, you may not even know that they're screwing with you (throttling).

Comparing Google and Amazon's behavior to Net Neutrality just muddies a discussion that already confuses enough people. Don't go grandstanding and getting indignant just to get clicks by trying to tie this into an important topic. It just pisses us off.

Also, neither Google nor Amazon have been big supporters of Net Neutrality in a long time. Both are big enough that they don't need Net Neutrality to protect them like the smaller players do.

There kind of is. Install Xubunt or Lubuntu, or install the respective desktop environments used by those projects. I'm running Xubuntu on an almost 8 year old NetBook with a 1.6GHz Atom CPU and, while I wouldn't call it fast, it's usable.

Ok, first of all, this is one of the dumbest "news" stories I've seen here in a while. It's really lame.

Secondly, he had to write python for this stupidity? From any bash shell:

while (true); do cat /path/to/song.mp3 >> /dev/null; echo "Another copy made." ; done

I think I actually lost intelligence by reading and spending 30 seconds thinking about how dumb this whole thing is.

I think I see the problem here. It's a perception problem. You've decided that you want Perl to be a "hack n slash" language, so you view it in that way, and only in that way. I think you're seriously shortchanging Perl and pigeonholing it to something that doesn't match reality.

"Why use Perl" if you're not going to write sloppy code? Because there's a huge number of things that Perl can do really well. For example, using Mojolicious, it can be a great tool for designing web applications. Using CPAN, it can do any number of things. Using Moose, it has Object Oriented capabilities that rival any other language available. It's fast, it's flexible, and it processes text better than anything else.

Also, I'd really like to see some evidence of your "perl almost directly encourages [ugly code]". No offense, but I think that's a bunch of crap. It perpetuates a stereotype that isn't based on fact, but prejudice. Take 10-20 minutes and do a little research on Perl. Not Perl as you think it is (based on outdated assumptions and incorrect information), but as it really is. Look at the Modern Perl movement, the push to get past the misinformation about ancient Perl, and the awesome new world of Perl.

It's a much different world than you seem to see. And, for the record, having written C++ and Java professionally in the past, I'd much rather maintain Perl code than either of those.

Have you actually written Perl?

I mean, no offense, but that's just silly. Maintainable code requires a specific effort in Perl? But it doesn't in other languages? Can you provide anything to back that up? I can add use strict; use warnings to my perl and still have less boilerplate code than an equivalent Java (or C++, or even Python) program.

Writing maintainable code, in any language requires some effort. Period. Perl makes it no more difficult than any other language, and offers more assistance than most (see warnings/strict/perlcritic/etc).

As for it defeating the purpose. . . well, I'd ask for evidence, but I'm really not convinced you understand Perl to an extent that you could provide a decent answer. Maybe I'll ask the two co-workers who are maintaining a 6 year old, 60k line perl application at work, see what they think. See if they think Perl is "suited for the task". Last time I talked to them, they seemed to be thoroughly enjoying it, though.

Agreed. Cookwise is a *great* book. And for those looking for a little more "geek cred" for her, Shirly Corriher has guested on half a dozen episodes of Good Eats, particularly earlier ones. Fans of Good Eats will appreciate her book, as will anyone who wants a better understanding about cooking.