Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Things I wish I’d known about CSS

cssfordesigners.com

Post reply on HN
Print view View original

221–230 of 340 posts

Re: Things I wish I’d known about CSS

#221

Post by rusticpenn »

wirespot wrote: post #103
rusticpenn wrote: post #51

Earlier quoted context omitted.

Yes, This is the main difference. In Germany the education is free and medical insurance not something to worry about ( I have no idea about what deductables, deletables etc mean). This is where the difference lies.

As simple rule of thumb an employer in the EU has to pay roughly double the net salary amount, so on top of the salary pocketed by the employee yet another similar amount goes to taxes. The education/insurance aren't "free", they're just managed better and give more direct benefits to the taxpayer.

It depends. When I was a student, I did not have to spend a penny on medical biils, my wife got paid by the government for some courses (+ cost of rent etc) that would have costed us around 20K € at that time. Now that we are earning enough, I have no problem in paying back, so that others who need it will be also be able to achieve their dreams.

Re: Things I wish I’d known about CSS

#222

Post by the_other »

onion2k wrote: post #203
Someone1234 wrote: post #164

Earlier quoted context omitted.

> Flexbox is supported back to IE11. Nope. An incompatible and broken version of Flexbox is supported in IE11. Therefore, layouts look completely different (and broken) when rendered in it. Only people who recommend Flexbox in IE11 haven't tried using it in IE11. I might via a library that did the heavy lifting for me, but there's just too many bugs to recommend anyone write Flexbox and expect it to just work -- it w…

I write a fairly substantiate app (60,000 DOM elements...) that uses flexbox and SVG for all the rendering and it's fine in IE11. The layout problems are more often SVG related. That said, if you don't need to support IE11 it's much easier not to.

Did you use AutoPrefixer/PostCSS?

Re: Things I wish I’d known about CSS

#223

Post by rusticpenn »

sushshshsh wrote: post #136
rusticpenn wrote: post #51

Earlier quoted context omitted.

Yes, This is the main difference. In Germany the education is free and medical insurance not something to worry about ( I have no idea about what deductables, deletables etc mean). This is where the difference lies.

Deductable is a scary word but a simple concept, it represents the amount of money you must pay before your insurance begins to pay bills for you :)

That is scary. When my child had to stay in the hospital for a month, the main costs for me were the parking tickets.

Re: Things I wish I’d known about CSS

#224

Post by chrismorgan »

leephillips wrote: post #188

I don’t thnk the author’s recommendation to include img { display: block; } in your reset is generally a good idea. It will break some common uses of images, for example to hold bits of math inline with the text when you are not using mathjax. If you want a displayed image, you should wrap it in a tag, which will give you a block element.

If you wrap an image in a figure, but leave the image still inline, you’ll probably get a few pixels of extra space at the bottom of the image due to line-height and vertical-align. People find that really confusing. With how most people use images, I agree that `img { display: block; }` is what you want >99% of the time, and would rather people reverse it for the rare occasion when they want something else. (BTW, doesn’t MathJax emit SVG? Viz., not anyway.)

Re: Things I wish I’d known about CSS

#225

Post by runarberg »

gklefnbkon wrote: post #206

People really didn't know this? To be clear, I'm not criticizing anyone for not knowing this stuff, as nobody can be expected to know everything (and everyone was a beginner at one time). I'm just surprised that within this community, where a lot of us are employed to build websites, that the basics of CSS are still a mystery to so many of us. And I don't think that's the fault of any individual. But clearly our indu…

I think the industry has an attitude problem towards the front end stack. HTML and CSS is not what programmers do. Nobody takes the time to learn it, everybody neglects it, managers hand it over to their newest junior developer, project managers are happy as long as it looks shiny, bootcamps don’t teach it properly, curriculums don’t teach it properly. In the end we have a bunch of people that don’t know anything about the craft, that accept poor craftsmanship as an industry standard.

I had a conversation about this with my partner—who is a woodworker—this morning after reading this thread. I explained my perception of the status of front-end within our industry as such:

It’s as if woodworking and carpentry were synonymous. There are woodworkers that do cabinetry, but all of them learned carpentry. At most they took a single course on cabinetry, but that course probably used outdated methods, tools designed for carpentry, and the teacher them self has build a couple of chairs and a few tables in the past. Most of the people new to the field of cabinetry would come for bootcamps that last for maybe a month where they had to learn woodworking from scratch. Good furniture makers are only expected to be good at woodworking in general. Master carpenters are often expected to be able to finish—or at least manage—furniture projects at their job.

