Using an API requires client-side JavaScript, which a significant proportion of users still don’t have enabled by default.
This is not accurate. ES5 is widely supported. It should also be noted that those running IE 8 or lower are probably not interested in using Codidact. We can’t support everything - that’s simply not worth the development effort.
I am not opposed to generating static HTML. But it shouldn’t be the “default”. We should first build a REST API and then - eventually - search for a way to generate static pages.
I did not intend to start a discussion about changing the entire tech stack, but at the very least Razor.
@jbis I might want to join you. I think that the Codidact documentation & specification is certainly good, but I don’t like the direction the implementation is taking.
I think we should have multiple implementations. A NodeJS dev will probably never contribute to the C# implementation and vice versa. So they should be able to each try on their own, and in the end, we can chose the “best” implementation and officially “advertise” it.
Follow up thread: Multiple implementations, one specification.