Does the Canvas api have support for webp?

By quickly looking at MDN[0], at least in Chrome, yes. Honestly, I can't say for other browsers at the moment.

[0]: https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasE...

Fair point, although I like the blur effect. But you can also fill in with a solid color or transparency.

Thanks It was fun to build.

Good idea. I've just changed it so now you can keep pushing the blur button and it will increase the blur by 1px for each push.

The site itself is at https://photo16x9.com

Cool... any chance to see a "photo1x1.com" doing exactly the same for Instagram, maybe? (They favour square format creating a simikar problem for users).

I just skimmed the source code and it looks like you could add support for other aspect ratios really easily. Not sure if OP is accepting pull requests.

EDIT: I went ahead and added quick support for other aspect ratios myself. Feel free to use it.

https://gist.github.com/CivBase/92f1b387c4c98d24481ec28ea2fc...

4x5 is the optimal size on Instagram I believe. Gets you the most screen real estate as someone is scrolling past your photo

The single player mode is just for beginners, but I do think we have a pretty nice multiplayer feature, where you can easily challenge others and start a new game without creating an account (we don't have accounts).

The alternative to serverless isn't "single instance". With Elastic Beanstalk you can have multiple instances, autoscaling etc.

> This feels very "Serverless is cool, everyone is saving money on it, lets do the same

More like "seems like there's an easy way for me to try this new thing out, lets give it a shot". It took a couple of hours to switch over to this, and I learnt something in the process. Also, our API is very simple, pretty much all the actions are a single database call, so I don't think in this case we would have gained anything by splitting things up into more pieces. But I can see how it would make sense for a larger, more complicated app.

Yes, ALB would have been a much better fit for us. We used API Gateway because that's what the serverless framework sets up (at least by default) and I didn't know you could use ALB in front of Lambda.

Yes, it does show there's a gap in the documentation, hopefully someone from AWS will pick this up (and the serverless framework has only just added ALB support a couple of months ago)

> requires a complete re-architect of your stack.

Not necessarily. The reason I decided to try this was exactly because I found a tutorial showing you could easily host a bog-standard ASP.NET web app on Lambda with the serverless framework. I had to add a small startup class, and one config file to our existing app and I was up and running.

Recently we had to test a posibility of our core application being hosted in contenerized environment. It was really hard, because some tweaks we used are not really documented well. Kernel Tweaks had to be tested separately because we were not sure whether they work or not, recource management had to be done from zero level. JVM optimalizarion from zero level. Service Discovery configuration from zero level. --- Sure it works from the go for punny small apps. But when it comes to huge corporations running extrordinary workloads - no its not that easy.