one2three4

You do that anyway as per Conway's law.

Honestly the only real argument I've heard for Golang is that it is "coming from Google so it must be good". Every time I've tried to write in this language it feels like I'm hitting my head with a hammer.

Google might have very smart and knowledgeable people in it but this language is like a bad overhyped C. See next code that all it is doing is parsing a CSV line:

func NewPoint(line string) *Point {

tokens := strings.Split(line, ",")

if len(tokens) != 4 {

  return nil

 }

 var err error

 p := new(Point)
 

// why cannot I declare and assign err in one go??

p.id_ride, err = strconv.Atoi(tokens[0])

if err != nil {

  return nil

 }

 p.lat, err = strconv.ParseFloat(tokens[1], 32)

 if err != nil {

  return nil

 }

 p.ts, err = strconv.ParseInt(tokens[2], 10, 64)

 if err != nil {

  return nil

 }

 return p

}

most of the code has nothing to do with its functionality - it's just error handling that is plain hideous to write and read. Not to mention all the clutter to just convert an integer and a float.

And let's just not go into deeper aspects such as the structs that double as classes and has everyone creating his own style of SOLID and DPs. Or the inconsistent syntax which sometimes looks like traditional OO and othertimes like plain C further confusing users.

I find it very hard to believe that this language would have caught on if it weren't for Google pushing for it so aggressively. And I find it so disheartening to realise that after all these years developer productivity and happiness is merely an afterthought for language designers and that marketing and hype are the main drivers.

And yes I know the saying "there are languages people complain about and languages that people do not use". I find it worthy of high school gotcha sayings to which I reply that language designers of the majority of programming languages have no clue about how to make a language nice to its users. It's as they know how to design a internal combustion engine and then they put a chair and 4 wheels on it and they dismiss complaints about how unreasonably difficult and miserable the driver experience is.

That's a great and pragmatic suggestion.

Pragmatic as in these are not generic solutions/patterns but actual working architectures.

Thanks.

I'm curious. Was Linkedin always so bad at securing its (our) data or things have gone downhill ever since the acquisition?

It is becoming a regular thing, almost part of the news cycle. "In other news, yesterday was the biannual data leak from Linkedin".

It is outrageous.

Is there any easy way to guard against this without putting everything in a VPC?

> miss languages with better type checking. What about python type hints?