Julian Dax brodo

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

	const std = @import("std");

	pub fn main() !void {
	var gpa = std.heap.GeneralPurposeAllocator(.{}){};
	const allocator = gpa.allocator();

	defer {
	const deinit_status = gpa.deinit();
	if (deinit_status == .leak) @panic("TEST FAIL");
	}

	# This file is licensed under the terms of the MIT license https://opensource.org/license/mit
	# Copyright (c) 2021-2025 Marat Reymers

	## Golden config for golangci-lint v2.1.2
	#
	# This is the best config for golangci-lint based on my experience and opinion.
	# It is very strict, but not extremely strict.
	# Feel free to adapt it to suit your needs.
	# If this config helps you, please consider keeping a link to this file (see the next comment).