Yep; but its worse. A lack of knowledge doesn't just stop you from building some applications. If you don't know what you're doing, its really easy to accidentally end up with security vulnerabilities in the software you make. I don't want my data ending up in yet more have-I-been-pwned dumps because beginners don't learn the basics.
Eg, lots of stack overflow answers recommend setting "Access-Control-Allow-Origin: *" to "fix" certain errors. Cross-origin messages are disabled by default in modern browsers for a good reason. No matter how convenient it is, you should understand the implications before opening flood gates like that.
HTTP is the wheels, HTML is the chassis, CSS is the paint and JS is the instrument panel. APIs are your roads and JS/CSS web frameworks are the upholstery and infotainment panel, nice pretty features that are easy to modify and customise, carried along by the rest of the stack.
I wouldn't expect web devs to read the browser source code to see how the sausage actually gets made, the fuel injection cycle so to say. However if you can't tell a HEAD from a GET or learn about Content-Type, Content-Security-Policy and all the other headers that will make or break your applicantion in practice, you're severely limiting yourself.