Not sure what you mean, but I have a feeling.
Normally you wouldn't see the "navigated to" message, because quickly after it, devtools are restarted for the new page. Console and network logs are emptied and started again.
However, there is an option and a checkbox for "preserve log". If that is enabled, you should be able to see these messages because the old logs will not be removed when a new url is loaded.
Good stuff, interesting. However, I really had to laugh at "in a faster, better compiled, and optimized language like Python or Rust"
Still have to chuckle ðŸ¤
Very interesting topic in my opinion, but the article is really hard to read (possibly a machine-based translation). Also, while it indicates the problematic areas, it doesn't go into possible solutions, but I guess that's fine - the title says it's about the struggle :)
I think that compiles-to-js doesn't count in this context, because that can be said about a great many languages. And I think what makes typescript different here is that it's a superset of Javascript. Coffeescript, well. Haven't seen it much lately :)
Also, personally I am not interested in webassembly articles on echojs although I am interested in the technology - I think it's simply a differently world, and probably deserves and has it's own community. I have a similar opinion about flutter and dart.
If I were interested in let's say HTML and had an aggregator for that, I wouldn't want react or JS there, even if we use it to produce HTML.
Since you don't support objects as in e.g `classnames({ isActive })`, I guess you might improve performance a little by using `typeof arg === 'string'` instead of the more expensive `Array.isArray(arg)` call.
Since you don't support objects as in e.g `classnames({ isActive })`, I guess you might improve performance a little by using `typeof arg === 'string'` instead of the more expensive `Array.isArray(arg)` call.