Shadowing-Übung: We've got separation of concerns wrong - Englisch Sprechen Lernen mit Video

People like to talk about the separation of concerns, especially when it comes to web development, in a really rigid way.

HTML is for the content, CSS is for making things look pretty, and JavaScript is for handling the behavior and everything else that we can't do with those other things, I guess.

But the fun thing, at least in my experience being a CSS guy, is most of the time when I hear people saying, Oh, separation of concerns, you shouldn't be doing it that way, comes up when somebody is going,

Oh, you shouldn't be using CSS for that, that's the job of JavaScript.

but then they often ignore all the things they're doing with JavaScript that probably should be done by CSS.

And this happens, or has at least happened for a long time now, because we just didn't have a choice.

There was a lot of things that you couldn't do with CSS, so you had to do it with JavaScript, and that sort of just stuck around a lot.

And there's some things that slowly shifts and moves around a little bit, and we get new things in CSS that nobody's complaining about, like, I don't know, anchor positioning, scroll driven animations.

I think we realize that's just styling related.

So that's completely fine.

But as CSS is getting all of these new features and becoming more powerful, especially in my comments section and just through conversations I've had with developers,

I keep hearing that CSS is starting to overstep its bounds.

And so much so that it actually inspired my talk that I just got back from at CSS Day, which was an absolute blast.

So much fun.

So amazing seeing so many people.

But yeah, it was I got inspired at least partially for what I was talking about in

that one where I was actually saying, well, things are going to change.

We're going to push more towards CSS and why that's actually a good idea in my talk.

But one thing that actually came up was Jeremy Keith came to see me and he was like, oh, Kevin, a really good talk, awesome stuff.

But I wanted to let you know that this conversation has been going on forever, which I sort of I'm aware of, but not to the extent that he let me know about because he actually put a blog post out in 2004.

So it's 22 years ago, which is crazy, where this whole separation of concerns thing was coming up

because hover was part of css and whether

or not it should only be for links or

if you could use hover anywhere

and people were like oh wait hover hover should be the

world of javascript that's behavior you're you're what the user's doing on the page

that shouldn't be on css i'll put a link to his article in the description

because it is kind of cool to like look back on on these types of conversations i think

and it's just it's funny how i guess it just never goes away

but i think the main thing is with all of this

is like clearly I think most people these days see hover as a styling related thing.

Yes, it's behavior, but it's also style.

And I think that's the whole problem with separation of concerns in the first place.

The idea of HTML, CSS, and JavaScript being these three things where we're separating into content styling and logic and behavior and all of that,

I think is just flawed.

And I don't think it really even encapsulates the idea of what separation of concerns is

when it comes to programming in general, where it's mostly about simplifying things.

Now, you see this in JavaScript.

If you're doing good, you're writing good JavaScript, you're separating things as much as possible, right?

You want one function to do one thing and not handle seven different things.

That's separation of concerns.

And that's something we should be doing when you're writing JavaScript or any language whatsoever.

But somehow we got this idea of HTML being content, CSS being styles, and JavaScript being the rest, right?

But the problem was JavaScript just filled in all the blanks

of the things we haven't been able to do with the other languages.

And now that things are changing, people are like, oh, a separation of concerns.

That's not how we should be doing things.

And it's like, no, it's not how we should be doing things.

It's, well, we haven't been doing it that way before because we had no other choice.

And it's just, there's this evolution that's going to continue to happen.

And I really think that we shouldn't be worried about it in that way because there is so much overlap.

A scroll driven animation, for example, is behavior.

It's the user scrolling on the page, going up and down, just like a hover would be.

So should that be in JavaScript or should that be in CSS only?

Well, I think it makes a lot of sense to be in CSS only.

I think anyone who's written the JavaScript to create scroll driven animations is probably happy it's only in CSS now

because it simplifies our life so much going from a lot of code to a few lines of CSS.

But it also increases performance

because we're not relying on JavaScript to be constantly figuring things out

and tracking our scroll position everywhere we're going and relaying

that over to our styles and updating inline styles and all of that.

It's a lot of work and now we can just let the browser pass that information directly through.

And to me, that is separation of concerns.

In a big way, we're simplifying things.

We're getting the information directly from the browser.

Invoker commands are very similar, right?

An invoker command allows us to open a modal or a dialog without any JavaScript.

You make a button, you make a dialog, you link them with a couple of attributes, which makes sense.

That's the realm of content.

Let's connect them through an attribute.

I don't see anything wrong with that.

We used to have to do the exact same thing in JavaScript, but you'd make your two elements, go and find them and then link them.

Why not just do that?

So we're simplifying the problem.

We're separating the concerns.

We're saying this button and this dialog or this modal are connected to one another.

We've simplified the matter.

And then when it opens, we style what it looks like with CSS.

Why do we need JavaScript?

We don't.

And it's not because it's behavior related, it's because we're trying to simplify the situation.

And we're making this button and thing that's being opened into this self-contained thing.

That's separation of concerns.

And sometimes with an invoker command, you might need some JavaScript.

And that's completely fine.

That API is available to do some extra things with, including creating custom commands.

Because I believe we can only do modals and popovers with the built-in invoker commands, but we can create custom ones for other types of things you might want to do.

Maybe a button to play a video or go full screen or other things like that, that for whatever reason you need your own button for, where you can make an invoker command for that now.

