News for hackers. Stuff that matters.

mesquka

Node.js read 3.7GB JSON file

I'm currently reading/writing a 3.7GB-ish JSON file from disk into NodeJS, I'm using --max-old-space-size to accomodate the larger file and JSONStream and FS streaming to get around Node's Buffer size limit/string size limit. Is there a faster/more efficient way of reading large JSON files? I'm thinking I can optimise the write out by just using a traditional DB for that, but...

( Read More... | no comments | on HN )
Re:Ask HN: Flutter VS React Native on Sunday December 03, 2017 @12:52PM (#15838585)
Flutter is in alpha, and has a very small ecosystem. Flutter does perform much better in 'tough use case' scenarios though.
Re:Impossible to type 's' or 'p' in GitHub text zones on Monday September 18, 2017 @10:24AM (#15276197)
Copy/Paste s's and p's from an existing piece of text works just as well
So to answer your question, the problem is a usability one.
The main issue with WhatsApp is the lack of warning when someone's keys change and the fact that you have no guarantee that the noise protocol is implemented end to end as it's impossible to check the source (decompiling/reverse engineering aside)
WhatsApp has implemented the same encryption scheme, but it's not as trustworthy as Signal on account of it being closed source. Assuming the code were trustworthy, proper verification of keys requires a physical meeting.
Take a look at Signal be Open Whisper Systems - biggest problem with signal is that in order for you to verify the other parties identity in a fully trustworthy manner, you'd need to verify your keys in person.
I'd be interested if it did consolidation of contact info from multiple sources as well.