Nothing New in 2022?
Tags: webdev, css, javascript, design
Published: 2021-10-19 06:06:30

What will web development be like in 2022?
What do I wish webdev to be for me? 
What are my personal plans as a web developer?

## 2022 Web Development Trends 🔮❓

I started to write this article to remind myself to keep my eyes open for emerging trends and possibilities in web development and keep learning new technology in 2022.

In autumn 2021 🍃🍂🌿🍁 I visited inspiring conferences  ([beyond tellerrand](https://beyondtellerrand.com) and [Never Code Alone](https://nevercodealone.de/de/nca-conference-duisburg)), meeting inspiring people and getting a lot of useful tips and inspiration. I updated this post in 2022, so maybe I could rebrand it as "2023 Web Trends" now. 😆

### Design Trends

Apart from technological innovations for programmers, I also wanted to keep an eye on design trends, like featured colors, palettes, typography, as well as fresh and useful UX and UI ideas. Which made me change the article's title to "nothing new in 22?"

### Nothing New in Twenty-Two?

A purplish "color of the year" and green-with-purple-palettes featured by Pantone sure look nice, but where's the news? The same color combination had already been a new trend at the end of 2020.

### Unlock the Fonts, Unlock the Fun 🖍️🖍🎨🎉

At beyond tellerrand Conference in November 2021, [Ulrike Rausch](https://beyondtellerrand.com/events/dusseldorf-2021/speakers/ulrike-rausch) and [Bianca Berning](https://beyondtellerrand.com/events/dusseldorf-2021/speakers/bianca-berning) showed how variable fonts, color fonts, handwritten fonts (using ligatures and other open type features to avoid repetitious glyphs), and even variable color fonts could be the next big trend in web design.

### Accessibility 👓🧐🧏

At the same conference, [Molly Watt](https://beyondtellerrand.com/events/dusseldorf-2021/speakers/molly-watt) and Karl Groves showed benefits and failed attempts at accessibility and proved the point, that most people make use of assistive technology at least once in their life.

I am wearing glasses, I have a slight hearing deficiency, but I think I should make an effort to look beyond my otherwise abled and privileged existence to understand other people's challenges as users of websites and web apps.

## My own Plans for the Future

Stop complaining about bullshit tech and just get things done instead. Or at least, complain a little less and make some important decisions in the upcoming months. A little rant about bullshit tech fads can be found at the end of this article.

It seems that most of the money is paid in projects for industrial companies, marketing, and useless products. So I ended up doing some work for impact projects and ecological startups, taking time to learn new technology, and otherwise doing a lot of the usual work that I won't even mention here, but looking back on the past months I am still super happy about my decision to be a self-employed freelance web developer!

### Sustainable Development Goals

[![Sustainable Development Goal 9: industry innovation, and infrastructure](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fjeiff74kpg8d3jwl92j.png)](https://en.wikipedia.org/wiki/Sustainable_Development_Goal_9)

I don't plan to follow tech trends, but I will not ignore them either. I value stable and long-lasting software, especially in the open source, which is why I plan to focus even more on classic front-end technologies like HTML and CSS, as well as on Symfony-based software like Shopware 6 (still have to finish my course to become a certified Shopware 6 developer in 2022).

Apart from that, I want to contribute even more to open source software (at least by providing feedback, bug reports, and sponsorship) and support [developersforfuture](https://developersforfuture.org/), [planted.green](https://planted.green/) and other charitable non-profit organizations and "green" (eco-friendly) startups.

At least I have never stopped learning, so I was happy to discover how my CSS, my favorite programming language, keeps evolving.

I will dedicate a small [DEV blog series to CSS features](https://dev.to/ingosteinke/series/16136) that are either actually new in 2021 / 2022 or new to me, underrated, never used before, or even overlooked and not recognized until lately.

### Features Missing from CSS

Parent selectors and proper container queries will land in browsers soon. Both features have been voted the most requested missing features of CSS in the [2021 state of CSS survey](https://2021.stateofcss.com/en-US/opinions/)

[![missing from css: container queries, parent selector, browser support, nesting. Screenshot from the 2021 state of CSS survey](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/q14f3xl4cs03t6v77gg8.png)](https://2021.stateofcss.com/en-US/opinions/)

### Parent-and-Child Selectors 👪

When working on front-end web projects, I often have to resort to solutions that would have been easier and more clear to code if CSS had [parent selectors](https://dev.to/ingosteinke/css-hasparent-selectors-287c). After first support in Safari at the end of 2021, Chromium will probably be next in 2022.

### Sustainability over Syntactic Sugar 🍂🍯

But what we need most of all, in my opinion, is more sustainability and accessibility. To me, this is far more important than another feature or framework that offers some new "syntactic sugar" or slightly more elegant coding style.  No matter if you like [optional chaining](https://tc39.es/proposal-optional-chaining/) and arrow functions, coding in JavaScript seems to become more graphical and more compact as the language keeps evolving. That being said, the latest innovations in CSS are anything but "syntactic sugar". Take [`:has()` pseudo classes (parent selectors)](https://dev.to/ingosteinke/css-hasparent-selectors-287c) or container queries for example.

[![CSS :has(.parent-selectors)](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rxtlfeslszvsgw0crp3t.png)](https://dev.to/ingosteinke/css-hasparent-selectors-287c)

You can't polyfill parent selectors and container queries with existing language features. That's like chasing a [holy Albatross](https://heydonworks.com/article/the-flexbox-holy-albatross-reincarnated/) as [Heydon Pickering](https://heydonworks.com) has been demonstrating over many years when container queries did not even have a proper requirement specification yet.

## A Wishlist as a Developer 🤓🎨

As I said, there are *some* upcoming features that I hope to use in 2022, especially in CSS. Apart from container queries and parent selectors, there are [more new CSS features like content-visibility](https://torquemag.io/2021/03/new-css-features/) that I did not use in production yet.

I also wish to continue [my exploration of a light-weight full-stack set-up using TypeScript and Tailwind CSS](https://dev.to/ingosteinke/series/13336) that I started as a side project in 2021, thanks to my old friend and fellow developer [Andy Weisner](https://github.com/retinafunk).

## Evolving Elephants of the World-Wide Web 🐘

Before I conclude my rant in the last paragraphs, some more words about PHP and the PHP community. Unlike JavaScript, which is still missing important core language features and handy DOM events (what about a native `debounce` function or `onResizeEnd` and `onScrollEnd`?) and still has a long way to go until its frameworks communities could agree on de-facto standards and best practices (probably never, and probably people would not even want them to converge like Laravel, Cake and Symfony did), PHP has long become a mature and stable language.

### Don't move fast, don't break Things

Ironically, PHP seems to have lost its popularity before the first PSR and is still being despised for all the wrong reasons. Anyway, after all the performance improvements and feature updates of PHP 7 and 8, the next major step to consider might be the announced deprecations in PHP 8.2, so we probably will rely on using stable PHP 7.4 for a long time to make sure our customers can continue to use their WordPress blogs and plugins in the future.

### WordPress Twenty Twenty-Two and Full-Page Editing

WordPress will of course release another [annual default theme, Twenty Twenty-Two](https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/), in 2022, and continue on its roadmap enabling users to do full-page editing with the Gutenberg block editor without resorting to WordPress page builders like Elementor, Divi, or Semplice. WordPress 5.9 will also improve PHP 8 compatibility and intrinsic web design.

As this useful development, at least useful for non-technical low-code end-users, is still part of the first two phases of WordPress’s Gutenberg editor roadmap (easier editing and customization), we will probably not see native multi-language support in WordPress at least not in 2022 yet.

### Open Source and Sustainability 🌎🐬♻️

I hope that diagnostic tools for [Web Vitals](https://dev.to/ingosteinke/optimizing-speed-and-usability-for-google-s-core-web-vitals-1286) and sustainable web development will offer more details and transparency than [WebsiteCarbon](https://www.websitecarbon.com) currently does. Still it might be a good idea to integrate WebSiteCarbon into Lighthouse, like Robin Osborne suggested on perfPlanet. But I still have mixed feelings about [Robin's suggestion](https://calendar.perfplanet.com/2021/) as it makes Amazon Web Services look nicely greenwashed despite Amazon being one of the evil companies that we should not support when we have a choice. See this [article by Pauli Poisuo about Amazon's founder Bezos](https://www.grunge.com/143621/the-dark-truth-about-amazon-founder-jeff-bezos/) for more background on that problem.

I also oppose Chrome's domination of the browser ecosystem. While I mainly use [Vivaldi](https://vivaldi.net), which is based on Chromium, I keep using alternative user agents like Firefox and Edge (which is also based on Chromium). At least the alternative Chromium-based projects refuse to blindly follow every bad idea that comes from Google, like [FLOC](https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea) or the forceful deprecation of `alert()` which [had already shipped to Chrome releases in 2021](https://nsaneforums.com/news/software-news/google-hits-undo-on-chrome-browser-alert-change-that-broke-websites-web-apps-r1610/).

But just when you start considering using Firefox more often again, Mozilla ends 2021 with a [shitstorm about its Bitcoin/Ethereum announcement on Twitter](https://twitter.com/mozilla/status/1476951030638260225)!

## Last and Least: the Web3 Fad 🤮💵💸

Here we are! After struggling to make people understand and embrace the decentralized, accessible, and non-commercial potential that has been an essential feature of the internet from the very beginning, after trying to make sense of "Web 2.0" (was it AJAX, "social media", rounded corners, or just another marketing fad), enter "Web3" with a ton of bullshit claims about the history of the web mostly issued by young fanboys trying to make money while actually being pawns in a game played the the real villains like Mark Suckerburg.

Apart from some potentially interesting innovations and actual use cases for augmented reality in medical technology and smart contracts for digitizing public administration, most of those "new trends" seem to move in the wrong direction.

Crypto, NFT, metaverse and other useless capital bullshit threaten to create a digital dystopia, wasting energy and sucking people into an imaginary cyberspace, instead of rebuilding actual communities, saving our planet and rediscovering humanism!

[The web doesn't have version numbers](https://hiddedevries.nl/en/blog/2022-01-03-the-web-doesnt-have-version-numbers) and it had been all about decentralized networking from the very beginning. Doesn't anyone remember [Usenet](https://en.wikipedia.org/wiki/Usenet)? I enjoyed newsgroups more than web 2.0 forums, slack and discord these days!

About time to sign the [web0 manifesto](https://web0.small-web.org/)!

## Conclusion

I wanted to write an article with "2022" in its title before the new year begins, in a naive attempt of some additional low-effort search-engine optimization, just to see that nobody seemed to care anyway, and in the end I am very happy about it (about the fact nobody seemed to care).

Software development and digital innovation does not follow annual cycles, even less in times of continuous development.

Just do your thing, follow relevant news channels, and connect with fellow developers.