Tip (please for the love): If you have a UI element on page that can be clicked for one action and dragged for a different action, make sure dragging it only one or two pixels fires the click action
After 6000 years of written language, we’ve honed the craft so most languages can communicate effectively with only a few dozen characters.
After 60 years of digitally recorded language, we’ve thrown all discipline to the wind and added hundreds of thousands of unnecessary characters, including poop, dolphin, and an eggplant that means phallus.
It is okay to nest #html <article /> elements so long as they contain a unit of self-contained content that could stand on its own and make sense, but also related to its parent article.
@chriscoyier After being told for a decade that the performance is too terrible to be possible, I feel a bit gun shy about them. I use them when it’s truly necessary, but still default to media queries when those are sufficient
jQuery plugins depended on jQuery, and when jQuery went out of favor, they ended up in the junkyard.
There is all sorts of componentry built exclusively on React, limiting it to React-based sites. As React goes out of favor, they will end up in the junkyard. (Same with any framework-specific extension.)
But with Web Components... it seems like the story will end differently. If they are built without dependencies, they might just live as long as the web does.
@davatron5000@chriscoyier@nicolaschevobbe yeah that’s key I think. I have some old school js on my blog for comments. I looked into converting to wc and the code was worse that way; longer and more obtuse. I need the same benefits I get from JSX to make wc palatable
Andy and I have been hand washing dishes for weeks because we don’t want to call someone to get the dishwasher fixed. Couldn’t be more millenial if we tried.
@zachleat I've noticed an additional trend that involves step by step, deep dive into the instructions BEFORE the ingredients list and final recipe (and after the life story)