The State of Css 2024

The The State of CSS 2024 survey is now open, and I believe participating is a good idea. Surveys can be a bit boring, but there are several reasons why it’s worth taking part in this one. The most obvious is because you gain knowledge that will help you progress as a developer since eventually, you might not be familiar with a property or set of them, as it’s hard to stay up to date. Another reason is that if you are part of the industry, you are part of this community, and participating in its ceremonies helps you become aware of that (sometimes you help, sometimes you receive help). And another, perhaps less visible but no less important, is that we can make some pressure on the decisions or the direction that technology will take, trying to ensure that new features respond to the real needs of those of us who work with them daily.

How it works

Simple. All the new features related to CSS are categorized into different sections; layout, colors, Typography, math, etc. And in each of them, there are several points about properties or rules with code examples and response options: If you knew it, if you had never heard of it, or if you use it or not. Additionally, you can indicate whether you’re interested in that particular point and add any comments about your personal experience. Finally, you can add the property, function, or whatever it is to your reading list, which you can receive by email to go through at your convenience.

The survey also gives you a score that you can share on social media, but it’s important to be honest because no one really cares if your score was 162 or 400, or at least no one but yourself.

Progressing through knowledge

Participating allows you to evaluate your current knowledge but also identify new trends and emerging technologies. Through reflection on our own skills and preferred tools, we gain a deeper understanding of the current state of technology and the areas that require our attention. This active participation in the process of self-assessment and discovery is essential for our professional growth. By knowing which tools and methodologies are being adopted by the community, we can make informed decisions that drive our careers or simply have a slightly broader view of what new horizons lie ahead or what issues are emerging because you don’t have to know everything.

Being part of a community

Getting involved in the community can be a great way to feel part of the group and eventually be able to give back what you surely borrowed at some point.

Sharing knowledge and experiences is essential for collective progress. Participating in this survey is an effective way to contribute to the well-being of this community, as it allows each member to express their preferences, challenges, and successes. Collective feedback helps shape the future of web development by identifying the most useful tools and practices for everyone. I sincerely believe that participation benefits you personally but also strengthens ties within the community, fostering a collaborative environment where we can all learn from each other.

Taking part in decision-making

Most web developers do not participate directly in drafting technical specifications like those of the W3C, where new CSS properties and standards are defined. However, by participating in surveys like “The State of CSS,” we can indirectly influence these decisions. By expressing our preferences and needs, we provide valuable data that can guide those who make decisions in the right direction. This is a democratic way to influence the evolution of CSS, ensuring that new features respond to the real needs of those who work with this technology daily. Therefore, by participating, we contribute in some way to building a future where CSS is more useful and aligned with the needs of the developer community.

Decisions are not taken in this survey

If you’ve ever read a W3C document, you may have seen who has been involved in the process. Most of them are well-known developers, and almost all participate on behalf of a large company, such as Google, Apple, Microsoft, IBM, etc. For example, in the Layout Module Level 2 document, you can find the editors at the top of the document.

If you’re wondering how to participate directly in a W3C working group, I can tell you what I know. It usually requires being a member of the W3C (although there are ways for non-members to participate as invited experts or in community groups), and there are two types of membership: corporate and individual. Both require paying a high annual fee that varies based on several factors. In the case of corporate membership, member corporations have the right to nominate representatives to participate in the working groups.

The cost depends on the type and size of the organization, as well as its geographic location. These are the costs for a company based in Spain, but we could say that the average price for SMEs is between $7,900 and $19,500 USD depending on the company, revenue, etc. And for large international companies, between $60,000 and $77,000 USD per year.

So, being able to have a bit of a voice and vote without having to shell out those amounts is quite appealing.

On the other hand, if you think that large tech companies (who are the ones who can afford these fees and put sector professionals to work full-time in the working groups) do so with the intent of steering or aligning technology with their products or commercial interests, don’t worry, because it’s a known and previously discussed issue. While these individuals have a direct participation and voice and vote in critical decisions, the W3C uses a consensus model that seeks broad agreements among all participants (including invited experts). Additionally, there’s public review, as specifications and proposals go through multiple stages of public review, allowing the broader community (including independent developers and small businesses) to give their opinion and comment. Lastly, there are Public Interest Groups, which are groups and forums open to public participation (which do not require membership), so anyone can participate, allowing for more diverse representation and preventing a single entity from dominating the process.

Conclusion

Another very interesting topic is the results and the insights that can be drawn when the survey closes. You can see the level of penetration or adoption of a technology and the average profile of a developer interested in CSS, or at least those who participate. And draw some conclusions. We’ll see what 2024 has in store for us, and I hope you take part in this initiative.

Resources

• State of CSS 2023
• W3C
• W3C Membership Fees