I'm still fairly new to programming and have been learning for a few months. I decided to build a website using HTML, CSS, and JavaScript, and getting started was pretty straightforward. However, whenever I want very specific behavior—such as making images zoom in or out in a particular way—I find it difficult to know how to approach the problem because CSS handles so much through a high-level layout and styling system.
Before web development, I experimented with graphics libraries like SFML to make small games. I enjoyed having to build many things myself because, once I understood the underlying systems, I had a lot of control and didn't need to constantly look things up. Of course, that also came with plenty of headaches.
Is there a practical way to develop websites at a lower level? Is this loss of direct control a common frustration for other developers, or should I focus on learning the fundamentals and getting comfortable with the browser's way of doing things?
4 Answers
CSS itself isn’t necessarily hiding everything behind a library; it is a different programming model. It can feel unintuitive because many solutions depend on understanding how layout, sizing, positioning, and the cascade interact. Experimenting with small isolated examples and studying working implementations can help, but there is definitely a learning curve.
The transition from a game loop, where you control every drawing operation, to CSS can be jarring. CSS is declarative: you describe the result you want and the browser works out the layout across different screen sizes and devices. Canvas and WebGL can provide a more direct graphics experience, but for regular interfaces you’ll eventually need to learn the browser’s layout model and its collection of CSS techniques.
Browsers are intentionally sandboxed and abstracted from the rest of the computer. WebAssembly can let you run code compiled from other languages, and rendering can also happen on a server, but those approaches don’t remove the need to produce HTML and CSS for a normal website. The platform has accumulated decades of standards, so some parts are awkward, but learning to work with those constraints is usually more practical than trying to bypass them.
For normal browser development, HTML, CSS, and JavaScript are already about as low-level as you usually get. You can eventually explore WebAssembly, Canvas, or WebGL, but those are specialized tools and probably aren’t the best starting point. Build a few projects with the core technologies first, then consider a framework once you understand what problem it solves.
That makes sense. It sounds like the lack of direct control is normal, and that becoming familiar with the common CSS patterns is part of learning the platform.