add new post from pixelstech

README.md

@@ -86,16 +86,6 @@ You're writing some code. And suddenly you understand you need something that la
   - type inference is too simple
   - no immutables
   - no pattern matching
-+ https://www.upguard.com/blog/our-experience-with-golang (Mark Sheahan, 2014)
-  - no decent IDE
-  - error handling
-  - unexpected variable shadowing
-  - no generics
-  - not-so-obvious slices behaviour
-+ http://dtrace.org/blogs/wesolows/2014/12/29/golang-is-trash/ (Keith Wesolowski, 2014)
-  - the worst compiler toolchain ever
-  - psuedointellectual arrogance of Rob Pike and everything he stands for
-  - confusing and undebuggable
 + http://www.yinwang.org/blog-cn/2014/04/18/golang (Wang Yin, 2014)
   - confusing/stupid syntax
   - immature toolchain
@@ -107,25 +97,37 @@ You're writing some code. And suddenly you understand you need something that la
   - defer is abused
   - stuck in Unix thinking
   - summary: not elegant as Python, not strong as Java
++ https://www.upguard.com/blog/our-experience-with-golang (Mark Sheahan, 2014)
+  - no decent IDE
+  - error handling
+  - unexpected variable shadowing
+  - no generics
+  - not-so-obvious slices behaviour
++ http://dtrace.org/blogs/wesolows/2014/12/29/golang-is-trash/ (Keith Wesolowski, 2014)
+  - the worst compiler toolchain ever
+  - psuedointellectual arrogance of Rob Pike and everything he stands for
+  - confusing and undebuggable
++ http://byrd.im/go-is-poor/ (Ian Byrd, 2015)
+  - not-so-obvious slices behaviour
+  - nil interfaces are not entirely nil
+  - unexpected variable shadowing
+  - no first-class support of interfaces
+  - questionable compiler rigidity
+  - go generate is a quirk
 + https://kaushalsubedi.com/blog/2015/11/10/golang-sucks-heres-why/ (Kaushal Subedi, 2015)
   - no generics
   - slow json parsing
   - bad dependency management
   - no subpackages
-+ http://spaces-vs-tabs.com/4-weeks-of-golang-the-good-the-bad-and-the-ugly/ (Freddy Rangel, 2015)
-  - not-so-obvious slices behaviour
-  - error handling
-  - hard to test, hard to mock
 + http://www.evanmiller.org/four-days-of-go.html (Evan Miller, 2015)
   - no unused imports
   - too opinionated
   - poor std math lib
   - weird mascot (gopher)
-+ http://nomad.so/2015/03/why-gos-design-is-a-disservice-to-intelligent-programmers/ (Gary Willoughby, 2015)
-  - too simple / lack of syntactic sugar
-  - no generics
-  - bad dependency management
-  - stuck in 70's
++ http://spaces-vs-tabs.com/4-weeks-of-golang-the-good-the-bad-and-the-ugly/ (Freddy Rangel, 2015)
+  - not-so-obvious slices behaviour
+  - error handling
+  - hard to test, hard to mock
 + http://tmikov.blogspot.com/2015/02/you-dont-like-googles-go-because-you.html (Tzvetan Mikov, 2015)
   - designed for stupid people
   - too verbose
@@ -144,6 +146,11 @@ You're writing some code. And suddenly you understand you need something that la
   - compilation rules are too confining
   - designed for stupid people
   - package mechanism is broken
++ http://nomad.so/2015/03/why-gos-design-is-a-disservice-to-intelligent-programmers/ (Gary Willoughby, 2015)
+  - too simple / lack of syntactic sugar
+  - no generics
+  - bad dependency management
+  - stuck in 70's
 + http://blog.goodstuff.im/golang (David Pollak, 2015)
   - no immutables
   - too simple / lack of syntactic sugar
@@ -154,25 +161,11 @@ You're writing some code. And suddenly you understand you need something that la
   - no generics
   - upper-case/lower-case scoping is bad
   - no `map`/`reduce`/`filter`
-+ http://byrd.im/go-is-poor/ (Ian Byrd, 2015)
-  - not-so-obvious slices behaviour
-  - nil interfaces are not entirely nil
-  - unexpected variable shadowing
-  - no first-class support of interfaces
-  - questionable compiler rigidity
-  - go generate is a quirk
 + https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e#.62yek82xg (Mike Hearn, 2016)
   - misleading marketing around garbage collector
   - garbage collector is nothing new; concurrent mark/sweep from the '70s
   - garbage collector requires implicit (hidden) tradeoffs
   - garbage collector optimized for pause times at the cost of other desirable gc features
-+ http://www.jtolds.com/writing/2016/03/go-channels-are-bad-and-you-should-feel-bad/ (JT Olds, 2016)
-  - channels are slow
-  - channel API is inconsistent
-+ https://medium.com/@rgausnet/3-reasons-why-go-isnt-the-perfect-language-yet-25e0da5ec04c (Ryan Gaus, 2016)
-  - not stable
-  - no `map`/`reduce`/`filter`
-  - bad dependency management
 + https://www.teamten.com/lawrence/writings/why-i-dont-like-go.html (Lawrence Kesteloot, 2016)
   - upper-case/lower-case scoping is bad
   - case defined exports is bad
@@ -184,23 +177,35 @@ You're writing some code. And suddenly you understand you need something that la
   - no versioning model
   - import-based vendoring is terrible
   - no generics
