What are you using for UI, any framework (Polymer, D3) or just plain WebComponent?
Perspective: Streaming pivot visualization via WebAssembly
61–70 of 141 posts
Re: Perspective: Streaming pivot visualization via WebAssembly
#62I wrote the C++ part of this codebase, would be happy to answer any questions about it here.
Is Emscripten the only game in town for WebAssembly C/C++ toolchains, or are there other contenders?
There is Cheerp.
https://www.leaningtech.com/cheerp/
Re: Perspective: Streaming pivot visualization via WebAssembly
#63Earlier quoted context omitted.
Thanks for taking questions. For a back end developer that's watching the front end landscape change from afar.. Do you feel like web assembly could potentially replace JS in the future with, say, my favorite back end language of choice?
Not the op, but there's more to frontend development than JS. You need to account for the API of browsers, the DOM, CSS and the myraid of frameworks and libraries built for the specific UI requirements of frontend development (e.g. React). So even if your favorite language of choice becomes compilable to WebAssembly, you'll still be learning an entirely different way of development that will be completely unfamiliar…
A paradigm shift could happen and what's cool is that it could be entirely something new. This reminds me of the early days of the WWW when the first programming paradigm was Perl/CGI, then Cold Fusion, then Legacy ASP, and then ActiveX, and so on.
The possibility of some company creating, from scratch, a new web development paradigm, given everything we know today, is exciting.
Re: Perspective: Streaming pivot visualization via WebAssembly
#64So, what there is about visualisation?
I read your docs, and found nothing about how to actually render stuff to the page.
Re: Perspective: Streaming pivot visualization via WebAssembly
#65Amazing, despite the fact that some heavy-lifting is done by highcharts and hypergriid.
What's missing for this to effectively kill all typical BI tools like PowerBI, Tableau?
Re: Perspective: Streaming pivot visualization via WebAssembly
#66First, let me say this looks awesome! I’m curious if your considered React.js for the presentation layer (i.e. the js/html5 parts) - on the surface it seems like it would be a good fit - and if so, what you saw as the benefits or drawbacks of it vs the approach you went with.
Will defer to texodus on that - he is the front end expert here.
Re: Perspective: Streaming pivot visualization via WebAssembly
#67Really cool to see non-software companies putting cool projects like this out as open source
the stock market is digital, they are a software company.
J.P.Morgan is not "the stock market" and financial companies are not software companies. They are not selling software. They are selling financial services.
Re: Perspective: Streaming pivot visualization via WebAssembly
#68This is great. Finance people especially love this sort of thing - they do want to browse through entire datasets vs seeing higher level metrics in a lot of cases.
> Finance people especially love this sort of thing - they do want to browse through entire datasets vs seeing higher level metrics in a lot of cases To expand on this, a lot of finance is searching out and understanding, normalizing or exploiting edge cases.
This is why excel is king. just give me a grid with all the data and a pivot table
Re: Perspective: Streaming pivot visualization via WebAssembly
#69For those interested, keep in mind the only way to use WebAssembly with CSP in Chrome is by turning on 'unsafe-eval'. FF/Edge/Safari all at least support compilation from URLs with more locked down policies
True - worth pointing out that this library gracefully falls back to ASM.js if your browser does not support WebAssembly, though.
Does it fallback if Window.WebAssembly doesn't exist, or does it fallback if WebAssembly.instantiateStreaming fails?
Re: Perspective: Streaming pivot visualization via WebAssembly
#70Presumably, the point of using WASM and service workers is for performance, but I see no benchmarks. I also have trouble imagining that this actually improves performance, unless you’re doing all of your compute in the browser and it’s CPU bound (this seems like bad design).
What is the performance of doing it this way vs. without WASM and workers?
Until we see numbers, this smells like a recruiting play.