Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

unovis.dev

Post reply on HN
Print view View original

21–30 of 55 posts

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#21

Post by taeric »

e1g wrote: post #20
taeric wrote: post #18

Earlier quoted context omitted.

I'm curious what is bad about it? Not in an "I don't believe you" way, but in a "I would love to know what would improve it." Starting to push to clean up some web pages I've been close to at work, finally.

Not OP, but some patterns instantly stood out - * The use of `useCallback` is confusing in the demo code and is entirely unnecessary. * Inconsistent use of single/double quotes and {}'s for literal values. * Non-idiomatic combination of JSX elements + raw HTML in strings [1] [1] e.g. https://unovis.dev/gallery/view?collection=Lines%20and%20Are...

I assumed the was just directionally wise? That is, it is clearly useless here, as there are no "dependencies" passed; but in a real app you almost certainly have something there.

Still digesting the rest. I'm curious why the mix of raw HTML. (Not in why it is a bad idea, but why it was felt necessary.)

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#23

Post by e1g »

taeric wrote: post #21
e1g wrote: post #20

Earlier quoted context omitted.

Not OP, but some patterns instantly stood out - * The use of `useCallback` is confusing in the demo code and is entirely unnecessary. * Inconsistent use of single/double quotes and {}'s for literal values. * Non-idiomatic combination of JSX elements + raw HTML in strings [1] [1] e.g. https://unovis.dev/gallery/view?collection=Lines%20and%20Are...

I assumed the was just directionally wise? That is, it is clearly useless here, as there are no "dependencies" passed; but in a real app you almost certainly have something there. Still digesting the rest. I'm curious why the mix of raw HTML. (Not in why it is a bad idea, but why it was felt necessary.)

In this specific case, having useCallback makes the demo code more complex and is unrelated to the actual concept being demo'ed to the reader. It's unwise to add unnecessary complexity if it doesn't add clarity.

More generally, adding useCallback is even directionally wrong unless you know _exactly_ why you need it ("for identity" is OK, "for performance" is almost always misguided because the cost of creating a closure is negligible).

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#24

Post by go_prodev »

eatonphil wrote: post #7

The thing I've wanted is a visualization library that also comes with the UI controls for configuring graphs: picking the graph type, picking the fields, picking the labels, picking the aggregation, axis settings, etc. Almost no one is implementing libraries that do this. Everyone just keeps building "low-level" graph libraries that leave application developers to build up (in my case) crappy and inflexible configura…

Yes, same here. I'd love an open source Power BI alternative.

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#25

Post by texodus »

eatonphil wrote: post #7

The thing I've wanted is a visualization library that also comes with the UI controls for configuring graphs: picking the graph type, picking the fields, picking the labels, picking the aggregation, axis settings, etc. Almost no one is implementing libraries that do this. Everyone just keeps building "low-level" graph libraries that leave application developers to build up (in my case) crappy and inflexible configura…

Ever try Perspective? https://github.com/finos/perspective

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#26

Post by no_wizard »

timetraveller26 wrote: post #12

As a Vue developer I take the lack of support personal.

At least you can just encapsulate it in a custom element. Vue has good support there and allows you to "componetize" it with little overhead or development time.

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#27

Post by eyelidlessness »

e1g wrote: post #20
taeric wrote: post #18

Earlier quoted context omitted.

I'm curious what is bad about it? Not in an "I don't believe you" way, but in a "I would love to know what would improve it." Starting to push to clean up some web pages I've been close to at work, finally.

Not OP, but some patterns instantly stood out - * The use of `useCallback` is confusing in the demo code and is entirely unnecessary. * Inconsistent use of single/double quotes and {}'s for literal values. * Non-idiomatic combination of JSX elements + raw HTML in strings [1] [1] e.g. https://unovis.dev/gallery/view?collection=Lines%20and%20Are...

All valid, but the thing that stood out to me most besides useCallback being weirdly inlined—and this is more important IMO—is how awkward everything around labels is. Surely there could be a base labels component that just takes `data`, or at least doesn’t require so much ceremony around the vanilla interface.

The Svelte and vanilla examples are almost identical, but the Angular example looks much more like I’d expect, which strongly suggests (to me) that this is an Angular library with support for other uses bolted on as an afterthought.

That’s all fine, but it probably won’t get much non-Angular adoption if there’s no further effort to make it feel somewhat more idiomatic in other environments. Even if it looks quite nice otherwise (which at a glance it does!).

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#28

Post by eyelidlessness »

arooaroo wrote: post #13

I immediately like this project for being “framework independent” rather than agnostic. It’s odd how computing has fashioned a completely different sense for “agnostic” despite perfectly adequate and well understood words already existing.

Is your objection to “agnostic” its religious implications in other contexts? It’s a perfectly cromulent synonym for independent in this context otherwise.

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#29

Post by taeric »

e1g wrote: post #23
taeric wrote: post #21

Earlier quoted context omitted.

I assumed the was just directionally wise? That is, it is clearly useless here, as there are no "dependencies" passed; but in a real app you almost certainly have something there. Still digesting the rest. I'm curious why the mix of raw HTML. (Not in why it is a bad idea, but why it was felt necessary.)

In this specific case, having useCallback makes the demo code more complex and is unrelated to the actual concept being demo'ed to the reader. It's unwise to add unnecessary complexity if it doesn't add clarity. More generally, adding useCallback is even directionally wrong unless you know _exactly_ why you need it ("for identity" is OK, "for performance" is almost always misguided because the cost of creating a clos…

Wouldn't you want it to be "dependent" on whatever the source of the data is?

Re: Unovis: Data visualization for React, Angular, Svelte, TypeScript, JavaScript

#30

Post by jd3 »

Traubenfuchs wrote: post #8

Example links are all broken... https://unovis.dev/gallery/

looks like a path issue

https://unovis.dev/gallery works, while

https://unovis.dev/gallery/ does not

you need to navigate to https://unovis.dev/ and then click "Gallery" for it to segue you to the former

Post reply on HN