JoeBot3000

5 ms·

1.
Building S4 – our own high-performance time-series data store(medium.com)
2 points by JoeBot3000 19d ago|0 comments
2.
by JoeBot3000 5y ago
The majority of packages in JS land change quickly and are poorly documented, unfortunately :( There certainly are stable packages, but sometimes to do what you need to do there is no other option.
3.
by JoeBot3000 5y ago
> I regularly see websites that have noticeably slow javascript "startup" times. True, same as any language or applications fast CPUs shouldn't be a free chance to completely ignore writing efficient code. Although I bet t
4.
by JoeBot3000 5y ago
> You can make either function take arbitrarily long by increasing the size of the input. The second one scales worse. I think this is the point, the second one scales worse - absolutely (ignoring the bug you mentioned) however it really
5.
by JoeBot3000 5y ago
For lower numbers this completely optimizes away for me too, but after a certain point the loops stays in place (with no flags)
6.
by JoeBot3000 5y ago
I don't know that I agree with this article, while there is absolutely a problem with package/framework/build tools churn that makes development super painful, I don't feel that developing with JavaScript has been any mo
7.
by JoeBot3000 5y ago
Super true, and JS frameworks haven't always been kind on their CPU usage ( cough AngularJS). I think desktop GUI apps also have browser rendering engines chewing resources.
8.
We've been lied to: JavaScript is fast(jyelewis.com)
56 points by JoeBot3000 5y ago|83 comments