So you want to do complete round trips to the server every time the page needs to update something on it without using JS? We already had that in the early days of the web and it sucked. Though I absolutely hate the use of bloated and mostly unnecessary JS frameworks, we can't just cut off all use of client-side scripting. Without client-side JS, most of the stuff out on the web today would not be possible, including Poal.
Imagine having to make a complete round trip to the server and have the page reload every time you upvote/downvote or post a comment. Without using the incredibly hokey techniques of named anchors to jump to a specific spot on the page where you were last at, each round trip would put you back at the top of the page. That would suck for reading comments.
Yeah, I hear what you're saying, but JS has its place on the web. Until we develop a brand new content and application delivery system, as in completely reimagining what a browser is and does, we will have to deal with the piecemealed technologies that it evolved with over 25+ years. Rather than fix the web, why not start a movement for building a new and better technology that doesn't rely on these flawed technologies?
Precisely. Say good bye to Google spreadsheets and all that. Honestly, if implemented properly, users don't even notice it. Google spreadsheets, docs, o365 sheize is quite impressive at a basic utilitarian perspective. In the degrees that they suck isn't because of the js frontend or whatever back end they are using, they suck because of the choices those companies make around the ecosystem they want for their clients.
GWT was and still is here, but, hey, cannot use it since it is not the latest fad language
golang is so stupid it is painful, let's just change the syntax enough to be incompatible with anything else
let's just solve some cases with a solution and declare victory
yes, victory, we GOOGLE managed to cage the idiot developer, YEAH, we ar emaster of the universe
(post is archived)