xkcd

While, I normally would argue that a words meaning is rather important. But in the case of a command, I think that what it is used to do is far more important then it's etymology, to the point that it's meaning can be completely disregarded. Though it is certainly interesting to know the meaning (be...

Probably already mentioned but...
http://xkcd.com/378/

That said, I don't program on *nix anymore these days. But when I did I used nano (well actually originally pico), because it had the smallest learning curve. These days I seem to be using Notepad++ a lot.

I usually say "u-torrent" or "micro-torrent".

I realized something, that if it was "su do". That is program su with an option do. I would have pronounced it "sue-doo". But it isn't, and so I don't. When there is no space, I treat it as a single word, and the easiest single word for "sudo" is "sue-doe", no...

I use 1TBS or "the one true brace style", but with attached function braces. It is a variant of K&R. But you always add curly braces even around single statements. Basically allowing safe line insertion anywhere in the file.

I really fell in love with top bound ring college ruled notebooks after using standard ones for so long. They are overall much nicer as the binding doesn't get in your way and there is less chance of a bad tear.

I pronounce it sue-doe, because that's how I have always pronounced it, and I am not going to change the way I pronounce it just because someone dislikes the way I pronounce it. Have a nice day.

Yes, but they are still libraries. Just standard ones, rather then language constructs. Thought this is something of a grey area. I don't particularly like working with grey areas, as the arguments tend to become circular.

People referencing heartbleed as a failure of C is starting to cheese me off. Since they obviously believe that it wouldn't have occurred if it they had just used C++. Well let me correct you. Just because the standard C++ library includes a nice string container, doesn't mean it isn't vulnerable to...

Well "better" is always going to be subjective. Just adding a bunch of features doesn't necessarily make something better. The fact that C is simpler, in my opinion makes it better. Which fits well with a few programming philosophies. Such as the KISS principle , Worse is Better , and YAGN...

I don't think C++ is a superset of C. It is very close to being a superset, but it isn't one. In fact there is a whole wikipedia article on the topic. I should totally start using variables named new, catch, try, throw, using, this, private, delete, class and template in my C code, just to stick it ...

Okay... you shouldn't FFI with C++ then. I am pretty sure C++ varies with its call routines compiler to compiler, making dynamic libraries difficult to work with if not built by the same (or compatible) compiler. But that's off the top of my head and I might be entirely wrong, as I so often am with ...

Oh well, declarative languages are something different. Forgive me, but it sounds like you're saying that it's easy to learn languages that are pretty much the same as the languages that you already know. Yes, you're clever, that's exactly what I am saying. It just happens that most of the language...

Oh well, declarative languages are something different. But most production languages are imperative. I don't need any hands to count the number of times I have used a program that uses a primarily a declarative language. Heck, I can only think of one that uses a primarily functional language (that ...

A sad anthropomorphism of Rainbow Dash wearing a dark hooded shirt. I have no idea how I know it is Rainbow Dash, since I have never seen the show before in my life. But otherwise fairly cute.

8/10

120201₃

If my math is correct anyway.

Some kind of blurry sheep ball wearing some kind of leather hat behind a clock. I'm confused. I don't like being confused.

4/10

I would say this thread isn't completely relevant per se. A good programmer can get to know a language in an afternoon.

Which usually leads to us having a long laundry list of languages we know how to program in, or at least are fairly confident we could program in again with a short refresher.

This isn't a religious war, this is a Microsoft marketing campaign. We all know who the king of search is.

Also, I tried their blind test a few times in the past, and Google won fair and square, without me trying to "guess" which is which.

I am pretty much 100% self taught so my progression was a little strange...

BASIC
C
Bash
Javascript
Visual Basic
C++
PHP
Java
Lua
Fortran (T_T)
Z80 ASM
ARM9 ASM
C#
Perl (Never again)
Scala
Java Bytecode
AMD64 ASM
Python (a.k.a. BASIC 2.0)
Go

I grew up without a role model for my pronunciation of acronyms. I was a very avid young reader who was often alone in the library for many hours at a time. Therefore my pronunciations are whatever ones seemed most natural to me at the time (even if completely wrong). GIF = Like GIFT but without the...

I don't think that counts. That isn't so much a internal program issue as it was someone not properly checking their inputs. You can't claim for certain that the bug wouldn't have occurred if they had written it in C++.

Okay, I relent, there are a number of nice features in C++. I didn't realize people had such a hard time keeping their indexes within bounds of their arrays. I suppose without some kind of check, that you could get yourself into trouble without noticing it. C++ does have useful features. But speakin...

ahammel wrote:"Why do you need [language feature]? Why don't you just never make mistakes?" <- C programmers.

Or, you know, you could fix your mistakes.

Well you should never have a program that needs to access an array beyond it's known bounds when those bounds don't change. Though to be fair (to me), that was just an example.

I am a little behind on the posts, but using a vector in place of a raw array because its "often better" is just the problem with many C++ programs. If you only have 20 elements and you will only ever have 20 elements, the you really shouldn't be using a vector. Except many programs do any...

Funny ones. I stumbled across this one rather recently in some of my old code. /* I am so very sorry (future me), I didn't know any better. */ Another one by me. Right before a complicated function that converted pixels to and from a complex embedded format to RGBA and back. (Lots of bit shifts and ...

I generally use Eclipse, but then again I am something of an old salt with that IDE. So I managed to get it working with C/C++ rather easily. The biggest gotcha's with running C/C++ in it is when your Index(er) isn't properly setup (making everything display as an error), and your tool chain not bei...

There was no "C vs C++" thread. Despite being a classic debate. I am personally a C guy. I generally got sick of C++ at one point. It took me some heavy thinking to figure out why. I realized that if you write C++ code, you are expected to write C++ code. That means templates, classes, inh...

I agree, Waylander is the way things are moving at the moment. Though I wouldn't mind a system capable of delivering 16-24-32 bits per color per pixel. I know amazing applications like Photoshop can do this, but most systems are jammed in the 8 bits per color world (most image formats are like this ...