baroque

Git is conceptually simple, but has a baroque interface.

Writing about how it completely blows one's mind and takes you to this baroque, fluid land of programming literacy.

As a programmer though it's hard to feel much enthusiasm for such a fragmented, baroque, and inadequate toolkit.

But in the aggregate, they can leave us with something that is baroque, off-putting to the uninitiated, and hard to maintain.

Common Lisp kind of does; it's pretty baroque, but if you look deep enough, you'll see it's way behind the systems offered by ML derivatives, Scala, or Haskell.

Because of the complexity/sophistication of the software, the rules on SE/SO are far more baroque than the rules on Usenet ever could have been.

Having said that, I don't think anything in the JS world has reached the baroque complexity once regarded as normal in the enterprise Java world.

The perfect coupling of an average biological agent, and a bubbly, baroque piece of antique Lisp technology.

For instance, there's no 'funcall, 'apply, and sharp-quoting everywhere, and no powerful but baroque object and package systems deeply integrated into the language.

Unlike GPUs which have baroque memory access restrictions and many performance cliffs, this is a much more familiar SMP architecture with a unified coherent cache hierarchy.

I understand that other modern frameworks like Angular and Ember "make sense" as well, in that they're current best implementations of well-understood best practice, but from my outsider perspective, it looks as complicated and baroque as Catholic theology.

The vast majority of commercially significant apps are built in relatively baroque and ugly languages like Java and C++.Personally I think that the ability to define your own language constructs is ultimately a lot less useful than things like rich libraries and robust tooling and I'm still waiting to see real-world proof of the advantages of programmable programming languages.

Instead the latter seem more interested in building large, absurdly complex, baroque architectures to solve simple problems.\nMaybe the "every byte and clock cycle counts" attitude might not be ideal either for all problems, but not thinking at all about the amount of resources really needed to do something is worse.> how much layers is too much layers?Any more than is strictly necessary to perform the given task.