perspective VS cli

Why do you want to render to canvas?

Perspective seems to be the most performant html table. It is more focused on extremely fast updates than styling, although it looks good.

Glide is a newcomer that also renders to canvas.

https://github.com/finos/perspective

https://github.com/glideapps/glide-data-grid

SQL workbench also uses https://perspective.finos.org/ for tables. It's a WASM table library which pairs nicely with duckdb and works well with large tables.

Yes. We are working on adding support for aggregation and pivoting using https://github.com/finos/perspective

I haven't looked extensively at react-datasheet. It looks like it is trying to build more of a full product than the other data tables.

I have used ag-grid extensively, its an impressive product. Some pieces are a little awkward to use, particularly auto-sizing. But generally ag-grid has thought of most functionality and has a solution. The creator of ag-grid had a great interview on Javascript Jabber [1].

The other serious data table component that I have seen is FinOS Perspective [2]. This is extremely high performance, also more specialized and probably harder to customize. I think Perspective renders to a canvas element from Rust/C++ compiled to WASM (not 100% sure). It is also made for streaming updates.

AG-Grid supports streaming updates... but only in the commercial version.

Eventually the data model for these types of tables becomes tricky. I will be investigating parquet-wasm for my use case. Hit me up if you want to collaborate.

[1] https://blog.ag-grid.com/javascript-jabber-podcast/

[2] https://perspective.finos.org/

Something like https://github.com/finos/perspective ? We use an OLAP(-y) WASM engine to provide query-ability to our data visualization tool, and doing the calculations in the browser is cheaper and simpler than a server-side database for datasets that fit in browser memory.

Note: You can check the quality of SOCKS5 or HTTPS proxy with companies like: https://ipinfo.io or whoer.net

You need an access token from ipinfo to access their API. Go to ipinfo.io and sign up for an account. After signing up, you'll get an access token. Keep it handy as we'll need it in the next step.

stories: - name: get-ip-info steps: - name: get-ip url: https://api.ipify.org/?format=json http_method: GET - name: get-location url: https://ipinfo.io/${{steps.get-ip.response.body.ip}}/geo http_method: GET expectations: - field: Body operation: Contains value: "Australia" schedule: initial_delay: 10 interval: 60 alerts: - url: https://my.site/notify

3- IPinfo

Mullvad VPN location set to Frankfurt germany

Using the us east test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 0/55 - Very likely not a VPN

Using german test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 30/55 - Very likely a VPN

The thing that changed between both tests was the flow latencies vs ping latencies check. Clicking on more info it said: "flow variance too large in relation to avg flow: 0.6937484181219945"

I guess it works kinda, but not very consistent.

But e.g. https://ipinfo.io/ reveals immediately that this IP is a VPN IP address.

If it's a work computer it may be connecting to it's own VPN automatically. If you go to a site like https://ipinfo.io/ do you recognize the external IP address, region, and org?

Then just check IP of the server when ping is high for you, put IP in https://ipinfo.io/, and block range for all other servers in same datacenter.

3. Check the IP address information by ipinfo.io, and confirm the IP location information is right with okeyproxy's we pasted into ProxyHelper.