How would you call a word/term that is thrown around without much backing reasoning? e.g. sometimes people say things like "this looks unscalable to me" or complex, magical, etc blanket statement seems close but it has a distinct meaning shallow dismissal also is close but I'm targeting the use of just one word. It bothers me because you can't just use a word and call that a piece of argumentation :)

great discussion as always, a bit more opinionated that it could have been, but that only means we did something right :) one thing I’d like to point out to people who is afraid of “a global state without giving a context”: • your data store is a global state • your I/O is a global state • your message broker is a global state etc. all these usually have mechanisms to deal with it: data stores have transactions, I/O is usually based on file handles and OS tooling, message brokers use internal queues, etc. no need to hide behind an illusion that you are not using global state because of hypothetical dogma you like https://github.com/stuartsierra/component to manage state and it works for you? great! https://github.com/weavejester/integrant? even better! https://github.com/juxt/clip? all the power to you! for the last few years we have built not one, but several large systems with https://github.com/tolitius/mount that are happily living in production and helping humans to live a better life. so our experience is as good as yours as to strong opinions, don’t let them discourage you, especially if you are a beginner. start with nothing or go try many, it all depends on how you learn. Clojure community is so tiny and all this “strong opinions” about a library just make it even tinier I propose we grow vs. shrink

From my experience, leiningen, mount and compojure are much easier to start with rather than tools.deps, integrant and reitit. For the scopes of relatively small projects I make (focused on delivering useful features rather than engineering perfection or large dev team coordination), the “easy” things work just fine and save me from a lot of learning. When the projects make enough money to justify hiring a team of Clojure devs, surely we’d spend a couple of weeks on gradually improving the tooling and library choices.