-+ https://awalterschulze.github.io/blog/post/sum-types-over-multiple-returns/ (Walter Schulze, 2017)
-  - no sum types
-  - no algebraic data types
-  - multiple return parameters are overrated
++ http://www.jtolds.com/writing/2016/03/go-channels-are-bad-and-you-should-feel-bad/ (JT Olds, 2016)
+  - channels are slow
+  - channel API is inconsistent
++ https://medium.com/@rgausnet/3-reasons-why-go-isnt-the-perfect-language-yet-25e0da5ec04c (Ryan Gaus, 2016)
+  - not stable
+  - no `map`/`reduce`/`filter`
+  - bad dependency management
 + http://sitr.us/2017/02/21/changes-i-would-make-to-go.html (Jesse Hallett, 2017)
   - no non-nullable types
   - error handling
   - no generics
   - no tagged unions
   - no first-class tuple
   - concurrency and parallelism are mixed
++ https://awalterschulze.github.io/blog/post/sum-types-over-multiple-returns/ (Walter Schulze, 2017)
+  - no sum types
+  - no algebraic data types
+  - multiple return parameters are overrated
 + https://grimoire.ca/dev/go (Owen Jacobson, 2018)
   - hostile to developer ergonomics
   - too opinionated
   - package mechanism is broken
   - GOPATH is a mess
   - error handling
++ https://www.pixelstech.net/article/1541901293-Advantages-and-disadvantages-of-GoLang (Pi Ke, 2018)
+  - lack of frameworks
+  - error handling
+  - package management
+  - generics support is missing
 
 
 # Reverse complaints index
@@ -266,12 +271,15 @@ It's a reverse complaints index, generated by https://github.com/ksimka/go-is-no
   - http://blog.goodstuff.im/golang (David Pollak 2015)
   - http://sitr.us/2017/02/21/changes-i-would-make-to-go.html (Jesse Hallett 2017)
   - https://grimoire.ca/dev/go (Owen Jacobson 2018)
+  - https://www.pixelstech.net/article/1541901293-Advantages-and-disadvantages-of-GoLang (Pi Ke 2018)
 + garbage collector is nothing new; concurrent mark/sweep from the '70s
   - https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e#.62yek82xg (Mike Hearn 2016)
 + garbage collector optimized for pause times at the cost of other desirable gc features
   - https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e#.62yek82xg (Mike Hearn 2016)
 + garbage collector requires implicit (hidden) tradeoffs
   - https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e#.62yek82xg (Mike Hearn 2016)
++ generics support is missing
+  - https://www.pixelstech.net/article/1541901293-Advantages-and-disadvantages-of-GoLang (Pi Ke 2018)
 + go generate is a quirk
   - http://byrd.im/go-is-poor/ (Ian Byrd 2015)
 + goroutine is not original and revolutionary
@@ -300,6 +308,8 @@ It's a reverse complaints index, generated by https://github.com/ksimka/go-is-no
   - http://www.darkcoding.net/software/go-lang-after-four-months/ (Graham King 2012)
 + lack of basic data structures
   - http://blog.mattbasta.com/things_that_make_me_sad_in_go.html (Matt Basta 2014)
++ lack of frameworks
+  - https://www.pixelstech.net/article/1541901293-Advantages-and-disadvantages-of-GoLang (Pi Ke 2018)
 + misleading marketing around garbage collector
   - https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e#.62yek82xg (Mike Hearn 2016)
 + multiple return parameters are overrated
@@ -348,8 +358,8 @@ It's a reverse complaints index, generated by https://github.com/ksimka/go-is-no
   - http://how-bazaar.blogspot.ru/2013/04/the-go-language-my-thoughts.html (Tim Penhey 2013)
   - https://rule1.quora.com/Golang-Not-yet (Jordan Zimmerman 2014)
   - http://yager.io/programming/go.html (Will Yager 2014)
-  - https://www.upguard.com/blog/our-experience-with-golang (Mark Sheahan 2014)
   - http://www.yinwang.org/blog-cn/2014/04/18/golang (Wang Yin 2014)
+  - https://www.upguard.com/blog/our-experience-with-golang (Mark Sheahan 2014)
   - https://kaushalsubedi.com/blog/2015/11/10/golang-sucks-heres-why/ (Kaushal Subedi 2015)
   - http://nomad.so/2015/03/why-gos-design-is-a-disservice-to-intelligent-programmers/ (Gary Willoughby 2015)
   - http://blog.goodstuff.im/golang (David Pollak 2015)
@@ -393,8 +403,10 @@ It's a reverse complaints index, generated by https://github.com/ksimka/go-is-no
   - https://medium.com/@rgausnet/3-reasons-why-go-isnt-the-perfect-language-yet-25e0da5ec04c (Ryan Gaus 2016)
 + not-so-obvious slices behaviour
   - https://www.upguard.com/blog/our-experience-with-golang (Mark Sheahan 2014)
-  - http://spaces-vs-tabs.com/4-weeks-of-golang-the-good-the-bad-and-the-ugly/ (Freddy Rangel 2015)
   - http://byrd.im/go-is-poor/ (Ian Byrd 2015)
+  - http://spaces-vs-tabs.com/4-weeks-of-golang-the-good-the-bad-and-the-ugly/ (Freddy Rangel 2015)
++ package management
+  - https://www.pixelstech.net/article/1541901293-Advantages-and-disadvantages-of-GoLang (Pi Ke 2018)
 + package mechanism is broken
   - http://valuedrivenit.blogspot.ru/2015/12/to-go-language-is-mess.html (Cliff Berg 2015)
   - https://grimoire.ca/dev/go (Owen Jacobson 2018)

entries.json

@@ -326,4 +326,14 @@
         "GOPATH is a mess",
         "error handling"
     ]
+},{
+    "URL": "https://www.pixelstech.net/article/1541901293-Advantages-and-disadvantages-of-GoLang",
+    "Author": "Pi Ke",
+    "Year": 2018,
+    "Complaints": [
+        "lack of frameworks",
+        "error handling",
+		"package management",
+		"generics support is missing"
+    ]
 }]