Well comparing Go and PHP is kind of difficult, because they are targeting completely different goals. After some years of development, both languages have evo

Well comparing Go and PHP is kind of difficult, because they are targeting completely different goals. After some years of development, both languages have evolved a lot and they both can be used for many other things, that they haven't been designed for. PHP was a dynamically typed scripting language to build personal homepages (Personal Home Page Tools). Today it is an object oriented, type hinted language that supports functional and object oriented programming, many database management systems and has a package manager (composer). I really like PHP (see https://github.com/sandreas/m4b-tool https://github.com/sandreas/m4b-tool for a proof), but some concerns about PHP have always been (and still are): - backwards compatibility reaching too far - way too big standard library (see levenshtein function) - the "callable" concept - call_user_func_array([$obj, "method"]) - mixing up too many concepts (OOP, Traits, Functional style) - the type system (which is getting better with php 7) - unpredictable statements - empty($x), comparisons (== vs ===) and the "mixed" type - the "array" type being array and dictionary and... - the $ used for variable declaration - $this-> is still needed for calling object methods - "." for concatenation and "\" for namespace separation Another bad thing about PHP is, that on most web servers it is meant to be stateless, which means that you are in trouble using technologies like websockets. Some of these things unfortunately mean that PHP often is much slower than it could be - and this is where "go" can be a successor. Performance. If you really need FAST web apps and performance is the goal, go can be a nice choice. But for getting things done in a not too complex web page, i would always choose php.