thr23d93 · HackerTrans

7 ปีที่แล้วdiscuss

I find the logic the article uses to make its point a bit handwavy, or you could even say "wrong". If the language specification required the first line to start FIRST and then every subsequent line in each file start with AND THEN, so that this:

   package main
   
   import (
    "fmt"
    "net/http"
   )
   
   func main() {
    http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
     fmt.Fprintf(w, "Hello, you've requested: %s\n", r.URL.Path)
    })
   
    http.ListenAndServe(":80", nil)
   }

becomes

   FIRST package main
   AND THEN 
   AND THEN import (
   AND THEN  "fmt"
   AND THEN  "net/http"
   AND THEN )
   AND THEN 
   AND THEN func main() {
   AND THEN  http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
   AND THEN   fmt.Fprintf(w, "Hello, you've requested: %s\n", r.URL.Path)
   AND THEN  })
   AND THEN 
   AND THEN  http.ListenAndServe(":80", nil)
   AND THEN }

there is a very good chance it would not make it into "the biggest challenge you personally face using Go today." Because it's not a challenge. It's stupid, but not a challenge.

So just because the verbose incantation

   if err != nil {
       return err
   }

or other issues, could be thought of as very similar to AND THEN, it doesn't mean that this is the biggest challenge someone personally faces. it could be stupid, but you get used to it.

so it depends on the wording of the question. Basically the real question isn't how big of a pain point it is. It's how much it could be fixed.

my specification for the formatting of the language would be hugely improved by removing the AND THEN line from each line of the code. It's kind of ugly.

comments