...and this is why Political Correctness is a cancer to all sentient thought, and a bane to the software industry.

I get that people should remain mostly civil, but freaking out over pronouns? Grow the fuck up. Now.

I bet his editor of choice is TECO.

You know... We could have some sort of Rust-language forum HERE...

Okay. I've never been a big fan of Lisp, but I thought this was pretty cool.

...even if the result isn't so much as an interest in Lisp, as a paradigm shift for solving problems...

Heh. If they think Vim is difficult, wait until they find themselves in the middle of Emacs...

I'm just gonna pull my Apple IIgs out of mothballs.

I wonder if it'll still boot up after all these years?

Of course, this point may have been brought up in one of your sources. I didn't chase the links.

Anything that's not on the list seen from the listed sources can only be considered as "hobby languages", because they have minimal or no practical applications outside that of a hobby. Therefore, I would consider not bothering to learn them unless you want to have fun.

I think that would depend on where you want to work. If you want to work for some companies in Finance, it might be a good idea to be familiar with COBOL, as some of the bigger corporations (read: Banks) have a lot of time and money invested in their existing software and it's considered cheaper to maintain the software in its current state of stability than to risk introducing bugs by having it translated to something more current.

Although I've been around long enough to remember when knowing several dialects of BASIC was bragging rights, SamBone is correct: if one hasn't polluted their mind with the likes of BASIC, it's best to avoid it if at all possible.

Commercial use: License fee based on number of developers.

Non-commercial use: One may edit source and use it freely in projects. Images have attribution link embedded.

I've been using DirectNIC for my domains for years. $15 for each of them, with an additional $5 each for "information protection" that hides my name and address. Yeah, they're not the least expensive option, but I'm not parking on a couple hundred domains, either. The price is reasonable for what I want to do with them.

Not limited to Linux.

I would suggest that the description of ".tar" be amended as follows: Folder and files merged into one single file but not compressed (though one or more of its contents may already be); Directory information of the enclosed files are stored within the tar file as well.

one click on a remove button, and you're gone off the internet like you'd never exist.

At this point, I'm beginning to wonder if that is such a bad thing... I'm so fed up with these morons that get butt-hurt over the smallest thing that I want to move out to the middle of the woods somewhere, just to get away from civilization.

...then I realize I'm effectively addicted to the Internet.

Looks like the page that is linked is reporting the video is no longer available.

Your crotch and melanin content do absolutely nothing to aid your development knowledge, so don't bring it up. I. Just. Don't. Care. If you try to make me care, then I don't want to deal with you.

I thought this was the best part.

Interestingly, cyber-bullying is flat-out illegal in many US states. I interpret SJW CoCs as bullying....

This is pretty much why I think this CoC is complete BS. All I care about is whether the code does what it portends to do. I really don't give a rat's ass what the programmer is like in Meat Space. People are different. Fine. I get that.

Make code that works and doesn't rub social agendas in the face of the End User (unless, of course, that's what the software was specifically written for), and nobody should know or care what the programmer's kinks are.

I've been working on learning Ruby more in-depth than to write "Hello World".

If this "Covenant" is accepted for the core language, I will have several Ruby books up for grabs.

In all seriousness, no computer language should need a covenant of any sort that polices thought and speech. If they are concerned about rabbit trails and downright despicable behavior on forums, that's what a Moderator is for. Arm the Moderator with something as ridiculous as a "covenant", and all it takes is one bad day to get everything you breathe or type to be eradicated.

Come on, people. The ancient Egyptians did that with people they didn't like. Are we going to go back three thousand years or more, just because someone gets butt-hurt?

If my code sucks, say so. (I probably know it already.) A covenant requiring people to use nice words isn't going to improve my code. Tell it like it is. Be constructive. I'll learn.

I wonder how long it will last before Blizzard sends a CnD?

[Edit: changed DnC to CnD because my fingers are dyslexic.]

My personal opinion: learn both eventually.

More immediately, focus on one of the two, because there are a lot of syntactical differences that might be confusing. Which of the two you go with first would depend largely on what you want to accomplish and what your environment is using most of the time.

At my last job (a SysAdmin), we did almost everything in Perl, and it was Good. At my current job (not exactly SysAdmin, but close), I haven't used Perl at all. I'm more likely to use bash, and lately I've seen reason to delve into Python.

As others have mentioned, there's a lot of stuff out there already written in Python. Although you may not like the forced indentation (it's not a favorite of mine either), it does help to make the code easier to follow when looking at someone else's code. Looking at someone else's Perl code, in comparison, can be an exercise in futility.

As with almost any other language of importance in the unix realm, adding "#!/usr/bin/env LANGUAGE" (where "LANGUAGE" is your language of choice) as the first line of your script will do the job nicely once you've set the execution bit for the file, whether you're looking at Python, Perl, or (as some have suggested) Ruby.

For the work around for forced indenting, if you're looking at portability, you're better off just dealing with the formatting the way it is. You'll be glad you did.

Hope this helps.