I think a big advantage of a framework is that the team(s) don't end up arguing over architecture as much because the framework made those decisions for us. Also the framework has a proven history of this architecture working well for xyz problems. Also it makes finding compatible talent much easier. If you're using a framework, finding someone who has worked with that same framework for years makes it a safer bet that they will start being useful quickly. If you have your own bespoke system, it could be years until a new hire feels comfortable with the existing system's quirks and nuances and stops breaking things as much.
This is what has me excited about Rama. I was very into the idea of event sourcing until I realized how painful it would be to make all the tooling needed.
More complicated in what ways specifically? I think the relevant thing is wether building an app with Rama is more or less complicated. Rama may be more complicated than mysql in implementation, but that doesn't affect me as a developer if it makes my job easier overall.
Like I have a bachelors degree in engineering. Is that intermediate or advanced? I feel like saying my science knowledge is anything beyond intermediate is a bit of an overstatement personally.
JS core (that's worth knowing) is pretty simple. My mental model is basically there are primitive types, arrays [], objects {}, and Promises. After that, you basically just have to understand the event loop and you're good to go. Then there's other special things like async/await, spread operator, etc. Among programming languages, it doesn't have THAT many things to learn at its core.