Simon Pascal Klein klepas

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;

Use wget to mirror a single page and its visible dependencies (images, styles)

Graphic via State of Florida CFO Vendor Payment Search (flair.myfloridacfo.com)

This is a quick command I use to snapshot webpages that have a fun image I want to keep for my own collection of WTFViz. Why not just right-click and save the image? Oftentimes, the webpage in which the image is embedded contains necessary context, such as captions and links to important documentation just incase you forget what exactly that fun graphic was trying to explain.

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

	#include <time.h> // Robert Nystrom
	#include <stdio.h> // @munificentbob
	#include <stdlib.h> // for Ginny
	#define r return // 2008-2019
	#define l(a, b, c, d) for (i y=a;y\
	<b; y++) for (int x = c; x < d; x++)
	typedef int i;const i H=40;const i W
	=80;i m[40][80];i g(i x){r rand()%x;
	}void cave(i s){i w=g(10)+5;i h=g(6)
	+3;i t=g(W-w-2)+1;i u=g(H-h-2)+1;l(u

	@function color($keys, $function-name: "color") {
	@return get($colors, $keys, $function-name);
	}

	@function c($keys) {
	@return color($keys, "c");
	}

	#!/usr/bin/env ruby

	require 'octokit'

	Octokit.auto_paginate = true
	client = Octokit::Client.new(:access_token=>ENV['GITHUB_ACCESS_TOKEN'])

	repos = client.repos 'ausdto'
	repos.each do \|r\|
	repo_name = r[:full_name]

	.force-show-scrollbars ::-webkit-scrollbar-track:vertical {
	border-left: 1px solid #E7E7E7;
	box-shadow: 1px 0 1px 0 #F6F6F6 inset, -1px 0 1px 0 #F6F6F6 inset;
	}

	.force-show-scrollbars ::-webkit-scrollbar-track:horizontal {
	border-top: 1px solid #E7E7E7;
	box-shadow: 0 1px 1px 0 #F6F6F6 inset, 0 -1px 1px 0 #F6F6F6 inset;
	}

	/// Function to get next map item
	/// returns next map item or fallback value if map, key or next item does not exist
	/// Github Repo: https://github.com/elcheio/sass-map-get-next-prev
	/// Node Module: https://www.npmjs.com/package/sass-map-get-next-prev
	///
	/// @author Simon Koch <[email protected]>
	///
	/// Licensed under the MIT license.
	///
	/// @access public

	@function mapReverse ($map) {
	$result: null;

	@if type-of($map) == "map" {
	$keys: map-keys($map);
	$map-reversed: ();

	@for $i from length($keys) through 1 {
	$map-reversed: map-merge(
	$map-reversed,