Is flexbox hard to learn? Yes, but it's because it's such a powerful layout tool. There are tons of gripes about Flexbox, but I've found that if you just put in a few hours to learn it, you are going to be way ahead in your CSS and layout game.
We haven't had to learn anything hard in CSS for years and now it's time. Hunker down and get at it!
Or is there more to learn?
The core of flexbox, and the most powerful and commonly used parts, isn't that much material, and isn't very hard to learn. But there's a long tail of corner cases and tricks and special situations.
There's one other reason too: flexbox is at it's most powerful and most simple, IMO, when you put flexboxes inside other flexboxes. But that inherently mixes markup and styling. Some of flexbox' features are designed to help you avoid mixing markup and styling, but that adds to the complexity.
CSS is somewhere between inherently complicated and a broken mess. That's not the most charitable way to put it, but not entirely inaccurate either.
If you start to learn the older tools to do page layout, you can learn each one a bit faster (float, positioning, display properties), but combined they do NOT form a consistent logical system of page layout. Your learning is just repetition to see what works, Googling of CSS tricks and then hopefully you develop some intuition about when to use which property to achieve your desired effect. This confusion is why Flexbox is a net positive comparatively.
With flexbox you can know what elements will do when you apply a CSS property pretty assuredly (well, if not now, in the near future). Without, it's a bit more learn by error. Flexbox is a brighter future.
Flexbox is actually relatively simple for the common use cases (absolute centering, distributing leftover space between elements etc).
If you have more complicated layouts, there's a lot more to the Flexbox spec that will help you out.
It's not a fact.
Nor is it a fact that to access videos on the web requires an email address! In both cases the author has chosen to do this for whatever reason.
The thing about layout styles for CSS that people seem to miss is that you don't have to choose a single one one. You can mix floats in one area of the DOM with Flexbox in another area and Grids (once they're ready) in yet another area, and they'll work well – provided they're properly siloed – because they're mostly targeted at solving different issues, layout-wise.
I mean https://css-tricks.com/snippets/css/a-guide-to-flexbox/ literally just gives you what you need in a skim-readable page.
I haven't watched the videos but it seems strange that there are 20 of them.
This is much more comfortable for designers than trying to do it through a set of declarations with no consistency checking. A constraint engine really is the right tool for the job. It also maps well to a GUI, which CSS does not.
The constraint system isn't limited to horizontal and vertical. You can have circles, arcs, and even splines. Graphic designers would love to have such capabilities in web design.
Most basic HTML courses are around 20-25 parts. That does not mean HTML is rocket science, or a broken mess.
- a broken mess,
- a less broken mess than what came before it,
- an inevitable consequence of trying to solve an inherently difficult and complicated problem?
- some combination of the above?
Either way, nice of Wes Bos to provide such a tutorial, will have a look.