You can now build native add-ons for Gmail that work on desktop/mobile gmail, with native UI and hooks without needing to write hacky chrome extnesions.
There's still a shit ton of companies whose products live extensively (or exclusively) in Gmail - not to mention the examples they give are use cases that you would not use in slack. Slack is certainly winning as an external communication tool, but email/gmail dominates external (and customer) communication for gSuite-using companies.
Looks like it will from the screenshots (https://4.bp.blogspot.com/-HeFnmVgMiJ8/WMDL3f4TQgI/AAAAAAAAB...) - each app will have it's own icon and hooks into emails/threads. I too have built a few gmail integrated apps and this will be super nice and convenient.
from the article:
Although xHamster is a free porn site, users can sign up to create personal favorite collections, post comments, or upload their own videos. According to the xHamster site, over 12 million people have signed up for an account.
What exactly is "dangerous" about this? The functionality is pretty straightforward - it just creates a parent element of the correct width/height around an element that dictates the original elements height, and then resizes the inside one proportionately as needed for responsiveness (using CSS only).
"Dangerous" was the wrong word, and I should have expanded further. Also, it appears as though my use case isn't specifically for what this is designed, so I take that back. I'm thinking of the case in which this may be useful to modify older complex sites where chosen selectors might cause unexpected results. Apologies.
Reframe.js is written the way that it is (to do 1 thing simply) to put the power back in the hands of the asset owner. This approach was chosen over trying to solve all ~all of the things~.
Very cool idea, and something that would have been useful on many projects in the past. A little light on # of listed sights, but certainly something I could see myself using for future projects.
I purchased Paw about 6 months ago and used it heavily, until recently I have ran into multiple situations where it didn't properly include custom headers I specified into the request, and was causing odd errors that I assumed were the fault of the code I was testing (happened in multiple different languages/projects). I have since started using Postman, but would love to go back to Paw since I appreciated some if it's features (such as being able to save an API definition into the github repo for sharing with other devs)
EDIT - didn't realize this post was for Paw 3, which just became available. Installing now and excited to try it!
