Message from JavaScript discussions

February 2018

— I'm planning to open source one of them when it is ready

— 

It's an sql cache thing that also abstracts away the sql language, and let's you query with http+json

— Mainly used because we have a slow-ass legacy MS SQL server at work

— So I have to throttle and cache DB requests

— Arrays have fixed length at the time of creation and cannot grow in length to accommodate new items past its size.. Arraylist can grow dynamically

Message permanent page

— Also deleting an element in the middle of the array means shifting all the other items forward to fill the gap.. Doing many creation and deletions on large data sets can be detrimental to performance.. Linked lists on the other hand don't suffer this problem

Message permanent page

— Before initial release:
1. Use prepared statements everywhere I can, and implement proper escaping where prepared statements are impossible
2. Support multiple DB backends

Message permanent page

— Mh.. Sounds interesting..

— JS Arrays are completely dynamic, they can contain elements of any time, different types at the same time, grow and shrink, etc

Message permanent page

— But yes, they do have this problem in JS. V8 may do some magic to optimize this, but the bigger question is:
Why are you storing huge arrays in JS?

Message permanent page

— JS is not great for CPU-heavy operations

— It's perfect for streaming, data-heavy apps, and I/O