Re:Breaking up with JavaScript front ends
by taeric on Saturday December 10, 2022 @06:11PM
(#33938070)
You didn't even mention GWT. I don't know what is causing it, but yeah, Google has dropped some turds over the years.
Re:Breaking up with JavaScript front ends
by johnthuss on Saturday December 10, 2022 @06:27PM
(#33938167)
The original version of GWT was mainly about solving compatibility issues between browsers (of which there were many). Modern GWT/J2CL is all about leveraging the mature Java development tools, especially code completion. GWT can be used with just the standard DOM APIs very effectively these days via the elemental2 library.
Re:Breaking up with JavaScript front ends
by taeric on Sunday December 11, 2022 @12:21PM
(#33945151)
Apologies on the slow response.
That makes sense, but I also recall it was about trying to use the same language on the server as the client. And it worked as well as the efforts to use JavaScript is the server. Which is not to say it can't work. There are a lot of traps there, though.
Re:Breaking up with JavaScript front ends
by runarberg on Saturday December 10, 2022 @08:44PM
(#33939126)
Material Design is also Google’s fault. Regrettably a pretty sizable chunk of the industry either uses it directly or—worse—incorporates elements of it in their design.
I also have a pet peeve with the Roboto font family developed by Google and used everywhere on the web. But I’ll admit that it is a fine font face for its purpose, just very boring and used way too much.
Re:Breaking up with JavaScript front ends
by thex10 on Saturday December 10, 2022 @09:01PM
(#33939250)
> Talking layer of DOM nodes, I actually did a few samples of this the other day.
Is there a tool for this? I’m kind of wanting to check my site now…
Re:Breaking up with JavaScript front ends
by nicoburns on Monday December 12, 2022 @08:53AM
(#33954602)
You can run the following snippet in the console:
function getMaxNestLevel() {
var i = 1, sel = '* > *'; /* html > body is always present */
while(document.querySelector(sel)) {
sel += ' > *';
i++;
}
return i;
}
console.log('total nodes', document.getElementsByTagName('*').length);
console.log('max nest level', getMaxNestLevel());
Meanwhile most of the industry is using React, which is actually pretty well engineered and perfectly fast (you may well find yourself using a slow React app, but that's not React's fault).
P.S. Talking layer of DOM nodes, I actually did a few samples of this the other day. Gmail has 34, which was by far the deepest of any website I checked and probably isn't helping it's performance.