New Features Don’t Mean Stop Using Old Ones Completely!
I’ve been hearing a lot of softheaded nonsense lately about how you “Shouldn’t ever use floats now that we have flex and grid!” and “You’re stuck in the past for still using them!” Well… to be brutally frank:
Warning: Practically perfect people prefer to be polite, but sometimes you’ve just got to say screw it! Once again I’m not “toning down” my disgust with the schmucks and putz claiming their brain-farts smell like roses. You have a problem with a little “harsh language” go back to your tea party grandma!
All the “This is 2022 stop using floats” tommyrot seems to once again be the result of those devoid of critical thinking or any real understanding using a paint roller on concepts that should be applied with an eye-dropper. Magically turning “when appropriate” into “always” as I wrote about in one of my first articles here on Medium years past.
These claims when contested seem to elicit the same gormless responses as well. It’s not “stuck in the past” when combined with properties like shape-outside that are as new if not newer than flex and grid! Same asinine bird-brained drek as the guy who said I was “stuck in the past” for favoring for..of over Array.forEach. News flash dipstick, for..of is the NEWER one! 2012 vs. 2006.
