Max Claus maxclaus

How to use clangd C/C++ LSP in any project

tl;dr: If you want to just know the method, skip to How to section

Clangd is a state-of-the-art C/C++ LSP that can be used in every popular text editors like Neovim, Emacs or VS Code. Even CLion uses clangd under the hood. Unfortunately, clangd requires compile_commands.json to work, and the easiest way to painlessly generate it is to use CMake.

For simple projects you can try to use Bear - it will capture compile commands and generate compile_commands.json. Although I could never make it work in big projects with custom or complicated build systems.

But what if I tell you you can quickly hack your way around that, and generate compile_commands.json for any project, no matter how compilcated? I have used that way at work for years, originaly because I used CLion which supported only CMake projects - but now I use that method succesfully with clangd and Neovim.

Custom format for displaying bytes as kb, mb, gb or tb.

Response to a few places on the internet: https://productforums.google.com/forum/#!topic/docs/x_T_N-yRUYg And here: https://stackoverflow.com/questions/1533811/how-can-i-format-bytes-a-cell-in-excel-as-kb-mb-gb-etc

Here is one that I have been using:

[<1000000]0.00," KB";[<1000000000]0.00,," MB";0.00,,," GB"

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;

Minimum Viable Async with Node 6

With the release of Node 6.0.0, the surface of code that needs transpilation to use ES6 features has been reduced very dramatically.

This is what my current workflow looks like to set up a minimalistic and fast microservice using micro and async + await.

The promise

HOW to CREATE a commit using github API

1. Get the Reference of the branch you want to commit to and store the SHA for the latest commit (SHA-LATEST-COMMIT)

https://developer.github.com/v3/git/refs/#get-a-reference

  const res = getReference( BRANCH );
  const baseCommitSHA = res.object.sha;

2. Get the sha of the tree

https://developer.github.com/v3/git/commits/#get-a-commit

	package main

	import (
	"fmt"
	"golang.org/x/text/encoding/charmap"
	)

	func main() {
	for i := 0; i <= 255; i++ {
	charnum := uint8(i)

	# Version key/value should be on his own line
	PACKAGE_VERSION=$(cat package.json \
	\| grep version \
	\| head -1 \
	\| awk -F: '{ print $2 }' \
	\| sed 's/[",]//g')

	echo $PACKAGE_VERSION

	# Version key/value should be on his own line
	PACKAGE_VERSION=$(cat package.json \
	\| grep version \
	\| head -1 \
	\| awk -F: '{ print $2 }' \
	\| sed 's/[",]//g' \
	\| tr -d '[[:space:]]')

	echo $PACKAGE_VERSION

	package main

	import (
	"encoding/json"
	"log"
	"net/http"
	"reflect"
	"time"

	"github.com/gorilla/context"

	# Simple version using only "find"
	find . -name "node_modules" -type d -prune -exec rm -rf '{}' +