You can imagine the sloppy craftsmanship you would see in the furniture building industry if that were the case. And yet, as tech workers, here we are.

Re: Things I wish I’d known about CSS

#226

Post by benrbray »

IggleSniggle wrote: post #204
jb3689 wrote: post #181

CSS is such a weird abstraction. Who thinks in blocks and inline blocks? Who thinks in paddings and margins? Floats, etc? I know these are more flexible, but I've always found grid-based frameworks to be far more intuitive

Dear lord it's 2020 CSS has its own grid system, it's CSS Grid, and it's both easier to understand and more flexible than adopting the old frameworks. It also has variables, pseudo-selectors (which, like with html elements, you can invent new ones to suit your purposes), and more.

Is creating your own pseudo-selectors really possible? I like to think I'm pretty up to date on modern CSS but I've never heard of this.

Re: Things I wish I’d known about CSS

#227

Post by [deleted] »

miiiiiike wrote: post #65
jb1991 wrote: post #31

Yikes. I've been earning 6 figures as of about two years ago doing mostly HTML and CSS UI design for a bank. And I still did not know about many of these! I guess they are things I wish I'd known about CSS! Better late than never I guess.

I've never been happy with a front-end dev that I've paid six-figures to. I once paid a senior front-end engineer far too much to do a fairly involved layout. Three months, an uncountable number of bugs, and one unusable tangle of Sass later I pulled the plug and swore off ever hiring a "CSS Person" again. I took the Linus+Git approach and said "I'm not writing another line of Python until I understand CSS." After a…

[deleted]

Re: Things I wish I’d known about CSS

#228

Post by leephillips »

chrismorgan wrote: post #224
leephillips wrote: post #188

I don’t thnk the author’s recommendation to include img { display: block; } in your reset is generally a good idea. It will break some common uses of images, for example to hold bits of math inline with the text when you are not using mathjax. If you want a displayed image, you should wrap it in a tag, which will give you a block element.

If you wrap an image in a figure, but leave the image still inline, you’ll probably get a few pixels of extra space at the bottom of the image due to line-height and vertical-align. People find that really confusing. With how most people use images, I agree that `img { display: block; }` is what you want >99% of the time, and would rather people reverse it for the rare occasion when they want something else. (BTW, do…

I’m confused by your reply. Did your eye skip over the word “not” in my comment?

Re: Things I wish I’d known about CSS

#229

Post by runarberg »

steve_adams_86 wrote: post #6

I’ve always thought of ch as a unit intended for monospaced fonts or languages with monospaced characters. Does anyone know of any other practical uses?

Yes. A good column width or grid card inline-sizes is between 30ch and 45ch, generally you don’t want text to exceed 90ch.

These numbers come from print design for magazine or journal layouts. In general the `ch` unit is perfect for defining the inline-size of text containers.

Re: Things I wish I’d known about CSS

#230

Post by chrismorgan »

soperj wrote: post #202
theelous3 wrote: post #141

Earlier quoted context omitted.

Cobbler here, currently cobbling a frontend (am a backend dev by trade). The issue for me is the format these courses and resources take. CSS is the most jam packed with non-intuitive technology I've met. How many dozens of pages or segments of video would I have to go through in a course to learn what the author in OP summarised in two or three sentences? Any time I've considered the structured approach for somethin…

> Behold, 8 zillion words and symbols across 7 trillion seemingly randomly organised boxes full of both all of the information, and simultaneously none of the information, about css grids. It's interesting, because that's my go to resource for CSS Grid. I find it super handy when I forget something. Although, I'm not learning grid, I'm using it.

> Although, I'm not learning grid, I'm using it.

Precisely. What CSS-Tricks calls a guide is actually almost entirely a reference. It makes a tolerable reference if you already know what you’re looking for. It’s a poor reference if you don’t know what you’re looking for because it’s insufficiently structured and takes waaaaay too much scrolling to explore. (It used to be more manageable—it used to be more a guide. It has been allowed to grow far beyond a healthy point.) And it’s atrocious as a guide.

Post reply on HN