wellsjohnston

Wonderful product :)

no Roblox Studio, no nothin.

I tried "hacking" on Atom recently for a side project and found it was full of bugs and not performant at all. Next.

I started a project called Go++ which was exactly this lol

They are incentivized to give new phones better battery life, while being disincentivized to optimize battery life for previous generation iPhones.

Metroid Prime was so good.

No.

Oh snap.

And my pet snake is one of them, so I'm not sure what that really means.

How is this different from Upwork?

Is setting unknown ages to the median really the right way to go about this? Feels strange to me.

I stopped reading when I saw they were quoting Ellen Pao.

I'm not aware of S3's consistency constraints. What are those?

Good point...I will make it so that destructive is opt-in

I've had the same frustration with S3, and the reasons you went over are what drove me to create this. It seems like they made S3 (10 years ago now?) and just forgot about it. There is no way to sort/filter or even list all the objects in a bucket without writing a recursive algorithm using one of their SDKs.

This does not have to do with AWS Lambda, I'm thinking about renaming it to "functional-s3", or something similar.

To answer your question, there isn't really a workaround for this yet, although indexing should be much quicker than "days". All the keys are listed recursively before running the lambda expression locally. If you have a huge number of files, this can take several minutes, maybe hours depending on the scope.

A workaround I've been considering is using a generator function to list the keys; that way, the lambda expression can start immediately, generating keys as it needs them.

Okay this seems like a good alternative. I just renamed the repo. Renaming it on npm...is a bit cumbersome :|

I did not know about this...looks like Amazon's version of BigQuery. Fantastic!

Sure. We have application logs that come in to s3 and are stored by date prefix. I have CRON jobs that run node scripts that do various counts/statistics.

Ah yeah, just realizing this...what would you recommend?

First, a list of keys is generated based on the set context (and modifier functions). "context" returns a Request object, allowing you to call a lambda function (each, forEach, map, reduce, filter). Each lambda function returns a Promise, allowing you to chain them together. They will operate over the same context, in sequence.

Edit: This is not related to aws lambda...sorry for the confusion

Thank you :)

Writing this was a necessity for me, being a 1-person data team coming from a Node.js background.

This is just wrong. For example, the "best" recording microphone (to many artists), the U67, can no longer be made because the parts aren't available anymore. Yet it is the most popular mic, and 100% not obsolete.

Similarly, Python 2 might not be made anymore, but it is used everywhere, and people are making new things with it. So...it's also not obsolete.

I made a gui for this https://github.com/wellsjo/JSON-Splora

Thanks :) https://github.com/wellsjo/JSON-Splora/issues/38

I made a gui for it, if you're interested https://github.com/wellsjo/JSON-Splora

Thank you for this! Accepted & merged!

Yes, in addition to JavaScript. The filter is first run through a JavaScript VM, then jq, allowing you to manipulate the object with either.