Little 'bout my age: far from that of B
Yet in my syntax, you will find some C
The way I treat vars, that is much like D
I do take objects, but I'm not like E
If it starts with F, you'll know it's not me
Now I challenge you, just what could I be
I guess this should be fairly easy for people who study computer-related stuff.
Update: some clues
As of now nobody has guessed the language I am thinking about. I understand that this seems to be quite broad and many languages can fit to some degree, but my thought is, if there are still many candidates, then you might as well make the rules(clues given in the riddle) stricter and screen the candidates down. E.g. some said that the "D" line refers to D having local vs. global variables, but so many languages do, so you might want to look deeper into, say, variable naming conventions (clue: just an example, nothing to do with that).
Also, here are some additional clues:
Age
The age is farther from B than all four guesses as of the time of writing.
How it treats vars
Think typing and stuff.
Even more clues:
Also think memory management.
Objects
Again, since few if any language is like E with respect to the object system, things remain pretty broad, so you may as well look at a certain aspect of it to screen candidates, more specifically,
the philosophy: E very strongly adheres to OOP.
also, I might need to clarify that
objects can mean anything, but I did mean it in the OOP sense: an abstraction of a value (or set of values) with specific functions that are owned by and can operate on it (methods).
One more, really big clue
"If it starts with F" is actually trying to suggest the first letter in the language's name is important.
With this one I probably made it too easy, though.
The explanation
So Chiel ten Brinke got it right, the correct answer is
Go (official site)(Wikipedia)
Little 'bout my age: far from that of B
Go was created in the 2009, just 7 years ago. The clue doesn't give a specific range, but at least one can expect no possible answer to be older than C.
Yet in my syntax, you will find some C
Go's syntax, although pretty special in the family, is largely based off C, with C keywords, curly braces, operators, etc. Also, although there isn't always a semicolon after statements, they are just implicit, it's perfectly fine to use semicolons like in C, and that would be required to separate statements when doing inline stuff. However, that still doesn't throw C++, C#, Java, etc out of the pool of candidates.
The way I treat vars, that is much like D
I stated in the extra clues that one should look at memory management and typing system. Now D has static, strong, inferred typing with automatic memory management (as in: delete vars when they are no longer needed). "Inferred" alone throws many languages out of the question, but since I didn't explicitly talk about type inference it is just a quite probable, but unconfirmed constraint. Automatic memory management filters out C++ and friends.
I do take objects, but I'm not like E
In the extra clues I said the language was not like E that it doesn't adhere strongly to OOP, so C# and Java are out too, as well as Eiffel which was one of the answers you can find below. Go doesn't have classes, but structs can have methods, so OOP is pretty well supported, but the language itself doesn't emphasize OOP.
If it starts with F, you'll know it's not me
In the extra clues, I mentioned that "starts" is trying to suggest that the first letter in the language's name is important. Now if you see that the riddle went all the way from B to F, and the first letter is important, it should be logically sound to think the language starts with G, the next letter in the sequence. That's not necessarily the way you should think, you can also say that it's Eiffel if not for the other clues. The other best candidates thus far, Rust and Swift, couldn't fit this.
So in the end,
The ones who guessed Rust and Swift did very well, they only missed the BCDEF-G clue. Also, kudos to Klaws for suggesting Deesel, the answer only misinterpreted the line about E (it was about objects, not variables).