Oh yeah it's so unpleasant not having to see creepy and gross shit in the work place because some horny dork never grew up. Gosh won't someone please think of the incels?!
Why would you assume other men want to see that shit either? It's weird, creepy, unprofessional, and weird and creepy. Mostly weird and creepy though. Like are you so lonely and horny that you need to plaster your shit with half-naked women?
Did Blizzard ever give a reason for not supporting Macs? They used to be really good about supporting them (I played a lot of WoW on one for years with zero issue). Guessing the extra effort required to support ARM didn't make financial sense?
For a few years during the Playstation 2's reign, I used a PS/2 -> USB adapter on my PS2 for my keyboard so I could text-chat while playing Tony Hawk games online. Always saw some humor in that.
It's funny how eternal the IE6/7/8 struggle felt at the time and now it's essentially ancient history. All that knowledge of how to coax CSS into doing things cross-browser circa 2004-2010 is basically useless to me now. Those years were my HS hobby -> college -> career transition period and it's amazing that I didn't give up because of how god damn convoluted basic frontend development was back then. And it was so discouraging because you could do things by the book (er, spec) and they'd work flawlessly in Firefox, but look assbackwards in IE6.
I'm sobbing like a baby while my 5yo twins are watching TV nearby. That is such a 5-going-on-6 decision to make, which just drives the whole thing home for me and I can't handle it right now.
I've always loved the existence of "rebeccapurple", but I somehow missed that part of the story. Her color being immortalized in the CSS logo (even if it changes years from now) is so incredibly beautiful to me.
I've been out of the WP community/scene for a number of years now, but this post is kinda weird. Revisions definitely aren't the hill I'd die on when choosing a hosting provider at all. Especially considering WPEngine does a lot of things very well:
1. Dead-simple staging environments
2. Support for Local, which makes WP development an absolute breeze because I don't need to maintain docker, vagrant, or a LAMP stack, etc. And it makes deployments quick/easy.
3. Dead-simple backup/restore features
4. Simplified cache-management
And yeah, I've got the technical know-how to handle all of that myself directly on a proper server and all that devops-y goodness. And yes, $5/mo shared hosting cPanel provider would be comparable (and let's be real, it's good enough for most people using WP)....But man is it nice to just charge/pay a little more for a host that just does that crap for me with a nice interface.
I like revisions as a feature. Hell, I made reference to them a lot in the training material and sessions I put together for clients way-back-when as a way to give clients the confidence to tweak copy without fear of completely ruining their site. But this blog post seems to pretend it's the heart of WP and without it, it's an entirely different piece of software all together, which is absurd.
We got the same pep talk at the beginning of the year. They wanted to give us developers more autonomy, the ability to move faster, etc. Sounds great on paper as there were a lot of useless meetings and chat channels we wasted a lot of time in.
But the solution was to eliminate the release manager role and move QA away from testing individual tickets and instead toward developing/managing automated testing. And then the devs had to pick up the QA and release responsibilities without any change in our original responsibilities.
Which means that I now waste a massive chunk of my work week doing things other than write code. All the while they're making a big stink about "coding days". Which has pretty much never ended well for developers. I'm sure next they'll be counting total lines of code, too.
No it's fine! They'll just continue to merge with shitty media companies until the previously good HBO name is entirely worthless and the debt is some other overpaid executive's problem!
Maybe this is an annual payment thing? Because I paid monthly and cancelled the other day online and it offered to refund me back $2 and some change left in my current month.
Personally, I wouldn't mess with tailwind until you have the fundamentals of CSS sorted out. To use a PHP example...Whereas you're actively writing a lot of PHP when using frameworks like Laravel or Symfony, and can learn from that process, you're not really writing a lot of CSS with tailwind. You're mostly just adding classes to elements and supplementally adding some styles on top of that.
I would jump right into modern things like flexbox and the grid system as the old ways of floating are basically useless. I mean they still work, but I can't remember the last time I had to use a float to create new layout. Start with flex, as it's a bit more beginner friendly than grid is. I've been doing this for nearly 20 years now and I still struggle to wrap my head around grid sometimes.
You can ignore BEM until you've got the fundamentals sorted. BEM is just a clean standardized way to organize class/id names, it's nothing functional.
Sass helps streamline things a lot via nesting and variables to begin with. More advanced features can also be useful, but until you've got the fundamentals it may not be clear where those advanced features can be applied. And Sass requires substantial more initial setup than plain CSS (you'll need Webpack or gulp or something to turn the Sass into CSS). Not to mention that Sass's biggest draw is variables and nested styles, which CSS now supports natively (albeit with really weird syntaxes, imo). So I'd skip Sass for now.
And yes, you can jump into an existing page and tweak it. That's how I learned it initially. https://csszengarden.com is a good resource for that. It's the same basic HTML site with different CSS themes you can load. It's a good showcase of how powerful CSS is what you can do with it without touching the underlying HTML. Dev tools are very useful there as you can turn individual styles off, change their values, etc.
Lastly, I'd just start with a blank page and try to create a simple 2-column layout. Narrow left column with a basic navigation in it and a wide right column with a few paragraphs of text in it. Then build off of that -- add a header and a footer. See if you can get the header to "stick" while you scroll down the page, etc.