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.

One afternoon? Hm, it depends on the paper really and how close it is to your daily work.

2 pages in FoundationDB paper (https://www.foundationdb.org/files/fdb-paper.pdf) I knew I was looking at one month's reading material if I really was to grasp everything. It'd be much easier if I worked with DBs and Distributed daily but I don't.

But, yes, I see your point.

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?

>> In its newest release, CouchDB [2] (arguably the firstNoSQL system) is being re-built as a layer on top of FoundationDB.

That is impressive. Like a framework for implementing noSQL DBs.

To keep your identity small is probably akin to becoming a small Buddha.

Identity is even a dominant political trend in itself. "Identity politics".

I agree with the premise of the post. I just cannot see how it can be done. I think it's better to learn to accept differences gracefully rather than minimizing the identity surface. It's also my way to test people and communities. Try to disagree on something they consider basic. They way they'll treat you shows who they really are.

Your commend reminded me of this presentation https://www.youtube.com/watch?v=PQccNdwm8Tw

Ehm, I need to work to pay bills etc.

Thanks for the reply. This helps me a lot. I'll try to negotiate these terms.

I can assure you that on the personal income tax front and much more so at the indirect tax of cost of living the Irish govt is doing just fine thank you.

I think it's similar to all the super-liberal OS licenses that permit any usage of OS SW without warranting any kind of compensation for the original devs. Licenses that the devs themselves are putting in their OS SW. Why they do so I honestly don't know.

Which leads to a number of weird situations like maintainers begging for compensation from simple users while behemoths make tons of money out of their SW or pretty basic SW being undermaintained (I vaguely remember a case pertaining to a security related library a few years ago where everyone was waiting on an overwhelmed and unpaid maintainer to provide a security fix).

Dunno. Some things just don't make sense to me. FWIW as far as my projects go I license under GPL. If it's free for you let it be free for all. I'd hate to be in the shoes of Redis contributors. To me, if your work is being used you must be compensated. Anything else is just plain wrong.

>> Pynguin can cause serious harm to your computer, for example, wipe your entire hard disk! We recommend running Pynguin in an isolated environment, for example, a Docker container, to minimise the risk of damaging your system.

That sounds ominous.

Why do they execute the generated tests though? I mean I'd expect this to go only as far as generating the tests. Also that means that at least someone needs to review the tests.