Echo JS 0.11.0

I can't speak to any specific downvotes... but Top N lists are usually unwelcome as are framework comparisons... especially if there aren't metrics behind the why, what and how it is considered.

What is this list from, and why in this order?  What are the impacts of before/after, do you have test cases?

If you read the Steve Souders books on this, he specifically lists how/why and what tests were done to indicate the advice given.  While the specifics may change, the practice is usually what is expected.

TBH, when I see Top N lists, I usually remove them summarily for the reasons above.  Even if your tips are good advice, there's no why, and there's definitely no reasons behind them being the top... vs. what?  Testing, metrics, performance differences, etc should be included...

If you just went through the performance suggestions that Lighthouse goes through and what difference they make, that would probably be a more substantial article.  Make a completely unoptimized site/app then walk through the suggestions... there may be 25, there may be more, there may be less.

In the end, click bait titles, and comparison articles without metrics, meaning or rationale behind them are generally less well received.

@vfk This is *NOT* a Python site... this is a JavaScript site... while most of the openreplay content that is posted is fine, this is not okay here.

Maybe consider a web-worker that emits the change events, listening to a debounced method combined with requestAnimationFrame for render updates?

This is EchoJS not EchoGolang

I don't get why people aren't using plain fetch for these kinds of things... I know axios has some advantages, but you can shim what you need of it in like 20 lines of code most of the time.

If you could reach out to me... tracker1 at gmail ... would appreciate it.   Thinking it would be cool to get a couple old BBS terminal programs running in your dostbox js setup... RIPTerm 1.54 as an example... but no idea how to get it to connect to a modern telnet bbs.  There are websocket terminals already, but would be cool to get websockets into the jsdos environment.

11 paragraphs, sections, blurbs and bullet points before the ad block, and no content/example or demonstration of why it is a better workflow.

Comparisons to real DOM vs vDOM are somewhat immaterial from the developer experience... and iirc, React are considering removing virtual DOM since the browsers have improved since React first started... it doesn't change the flow.

React's size is an issue... and tbh, not sure why it's still as big as it is.  I get it during dev, they add a lot, and it's possible what's left is mostly cruft for dev experience... unsure.

The comparisons at the bottom are slightly more interesting... I'm frankly surprised that SOLID didn't just follow the React API for a lot of the hooks/naming, it makes it more different, but also makes conversion a hindrance.  The foo-compat libraries (such as preact-compat) are what make them better suited for a quick swap.

The biggest thing for any upstart react-alike or JSX framework or library to overcome is going to be React's entrenchment and ecosystem.  There are a *LOT* of modules, UI, state, and other libraries that work with React... anything that wants to unseat it and be similar, needs to be mostly compatible, that is just my own take on this.

In the end, I generally hate comparison articles, at least this one focuses on only comparing two, and apparently part of a series.

Cool, although I do wish there was some indication of the payload size/overhead for this.

The biggest issue I've had in embedded editors like this, is the payload is often pretty massive... I usually like to defer as much as possible to only screens where needed/used.

Adjacent is the need to sanitize html pasted content (such as from MS Word).  It's the bane of all human existence.

Seems to be a simple abstraction, since D3 is a very flexible API, it can be easier to work with simpler components.  I haven't looked into this, so can't recommend or comment, just replying on why one might want to use this, or something similar.

A lot of charting/graphing components use D3 under the covers.

With the exception of a few server and app module environments (such as adobe extensions), since nearly every browser is auto-updating, I tend not to support anything more than a year old for browsers... Phones are a little niggly, but even Android has separated chrome updates from android.. and Apple does updates for even fairly old devices.

For me, I use ES2020 features without much fear.  Just my own $.02 at this point.  Anyone that would disable updates is a security risk, and I'm fine with them not being able to use the applications I work on at this point.