Live data from Hacker News

JavaScript 2017 Rising Stars

slowwaker.work

11–20 of 25 posts

Re: JavaScript 2017 Rising Stars

#11
post #6
post #2

The article only talks about quantity, not quality and that is the main problem with javascript. Not so long ago I had to work with graphs in javascript and none of the graph libraries I found explained the implementation details or the complexities of the algorithms. It turned out that the implementations were ad-hoc and the time complexities were bad so I had to implement my own because they did not work for real l…

Javascript graphing libraries are a pain in the arse, whenever graphing comes up at work we all cringe at the prospect of having yet another go at picking a library out of the millions that is: not painfully slow, not terribly written and not poorly designed even though they are all written on top of D3. I've also submitted PRs so some that I will not name in an attempt to optimise them semi successfully, but you sta…

Would you recommend Plotly for real-time charts that update visually around 60fps? At work we wrote wrote ours in pure D3, but it was as pain in the ass

Re: JavaScript 2017 Rising Stars

#12
post #6

Earlier quoted context omitted.

Javascript graphing libraries are a pain in the arse, whenever graphing comes up at work we all cringe at the prospect of having yet another go at picking a library out of the millions that is: not painfully slow, not terribly written and not poorly designed even though they are all written on top of D3. I've also submitted PRs so some that I will not name in an attempt to optimise them semi successfully, but you sta…

Would you recommend Plotly for real-time charts that update visually around 60fps? At work we wrote wrote ours in pure D3, but it was as pain in the ass

Plotly and Victory Charts by Formidable?

Re: JavaScript 2017 Rising Stars

#13
post #3

> With big project like Vue.js and React, it’s almost becoming a pleasure to design your interface using Javascript. (...) > DisplayJS (...) is lightweight (100kb for the entire library) React + React DOM is around 100kB, Vue is 86kB.

100kb is light weight? That’s a typo, the website says 12kb min/gzipped which is still kind of large uncompressed.

Re: JavaScript 2017 Rising Stars

#14
post #8

fuzzy sorting with no mention of fuzzball?! surely an error /shameless self* promo :P *as much as porting something from another language can be self promo edit: ok technically launched dec '16 so not meet criteria, omission acceptable

not that fuzzysort not great or anything, i like the scoreFn and prepare api's ;)

diff algs for diff things

Re: JavaScript 2017 Rising Stars

#15
post #7
post #3

> With big project like Vue.js and React, it’s almost becoming a pleasure to design your interface using Javascript. (...) > DisplayJS (...) is lightweight (100kb for the entire library) React + React DOM is around 100kB, Vue is 86kB.

Coming from an angular world I went full spartan and just used jQuery (I tried to go native but the DOM interface is rather long winded) - it felt so good, suddenly you realise that for most things model view control is pretty simple to do with a few lines of code and you have the advantage of being able to see exactly what is happening.

jQuery's bread and butter is DOM manipulation. However, for even moderately small use cases (even an interactive form) it is useful to use React, Angular, or some data binding framework, as state changes in jQuery quickly become unmaintainable.

Re: JavaScript 2017 Rising Stars

#16
post #5
post #2

The article only talks about quantity, not quality and that is the main problem with javascript. Not so long ago I had to work with graphs in javascript and none of the graph libraries I found explained the implementation details or the complexities of the algorithms. It turned out that the implementations were ad-hoc and the time complexities were bad so I had to implement my own because they did not work for real l…

It appears to me that due the Github-CV-driven startups, everyone is publishing stuff just to show to such companies. The end result are piles of unmaintained libraries, with dubious quality, making quite hard to find battle tested useful libraries.

[deleted]

Re: JavaScript 2017 Rising Stars

#17
post #7

Earlier quoted context omitted.

Coming from an angular world I went full spartan and just used jQuery (I tried to go native but the DOM interface is rather long winded) - it felt so good, suddenly you realise that for most things model view control is pretty simple to do with a few lines of code and you have the advantage of being able to see exactly what is happening.

jQuery's bread and butter is DOM manipulation. However, for even moderately small use cases (even an interactive form) it is useful to use React, Angular, or some data binding framework, as state changes in jQuery quickly become unmaintainable.

It _can_ become unmaintainable but it entirely depends on how you define your view state, you can still create large applications with jquery if you refrain from creating overly complex state UI (speaking from experience). One thing I find overly shunned in favour of heavy MVC is CSS, CSS is a bloody state machine, it's perfect to manage your UI, you need one DOM call to update one piece of state... define the reset in CSS and your MVC UI component suddenly seem over engineered.

Re: JavaScript 2017 Rising Stars

#18
post #9
post #6

Earlier quoted context omitted.

Javascript graphing libraries are a pain in the arse, whenever graphing comes up at work we all cringe at the prospect of having yet another go at picking a library out of the millions that is: not painfully slow, not terribly written and not poorly designed even though they are all written on top of D3. I've also submitted PRs so some that I will not name in an attempt to optimise them semi successfully, but you sta…

I think GP was referring more to graphs as the abstract mathematical concept, rather than graphical plots. https://en.wikipedia.org/wiki/Graph_(discrete_mathematics)

my mistake, he said "graph libraries" and a graphing library is in the article's short list.

Re: JavaScript 2017 Rising Stars

#19
post #6

Earlier quoted context omitted.

Javascript graphing libraries are a pain in the arse, whenever graphing comes up at work we all cringe at the prospect of having yet another go at picking a library out of the millions that is: not painfully slow, not terribly written and not poorly designed even though they are all written on top of D3. I've also submitted PRs so some that I will not name in an attempt to optimise them semi successfully, but you sta…

Would you recommend Plotly for real-time charts that update visually around 60fps? At work we wrote wrote ours in pure D3, but it was as pain in the ass

It's hard to do anything DOM based at 60FPS and a moderate number of points, if that is the main crux of your problem then I think you picked the correct route (custom D3). Still I find it's hard not to rinse peoples CPU in the browser when doing this.

Alternatively if you have nore than 10K points it's probably time to abandon DOM based methods and just redraw everything every frame directly (canvas / webgl).

Re: JavaScript 2017 Rising Stars

#20
post #3

> With big project like Vue.js and React, it’s almost becoming a pleasure to design your interface using Javascript. (...) > DisplayJS (...) is lightweight (100kb for the entire library) React + React DOM is around 100kB, Vue is 86kB.

"If you were disappointed with Vue.js, React, etc... If you want something super simple to build UI, just try DisplayJS! We hope you'll choose DisplayJS next time you do something great!"

I think it's really hard to be disappointed with Vue.js. Or will hardly find anyone that is.

(That's from DisplayJS' homepage at https://display.js.org/)

Post reply on HN