Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
In my current implementation there are things that result in the absolute worst case performance. Unfortunately those are also things that will occur quite frequently in regular apps. Take the benchmak I made which lists items in a table and you can click to select a row. The engine will recognize that the attribute accessed the ident of the item and the ::selected key. So whenever this changes the query recomputes. With 1000 mounted rows that does a lot of work. No rendering occurs in 999 (or 998) cases but running the query alone takes too much time.
u/thheller how does the << macro compare to https://github.com/lynaghk/hicada ?
The source of the events is however dynamic. They either come from the DOM or any other hook. This design works well. Local state is just as straightforward as more complex things like the EQL.