anonfunction

The gif is lower quality than the mp4 or webm formats which we serve on our website and the embeddable GIFS player[1] if your browser supports it.

We've chosen to prioritize speed over quality for the initial launch so at this time but are working on transcoding to various sizes and qualities to return based on the client's device size and internet speed in the player or when someone wants to share a super high quality (and file size) GIF.

1. https://gifs.com/docs/player

Hey HN, I'm one of the back-end engineers at Gifs.com and we just launched a brand new editor that anyone can use to create and augment videos online.

We started with the premise of democratizing video editing by making an iMovie-lite in the cloud. Our goal is to empower people around the world to express themselves. We still have a lot of ideas in the works to make finding, creating and augmenting short-form media frictionless but launching our new editor is the back-bone of that dream.

You may remember us from gifyoutube.com where anyone could add gif in front of youtube and we would let you trim the video and add captions. Now you can simply replace youtube.com with gifs.com or put gifs.com/edit/ in front of any video or GIF to open it up in the new editor with even more editing capabilities.

Everyone knows a picture is worth a thousand words, so does that mean a GIF must be worth n pictures where n is frames in the GIF? After checking out /r/reactiongifs/ and /r/wastedgifs I now believe so.

This is a nice query[1] to view all open issues for your org's private repos:

https://github.com/issues?q=is%3Aopen+is%3Aissue+is%3Aprivat...

If you like this you'll love gifi[1] which plays a gif instead of npm's loading bar.

1. https://github.com/vdemedes/gifi

https://gifs.com introduces the .potato file format https://medium.com/@gifs/gifs-com-has-created-a-budding-new-...

.potato file format: https://medium.com/@gifs/gifs-com-has-created-a-budding-new-...

https://gifs.com

An easy way I've used to explain the difference between junior and senior is this:

> Junior devs use libraries, senior devs write the libraries

For anyone wanting to download it, which I don't believe it is set to allow since there was no such UI present to allow it I found that this link[1] downloads the spreadsheet in CSV format:

1. https://spreadsheets.google.com/feeds/download/spreadsheets/...

One of the only books I've consistently recommended is High Output Management[1] by Andy Grove. His methods for dealing with complex interconnected problems was as brilliant as it was when he wrote it 30+ years ago.

1. http://www.amazon.com/High-Output-Management-Andrew-Grove/dp...

Since most of the lines have references to footnotes it would be cool to supply those as well. Or remove them.

Link to github repo: https://github.com/bovard/raid

Demo of the gif player using vine videos: http://montanaflynn.github.io/basketball-style/

Example of importing an instagram video: http://api.gifs.com/media/import?source=https://www.instagra...

Thanks! It's just the beginning of some very cool things we have planned like captions and effects. It also opens the door for integrations with CMS's and publishers to start using our gif player[1] and driving traffic back to their sites.

1. https://gifs.com/docs/player

Not to mention when you fill it out it says:

> Success! We've got your information and will send you a note when 5.0 Alpha is available.

With no links to documentation or github or anything. Having me sign up and get told I'll be emailed at some unspecified time when it's available was very disappointing.

So it's android only?

Having used both this and gifs.com (formally gifyoutube.com) I can say that I prefer the latter. It's as simple as replacing youtube.com with gifs.com in the URL[1].

Disclaimer: I work at gifs.com

1. https://www.gifs.com/watch?v=jhyANGHDDH8

Where's the code? I just see docs and images in the repo.

Does anyone know what the temperature was like when and where this was taken? It actually looks like it would be a fun hike.

I also have a micro-library[1] that deals with dates, and it's also much faster than momentjs[2].

1. https://github.com/montanaflynn/human-date

2. http://jsperf.com/human-date-vs-momentjs

Also one of my favorites, and also like another reply to this comment I ported it[1] to a language I was learning, Golang.

1. https://github.com/montanaflynn/toy-spelling-corrector

They launched a new comment feature yesterday: https://github.com/blog/2097-improved-commenting-with-markdo...

Obviously just adding more moving pieces for no benefit is a waste of time. However there are many areas that can be improved or even entirely automated with software.

My bigger point was that writing code is not "a bad thing that should be avoided" because I think it helps programmers understand the problem and can add more value than debt. Even if it may change at some unknown point in the future.

I've often joked that 10x programmers were the ones who used multiple cursors. Seriously though, I would argue that writing a lot of code, even if it's not all going to be the next cash-cow for your company, is good for the hackers soul. It also adds intellectual property and infrastructure to your company.

It's a bit different, I added that I had never heard of the phrase and that I would be using it.

Thanks for clarifying, I guess I missed that part.

Thanks, I guess I glossed over that part of the article but when I got to the end and saw the original quote I assumed the worst. The title alone is pretty inflammatory in my opinion.

I've never heard that and I'm stealing it.

I don't like how the title and article reads like a hit piece on Amazon Glacier. It's great at what it is intended for. In addition it seems he still saved money because over 3 years because the $9 a month savings added up to more than the $150 bill for retrieval.

I'm surprised that this aspect has not been mentioned here in the comments yet:

> I was initiating the same 150 retrievals, over and over again, in the same order.

This was the actual problem that resulted in the large cost.

At my old job we would get a lot of complaints about overage charges based on usage to our paid API. It wasn't as complicated of pricing as a lot of AWS services, just x req / month and $0.0x per req after that, but every billing cycle someone would complain that we overcharged them. We would then look through our logs to confirm they had indeed made the requests and provide the client with these logs.