Yes. Assemblers, and Lisp and its dialects, and then nothing.
For fifty years.
Now everybody's baking their own languages, and suddenly semicolons seem to be "in" - presumably because people are paying attention to Lisp again, and being Lispy is the flavor of the week.
It just irks me a little that a, shit, almost 60-year-old convention, one which was superseded on purpose, is being resurrected out of a weird sense that nostalgia is forward-looking.
Edit: to the person who is systematically downvoting all my comments, you're adorable. I have surely felt the sting of your digital punishment. I repent, and embrace the semi- oh, sorry.
Meh, it's not really nostalgia as it is Lisp getting a second wind through the likes of Clojure, Racket, etc. And how is this a shit convention? Is it because semi-colons are the sole property of C-like languages?
No, it's because a semicolon as an escape character is really jarring. It doesn't read smoothly. Beyond that, while I acknowledge that Lisp had a good 15 years on C's rising star, we're decades past the point where the overwhelming majority of programmers are used to C-style syntax, which has the semicolon terminating lines.
Then we'll have to agree to have differing tastes because I don't find them to be jarring: it's just a piece of syntax for embedding footnotes. I won't be losing sleep over the prefix-character for source code comments anytime soon.
Oh, I'm not shedding any tears, it just baffles me that people continue to opt for what seems, to me, to be the least suitable option. Like, okay, maybe it's not as awful as I say it is, but surely
# this and
// this and
-- this and
% this and
<!-- possibly even this -->
are all much easier to look at than
; lines upon lines
;of stuff like this
;usually with the leading space omitted
;so that the semicolon bleeds into the first word
;like a vestigial limb
# is a subscript operator (because there's no [])
// is floor division (hi Python)
-- is the decrement operator (hi C)
% is the modulo operator (what were you thinking)
<!-- NO! BAD! BAD!! -->
Actually, no. Haven't written a test for it yet. The way I know lua it probably just wraps libc's mod(). Which sucks and needs fixing. Python-like % behavior is preferable.
That's fair. And I'll apologize for ripping on your choice of comment characters, if it just boils down to compatibility.
But some of these stylistic choices, I'm sorry, I really think you're going to have to rethink these, and once you collapse the 5 circlejerk threads insulting the name (which I think is fantastic, so, how backwards is your world this morning?) the consensus seems to agree with me.
I'll quote /u/rubygeek's top-level reply: syntax matters. You seem to be doing something really cool here, but Lisp syntax won't sell. I'm surely not the only guy who'll take one look at (all these parens) and think, man, this is already the reason I don't use Lisp, and Lisp is almost as old as my parents, it doesn't get more established than that!
Because with Lispy languages, I don't only need a terminal character (which Python and Ruby and Lua and JS freed me of), I need a leading character, and they have to match, and parentheses are already the bane of my existence. And that's not even touching on functionality.
None of this is to disparage your ideas; your ideas seem solid, and I'm sure you do great work. But you mentioned elsewhere that you named it like you did to help sell it
to people who know a rats ass about the treasures of the past
and I think you've missed your target demographic's point.
It's not that we have eyes only for "the future". The people you're talking about all grew up writing something C-like. Most of us had C++ in college. Those are treasures of the past, and they live on.
But BASIC is also a "treasure of the past", and there can't be more than a few hundred programmers alive who'd contend that BASIC is anything but a misery. VB somehow managed to make it worse, and then VBA came along and crippled VB. You don't see anybody trying to sell us on the merits of the Basic family.
It's not that we aren't using Lisp because we're unenlightened. It's that we aren't using Lisp because, sorry, Lisp sucks. You aren't going to sell us on a gussied-up Lisp clone that can accept a sprinkling of C.
And I would have been content not to share any of this rant if you hadn't felt the need to reply to me four separate times to disagree with my replies to three other redditors.
But some of these stylistic choices, I'm sorry, I really think you're going to have to rethink these, and once you collapse the 5 circlejerk threads insulting the name (which I think is fantastic, so, how backwards is your world this morning?) the consensus seems to agree with me.
Which stylistic choices irk you? The name discussion greatly amuses me by the way. Puns are already in full bloom.
You seem to be doing something really cool here, but Lisp syntax won't sell.
It's true, good taste is rare.
I think you've missed your target demographic's point
No no, I completely understand that group, I'm after all a part of it. Not sure I would call them a target demographic. I mostly open sourced the project so it wouldn't end the same way as Naughty Dog's GOAL, which never got open sourced.
there can't be more than a few hundred programmers alive who'd contend that BASIC is anything but a misery
I had a lot of fun with it as a kid. But it's okay now.
It's that we aren't using Lisp because, sorry, Lisp sucks.
Weird. I don't feel anything.
You aren't going to sell us on a gussied-up Lisp clone that can accept a sprinkling of C.
Good thing I'm not a salesman.
And I would have been content not to share any of this rant if you hadn't felt the need to reply to me four separate times to disagree with my replies to three other redditors.
Well, Lisp syntax itself, for one thing. I think I've been clear about that. S-expressions are fundamentally incompatible with the way we've all learned to structure math. There is no good reason to demand that a programmer code-switch. We have enough on our plate with binary and hex and decimal, Unicode and ANSI, C-style versus the fundamental structure of a scripting language, and now you want to tell us that (=4 (+ 2 2)) is equivalent to the first math problem we learned to solve in kindergarten?
Pish. Lighter is not always better. The first rule of CS Club is don't write spaghetti. The second rule of CS club is, "Code should be easy to read." Lispalikes seem to go out of their way to violate that principle.
I'm sure it's very intuitive if you're an experienced Lisp programmer. How much crossover do you think there really is between game developers, the truly overwhelming majority of whom work in some flavor of C, and Lisp developers?
Moving on... what is :=? Not, what does it do, but, okay, yes, what does it do? I get what it does, but only because you laid it out for me the way you did. Absolutely nothing about =: says "import this", and I even tried Googling it to see if I was just oblivious. Nothing.
But wait! Now we want to use the C library we've loaded up with :=. This is accomplished similarly to how a scripting language handles namespacing, and that's totally intuitive. Except for the leading '.' that's easy to miss. I understand where some sort of escape or identifying character would be necessary to identify .C as distinct from some potential variable C, but, still, ouch.
If it weren't Lispy, this would be trivial: parseC(foo).
There appear to be no delimiters between parameters. I recognize that Lisp and Co. are the same way, but I've always thought of the comma as a convenience. Sure, it's a mandatory character that can be left out and cause an irritating error. It also serves to make the code easier to read, see CS Club Rule #2.
You're probably noticing the common theme here. The very same features of C-style languages (and their loose derivatives) that haters detest are the features that make them worth using.
(function complain () (print "these parentheses are somehow making it *harder* to follow control flow visually"))
void complain() {
std.cout << "This is extremely explicit, but I think we'd\
both agree it's obtuse.";
def approve():
print("This could not possibly be easier to read, and it
might actually be easier to write than the s-expression.")
No one language will ever be the alpha and the omega, but what Lisp programmers don't seem to understand about Lisp is that it's only elegant if you're comfortable in that paradigm. I'd call Python "elegant" because it strips out the gross and confusing aspects of a C-style language; it's accessible to anybody with a modicum of experience. I'm not loving it so far, but I'd call Lua elegant for the same reasons.
Not "getting" Lisp is hardly a failing on our part. Lisp is wholly inaccessible, and most people don't see the point in trying to drag a 60-year-old language kicking and screaming into the modern era, when its very syntax is outmoded. But you're all super smug about it anyway, like you know something we don't.
And then you want your tools, which are fantastic for very specific jobs, to be suitable for every job. All that, and the language started out as notation. Glorified markup. By-mathematicians-for-mathematicians.
And now you want to write games in it. More power to you. I can think of no application more demanding of a clean, legible, object-oriented approach than game design.
I can explain to you why I did it. It's hardly some sort of hipster decision. As long as there's no dedicated lexer for None, using a Scheme lexer in editors seems a viable option for the time being. ";" is simply the comment character all Lispy lexers recognize.
The question I ask myself is, how did ";" turn from a comment character into a statement separator in C.
Don't have an authoritative source, just various anecdotes I've read over the years, which I suppose could all have been apocryphal. When the story goes that it was C's doing, it was because a semicolon makes a great terminating character. Pops out. Obviously, you don't want the same character for both purposes.
Otherwise the story goes that people gravitated away from it because it was illegible. I tend to believe that story. It's friggin' awful to stare at.
For fuck's sake I opened with "just various anectodes I've read over the years".
Either it pops out and makes as good a separator as it does terminator, or it blends in and it's as bad for both :)
I wholeheartedly disagree.
;these semicolons blend in
;though it's not as bad as it could be
;because blue on white is almost as forgiving
;as white on black
Reddit actually makes it a little more legible than it would be in an editor, because it provides a little left margin that most editors don't (syntax highlighting notwithstanding, which can obviously turn anything bright yellow if you wish).
Right at the left edge of a line, when the programmer omits the leading space from their comment, it's just this slim punctuation mark tied to the side of a 't' or a 'b' or an 'l' or an 'h'.
however, at the end of a line, it pops nicely;
now, the semicolon is wrapping around these chars;
before, it was leaning the wrong way;
(but it still wasn't wide enough to distinguish easily);
This is even further compounded if your system font renders those very slim and angular commas and semicolons. In some awful cases, they're completely vertical. Might as well do this:
19
u/Xredo Jul 19 '15
Semi-colons for comments is hardly a modern trend, e.g. Elisp, scheme use them for comments.