And that just simplifies everybody's life.

And a little bit of JavaScript is there just to actually add that extra functionality into there, but it's all part of that same system.

And I think looking at things in that way makes a lot more sense.

But instead of getting all excited about how we're starting to simplify things in many ways, in other ways, the web is getting more complicated

because of all of these things that are coming in and these new capabilities that we do have.

But there is a simplification in another way.

I don't know.

Maybe that's a topic for another day.

But instead of getting excited about, yeah, that's really cool.

People are like, oh, you shouldn't be opening a button with HTML.

You know, separation of concerns.

100

This is a problem.

101

And well, is it really, though, making life easier?

102

Is it a problem?

103

or is it just that they're not happy

104

that we're doing it in a different way than they've been told this is how we do things

105

and then they get frustrated and they say this is the wrong direction that things shouldn't be going that way.

106

I think just because we've been so trained on thinking of HTML, CSS and JavaScript in the buckets we have been.

107

And even if you think of it in more of a component-based system, you have your component file and all of the stuff for that component lives in that one file.

108

That's a separation of concerns in many ways

109

And that's why I think component based architectures become so popular because we're keeping everything self-contained, which makes a lot of sense.

110

But then what each one of the languages is doing there, it's handling its job.

111

But again, there's this gray zone, the overlap between what's behavior, what's styling, when should it be styling related, when should it be the behavior as much as possible.

112

I'm a strong believer being a CSS person that if this logic

113

or anything related to what's happening changes how the user sees it, it's updating the visual of it, well then as much of that should be done in CSS.

114

Because to me that makes sense, that's its domain.

115

But again, maybe I'm getting stuck there, I don't know.

116

Maybe it's just because I like CSS a lot.

117

But yeah, if we look at things more in that context, I think that's more of what separation of concerns should be, where we're looking at the element,

118

we're doing it as simply as possible within those languages that we have and in the way those work, instead of being so focused on, well, this is for this one purpose, this is for this other purpose.

119

And this all does raise another question, though, that I'm not too sure about.

120

And this is the one part in these videos I've started asking for what you guys think

121

and the comment sections have been fantastic.

122

So we're going to continue that on this

123

because I don't know what the answer is in terms of how AI is going to impact everything.

124

I wanted to make sure this video wasn't AI focused, but I do have a question on how you think this will be impacted

125

because AI has been trained on like millions of lines of code the way things have traditionally been done.

126

And the web's changed a lot in the last like two years.

127

There's a lot of features that are coming, invoker commands, popovers, dialogues all these things, the modals that we have now,

128

scroll-driven animations, anchor positioning, the list goes on and on and on and on, that aren't really part of those code bases.

129

And I know there's, you know, Google has their modern web thing

130

that can sort of help steer the direction a little bit

131

that I'm not 100% sure is as good as they want us to think.

132

But at least there are these things to say, oh, use these modern features and here's what they do.

133

But if people aren't writing as much of the code themselves, there's less concern about the architecture of that code and who cares

134

if we're doing it in a more complex way

135

that works i mean some people do because there's performance impacts

136

and we should probably be focused primarily on performance uh

137

which often goes by the wayside with ai but uh

138

if people are writing less code themselves is does this potentially

139

lead to a stagnation of all of our languages right

140

because it we have ways of doing things you ask it

141

to do it it can create some stuff you go in you tweak you massage it, you get it to go where you want it to be.

142

But if there's people like me, we continue writing code on our own.

143

And I know a lot of people listening to this are probably in the same boat.

144

But if there's less people doing that, does it put less pressure for the languages to continue to evolve or not?

145

This is a question that a few people asked me at CSS Day that I didn't really have an answer for.

146

It could be one of those unforeseen things that ends up happening, or maybe we continue to evolve or evolves in different ways.

147

Whatever it is, I'd love to to know what you think about

148

that and I'll probably talk about it in a future video.

149

And I think for today that is it.

150

So thank you very much for listening.

151

And of course until next time don't forget to make your corner of the internet just a little bit more awesome.

Was ist die Shadowing-Technik?

Shadowing ist eine wissenschaftlich fundierte Sprachlerntechnik, die ursprünglich für die professionelle Dolmetscherausbildung entwickelt und durch den Polyglotten Dr. Alexander Arguelles populär gemacht wurde. Die Methode ist einfach aber wirkungsvoll: Du hörst englisches Audio von Muttersprachlern und wiederholst es sofort laut — wie ein Schatten, der dem Sprecher mit nur 1–2 Sekunden Verzögerung folgt. Anders als passives Hören oder Grammatikübungen zwingt Shadowing dein Gehirn und deine Mundmuskulatur, gleichzeitig echte Sprachmuster zu verarbeiten und zu reproduzieren. Studien zeigen, dass es Aussprachegenauigkeit, Intonation, Rhythmus, verbundene Sprache, Hörverständnis und Sprechflüssigkeit signifikant verbessert — was es zu einer der effektivsten Methoden für die IELTS Speaking-Vorbereitung und reale englische Kommunikation macht.

Shadowing-Übung: We've got separation of concerns wrong - Englisch Sprechen Lernen mit Video

Über diese Lektion

Wichtige Vokabeln & Phrasen

Übungstipps

Was ist die Shadowing-Technik?