[s1k3s]

Do you have any previous experience with programming? Because if you don’t, leaping from HTML + CSS to JavaScript is a huge task. JS is programming, the others aren’t. I know people tend to put them together because that’s the regular FE stack, but the learning curve and skills required to do JS are way different than the other two. So I think you should just keep at it, but also keep in mind that JS is a programming language and you’re essentially learning a whole new thing there.

[denton-scratch]

> keep in mind that JS is a programming language

It's more than a programming language; it's a really big programming language, with quite a lot of backward-compatibility cruft. There are many ways you can use Javascript, but should not. I've been writing Javascript for years, but my JS code isn't fluent, stylish or even modern.

Before I retired I was a senior; but the fact is, it was the youngest guy on the team that was the best at sizing-up Javascript problems - so I would in the end rely on him. But I would first hit the problem with my head until I had a headache, not wanting to waste my teammate's time.

My teammate was actually interested in Javascript; he would go to classes and conferences. I wasn't - I never liked it. My strengths lay elsewhere.

[eurasiantiger]

HTML and CSS are programming languages too—documents in those languages are declarative programs for the browser’s layout engine.

The way one writes their CSS selectors against their HTML structure has huge real-world performance implications, but people rarely care to think about what actually happens under the hood as a browser parses their documents and generates an image on the screen.

[whtrbt]

I agree that HTML + CSS are very different, but why do you say they aren't programming?

[s1k3s]

Bad wording on my side, but I think you get the point.