Yes.

Superficially, `do ... end` blocks look like English, because they are English words. On the other hand, they don't really correspond to any real grammar construct of the English language. They live in the the uncanny valley where you try to read it like English, but you can't actually read it as such. For some reason, the use of keywords like `def`, `defmodule` or `defmacro` doesn't bother me as much. Maybe because they are not block delimiters?

In my opinion, braces, delimiters or parenthesis create less visual noise than endless cascades of `end` keywords:

    def f(x) do
      ...        
          end
        end
      end
    end

There are other block keywords besides `end`, which serve no purpose other than simplify some keyword list arguments at the cost of higher complexity.

In general there is too much syntax sugar for things that don't really benefit from it.

Parenthesis in function calls are optional in some places but not others, which creates some unnecessary confusion.

The syntax for anonymous functions is

    fn arg -> do ... end

The `end` keyword is strange and I keep forgetting it (that's more a problem with me than the syntax, I know).

The language is subtly whitespace sensitive in some places, while being mostly whitespace insensitive.

Macros can't take a variable number of arguments, which leads to the proliferation of Special Forms (it's a kind of macros that is treated as special by the compiler) which could perfectly be macros if it weren't for this limitation.

For a situation where this causes problems and requires some extra weirdness in what should be a simple DSL, look at this Github issue in the new testing library scheduled for inclusion in the standard library: https://github.com/whatyouhide/stream_data/issues/21

Not the OP, but I share the opinion. I strongly prefer a precise syntax over ones where parens are optional, but required in some circumstances, etc. I don't like Ruby's block syntax at all. (Incidentally, I wish Ruby had better first-class function support instead of blocks.) I don't like "end" littered everywhere. I find the `=>` for hashes/dictionaries to be annoying, given how often I use that data structure (granted, I now mostly can do `{foo: :bar}`).

There're other things I don't love, but that's a good chunk. Philosophically, I prefer explicit code to implicit (so, Rails is out). And I prefer functional programming to OOP in general, and find that Ruby greatly favors mutable OOP. I've had a tough time navigating around the Ruby parts of most code-bases I've found, largely due to the implicit nature, and annoying language features that allow clever generation of methods in a way that makes them impossible to search for (delegate ... prefix: true for example).