On the browser side, I do think it has become easier to write something that feels like a real interactive application as opposed to just a form that you can submit like in the early 2000s. The good news is that we really can develop fairly ambitious applications that run in the browser, and there are more frameworks available nowadays to make this doable without re-inventing the wheel.
However, you're right, it still feels clunky. I think part of the problem is that the tools/technologies remain rather immature, but I think a significant part of the problem is also just that the web was designed as a way to share documents. Even today I think that this philosophy remains embedded in the standards, and there is just a significant mismatch between between the models of "sharing documents" and "making interactive applications." In that regard, I don't know if I entirely like it, but I do wonder if the future is something like Blazor.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
On the browser side, I do think it has become easier to write something that feels like a real interactive application as opposed to just a form that you can submit like in the early 2000s. The good news is that we really can develop fairly ambitious applications that run in the browser, and there are more frameworks available nowadays to make this doable without re-inventing the wheel.
However, you're right, it still feels clunky. I think part of the problem is that the tools/technologies remain rather immature, but I think a significant part of the problem is also just that the web was designed as a way to share documents. Even today I think that this philosophy remains embedded in the standards, and there is just a significant mismatch between between the models of "sharing documents" and "making interactive applications." In that regard, I don't know if I entirely like it, but I do wonder if the future is something like Blazor.