kgthegreat

'One of the first questions people consider with this kind of thing is performance. Personally I don't think performance should be the first question. My philosophy is that most of the time you should focus on writing maintainable code. Then use a profiler to identify hot spots and then replace only those hot spots with faster but less clear code'

1. Tele-inspection of the job. 2. Ship parts required. Tools can come in the same box which then needs to be returned after the job. 3. Tele-supervise the job

Very cool UX stamps to help with wireframing on paper

"Rust competes for mindshare with C++ and D for programmers who are prepared to accept more complex syntax and semantics (and presumably higher readability costs) in return for the maximum possible performance. For example, micro controllers, AAA game engines, and web rendering engines.

Go competes for mindshare in the post 2006 Internet 2.0 generation of companies who have outgrown languages like Ruby, Python, and Node.js (v8) and have lost patience with the high deployment costs of JVM based languages."

Different search terms give different trends: https://trends.google.com/trends/explore?date=all&q=node%20j...

Clojurescript

Clojure

Java

Mongo

Mysql

Postgres

Database

Reason ML

ES 2016

Typescript

Elm

Compiled to JS

No FE framework required

Elixir

Angular

Vue

React

Frontend

NodeJS

PHP

RoR 5 API

Python

Golang

Backend

Poll