// jQuery
$(document).ready(function() {
// code
})
// 1. Go to https://twitter.com/i/likes | |
// 2. Keep scrolling to the bottom repeatedly until all your favs are loaded. | |
// 3. Run this in your console (open in chrome by View > Developer > JavaScript Console) | |
// Notes: this may take a while if you have a lot of favs/likes | |
// you can only access your most recent ~2000 likes. | |
// inspired by https://gist.github.com/JamieMason/7580315 | |
$('.ProfileTweet-actionButtonUndo').click() |
https://twitter.com/snookca/status/1073299331262889984?s=21
“In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?”
Happy to chat about this. There’s an obvious disclaimer that there’s a cost to css-in-js solutions, but that cost is paid specifically for the benefits it brings; as such it’s useful for some usecases, and not meant as a replacement for all workflows.
(These conversations always get heated on twitter, so please believe that I’m here to converse, not to convince. In return, I promise to listen to you too and change my opinions; I’ve had mad respect for you for years and would consider your feedback a gift. Also, some of the stuff I’m writing might seem obvious to you; I’m not trying to tell you if all people of some of the details, but it might be useful to someone else who bumps into this who doesn’t have context)
So the big deal about css-in-js (cij) is selectors.
// get an array of all the keys on the window | |
const dirty = Object.keys(window); | |
// Then create an iframe set to nothing | |
const iframe = document.createElement('iframe'); | |
iframe.src = ''; | |
// put it into the DOM | |
document.body.append(iframe); |