5 ms·
As someone who has little direct experience with this part of webdev (other than aligning paragraphs once in a while for really basic static text sites), I have
by vanderZwan 11y ago
As someone who has little direct experience with this part of webdev (other than aligning paragraphs once in a while for really basic static text sites), I have to wonder: is the fact that flexbox requires a 20-part video course a sign of it being:
- 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.
- wesbos 11y agoAuthor here - it's just 20 videos broken apart into each topic so when you need to come back to reference something, it's quick. 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!
- kylestlb 11y agoThanks for putting up the effort to do this. For some of us, video tutorials w/ narration are much easier to absorb than one off blog posts!
- Numberwang 11y agoIf I learn this, is this all i need to use for CSS layout from now on? Or is there more to learn?
- wesbos 11y agoYou'll still need floats to text and images, but this takes care of quite a bit any float based layouts
- mbrock 11y agoYou can't draw any such conclusions from the existence of a series of 20 short tutorial videos. I could make 20 videos about how to use ls.
- madeofpalk 11y ago> - an inevitable consequence of trying to solve an inherently difficult and complicated problem? 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.
- dahart 11y agoI cant speak to these videos, but most flexbox tutorials are quite long. The number of videos may be a sign of completeness. 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.
- weego 11y agoIt's just a sign that a section front end people are obsessed with making trivial things seem complicated. I mean https://css-tricks.com/snippets/css/a-guide-to-flexbox/ https://css-tricks.com/snippets/css/a-guide-to-flexbox/ literally just gives you what you need in a skim-readable page.
- toxican 11y agoIt me took about 15 minutes of reading an article to get a basic understanding and start using some basic functionality. I'd imagine the 20 videos explore every crevice of Flexbox, which you don't necessarily need to start using it.
- jasonkostempski 11y agoDynamic layout is a hard problem. I've never come across a layout engine that didn't require at least a day to get comfortable with. Some may have the advantage of being similar to something you've used before and might give you a head start but that can also slow you down when you assumed it's exactly like the other when it's not.
- Animats 11y agoIf you want to see a completely different approach to dynamic layout that makes more sense, check out the constraint system in the 2D sketch system of Autodesk Inventor. It's all visual, controlled through a GUI; you select two points or two lines or a point and line and apply constraints such as "coincident" or "perpendicular" or "parallel" or "tangent". You can also give things explicit dimensions, which may be computed from other dimensions. The GUI stops you if you try to insert incompatible constraints. You can put in text, too, so you can actually use it as a layout engine. There's no notion of "line break", though; it won't change the number of things in a row if you change the outer bounding width. 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.
- vbezhenar 11y agoI don't know about Flexbox, but I never saw easy and powerful layout libraries. They can be easy, but with very basic capabilities (Delphi 7) or they can do almost anything, but with a lot of concepts and complex API (Java Swing, Java FX, Cocoa, Qt, HTML positioning in general). I guess, that efficient layouting is just not a simple problem.
- exodust 11y ago> is the fact that flexbox requires a 20-part video course 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.
- giacomone 11y agoLooks like the author uploaded all videos on Youtube though: https://www.youtube.com/playlist?list=PLu8EoSxDXHP7xj_y6NIAhy0wuCd4uVdid https://www.youtube.com/playlist?list=PLu8EoSxDXHP7xj_y6NIAh...
- woah 11y agoI don't think that you should be in the habit of making technical decisions based on the number of videos or something. Take 1.5 minutes to read a web page on flex box and realize that it consists of putting boxes into boxes, deciding the alignment and how much space they will take up. I haven't watched the videos but it seems strange that there are 20 of them.
- elros 11y agoAs someone who pushes pixels around every day for a living – among other things, of course – I'd say option 3. 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.
- roneesh 11y agoFlexbox takes a few hours of work to learn, as others here have said. However, once you learn it, you have a logically sensible system of layout. It's worth the time. As far as it's quirks go, that's because it was slow to be standardized, so there is outdated info out there. 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.
- arihant 11y agoIt's the sign of having more videos of shorter length than having less videos of longer length. Most basic HTML courses are around 20-25 parts. That does not mean HTML is rocket science, or a broken mess.
- furyferret 11y agoIt's just web developers who lived in a world where front-end layout was supposed to be hard and who distill complexity out of four or five trivial CSS properties to convince themselves that all of the hours they lost aligning divs with floats or bootstrap weren't pointless, and that the new way must be as complicated.
- kelvin0 11y agoEvery time I finally resolve to start doing some Web Front-end stuff, I have the same reasoning as you put forth ... and I go back to coding my frontend in wxPython. I just don't know where to start, and nothing seems to last more than a few weeks until a shinier thing pops up... I need help!