Google's go

rate it on a scale of 1 to 10 on the basis of the following criteria :

- writability

- readability

- optimizability

- extensibility

- security

- portability (but seriously, who give really a fuck about portability except java faggots?)

- writability = 2 (1 would be assembly, without macros)
- readability = 2 (1 would be assembly, without macros)
- optimizability = 6 (Go is no assembly and garbage collection is unpredictable)
- extensibility = 1 (absence of preprocessor makes metaprogramming worse than C)
- security = 2 (forced array bounds checking give +1)
- portability = 2 (C/C++ has a compiler for every platform)

- security = 2 (forced array bounds checking give +1)

at runtime so it's almost useless

- optimizability = 6 (Go is no assembly and garbage collection is unpredictable)

they also tried to put pointers, mutable and shared state in a concurent enviroment with GC
this makes it shit for optimisation, plus that the go compiler is not a optimising beast

>>3

at runtime so it's almost useless

Instead of allowing shellcode, it will just crash and sys-admin will notice the crash in a log file.

this makes it shit for optimisation, plus that the go compiler is not a optimising beast

Well, set it to 5. Go still has more predictable performance than Haskell (no lazy evaluation) and easier to compile efficiently (no dynamic typing - no JIT required to optimize call-sites).