"lightweight charts"

dude what the fuck am i look at

https://tradingview.github.io/light...

tell me about react headache

THIS is why people hate react! because your garbage library doesn't export simple APIs that are easy to use!!!!

to be clear: this isn't a react problem. this is a modern library LIKE react having to screw around with boomer global exporting libraries

grug hate complexity

complexity is spirit demon that enter codebase through well-meaning but ultimately very clubbable non grug-brain developers and project managers who not fear complexity spirit demon or even know about sometime

https://themer.dev/blog/...

Read that article some time ago.

(I think the author should be shot for the font choices....)

Curious as I am... Is your main problem with the boilerplate code regarding the event / state handling or the general design of the API?

I haven't even heard or read anything about that library so can't say anything about it. But you do know you linked to the advanced usage page?

@IntrusionCM font isn't that bad. Article is interesting though. Thanks for the share.

also this is their 'documentation'

https://tradingview.github.io/light...

I don't even know what object this belongs to!!! i mean wtf

yeah, when your GitHub has hundreds of open and closed issues, its gonna mean your documentation is garbage

also love the guy in here who works for tradingview downvoting me, maybe stop downvoting and go work on your documentation!!!

I went through the React, Vue & webcomponent integration guides and tbh the React one was wtf, but the other 2 were easy to follow so not sure about "this isn't a React problem". Had a look at the source code, it was heavily class-based (so not sure about "lightweight charts") but clean.

There could be some more API examples but it looks straight-forward (except in React) if you have TS intellisense

React is disguisting compared to vue. Total carbage. Fun for the 'creative' programmer maybe

imagine writing code like this in javascript only!!!! i'm refactoring it to typescript and the slightest change is breaking everything

i should have known... whenever i see useImperativeHandle it's time to run

amazing how people can absolutely overcomplicate everything and fuck it all up

parent.api() is not a function

shared context

p

asdhkljasfdjghklsdfahjklasdfhjil;jadfsfsa'od

AAAAAA YOU STUPID CLOWNS WHAT DID YOU DO TO THIS LIBRARY

Haloperidol for room 5. The clown acts clowny!

"The Series will be created first whilst requiring a parent Chart..."

The Series requires WHAT?

What does this guy think a component represents in React???

React Router also makes this mistake, in fact it makes another mistake as well by mutatkng the objects defined by the user-provided JSX to attach custom props.

I'm fundamentally happy with React and its ecosystem, but this blatant disregard for established APIs in favour of code aesthetics pisses me off to no end.

Sometimes I think that React would be better off without JSX. If the markup was built with a function call tree, people would be more inclined to use normal fucking functions where they're a better fit instead of trying to squeeze anything into the shiny syntax.