4 ms·
Seems like exactly the tool we needed just two days ago for pruning down a 49mb json file. We ended up parsing it in nodejs as it could simply spit out the outp
by 97-109-107 13y ago
Seems like exactly the tool we needed just two days ago for pruning down a 49mb json file. We ended up parsing it in nodejs as it could simply spit out the output to a file. I didn't want to risk crashing my browser again - is there any chance that a client-side web-app parser (like yours) would be able to handle files that big?
- spolu 13y agoYep. We are trying to push our bizdev to use it as well. It's still slightly complicated... but they're starting to get it! :)
- 97-109-107 13y agoAm I missing something, but wouldn't that require pasting the 49mb file into your app through my clipboard? Just getting a file like that into the clipboard, let alone pasting into the browser, seems like a task in itself.
- spolu 13y agoYes you're right. 49mb is slightly large for REPL. but I've been working successfully with 200k lines CSV of over 15mb without issue
- maninalift 13y agoYour bandwidth has nothing to do with it, it runs in the browser. All it does is JSON.parse, execute your series of functions then JSON.stringify. Unless I'm missing something there is no advantage over ad-hoc javascript. If you want to load a file from disk, deserialize and do some processing in javascript then node is absolutely the right tool (and this isn't).
- Cthulhu_ 13y agoMaybe if you could install it locally / if it supports the file API without having to upload it to the server. I would like to see a 'pure' client-side implementation, though.