Unfortunately, javascript web frameworks build on top of the javascript APIs browsers expose.
If you're starting from a set of APIs that are too complex for someone to keep in their head, it's hard to end up with a much simpler API.
Especially since people do use a large portion of the web's APIs.
For example, "prevent", the thing in the parent comment, is needed if you use javascript to submit your forms, but isn't needed if you have a form that is expected to be submit by the normal browser mechanism.
Webframeworks rarely are prescriptive to the point where they can default in one direction or the other on that point.. and thus we end up with another option.
That repeats many times over and we end up with a large API surface.
If you're starting from a set of APIs that are too complex for someone to keep in their head, it's hard to end up with a much simpler API.
Especially since people do use a large portion of the web's APIs.
For example, "prevent", the thing in the parent comment, is needed if you use javascript to submit your forms, but isn't needed if you have a form that is expected to be submit by the normal browser mechanism.
Webframeworks rarely are prescriptive to the point where they can default in one direction or the other on that point.. and thus we end up with another option.
That repeats many times over and we end up with a large API surface.