Don't give up too easily on Lisp. It also has picked up various syntax which has leveraged people's abilities.
As an exmaple, the backquote notation. Without it, it would be very painful to write macros at just one level of expansion. There is tremendous value in being able to do `(a b c (,@foo)) and so on, and it is a character syntax, like infix.
The possibilities for adding notations to Lisp without disturbing its syntax are not exhausted.
In my own Lisp dialect, I have introduced a modicum of notations which make quite a difference:
obj.slot.a.b.c -> (qref obj slot a b c)
obj.bar.(method arg) -> (qref obj bar (method arg))
a..b -> (rcons a b) ;; construct range object
[seq from..to] ;; slice
(fun arg . rest) ;; dot notation with atom serves as apply
(. blah) -> blah ;; dot not preceded by anything reduces to atom
#"word list literal" -> ("word" "list" "literal")
`quasi @literal @{blah[3]}`
All such little things make the "little code" you write daily a lot nicer.It's understandable that coders might be put off by verbiage like (concatenate 'string ...) or (slot-value obj 'slot) or (aref array index).
You assume I gave up on it easily. I didn't. I simply found nothing important enough to keep suffer the syntax. Not because there's nothing of value in Lisp, but because most things of value have been copied by many other languages by now. I'm not saying that Lisp doesn't have value any more, but that what it provides that other languages doesn't is not sufficient to outweigh the inconvenience of the syntax to me.
> The possibilities for adding notations to Lisp without disturbing its syntax are not exhausted.
The problem with this is that while you can do it for yourself, until/unless it gains traction you still need to deal with the surrounding ecosystem too.
The syntactical decisions you make influence how you think about a problem as much as the semantic choices you make, and it needs to be a back and forth.
E.g. lisps homoiconicity fundamentally alter the freedom you have with respect to syntactic sugar (though I'd argue that it makes less difference than some want to think). If you leave the syntax considerations to the end, you will have potentially made semantic choices that constrain your syntax in ways you don't want.
This also applies in reverse.
You can't divorse the two.
The semantic concepts that made it into Ruby largely already existed, sure, but not the mix of them, and that mix is strongly affected by the syntax.
One effect of this interplay which I find a bit annoying (though I've looked long and hard for a solution that wouldn't be a grammar-nightmare), for example, is that while Smalltalk can (re)define core language features in a transparent way, Ruby can't, because while Ruby-style blocks can be very unintrusive, they are not invisible, so you can't simulate something like "if" or "while" without creating syntactic "noise".
These are conscious tradeoffs in Ruby - the cleanness of the core syntax was seen as more critical than retaining those features from Smalltalk. If the semantics had been designed first and dictated those features, then the current Ruby syntax wouldn't have been possible. We'd have gained some marginal utility, but we'd have lost readability.