A Farewell to Go
81–85 of 85 posts
Re: A Farewell to Go
#82Go is a lowest common denominator language designed by a large company to make programmers expendable. It's ironic though because we all know how that worked out after Sun tried it with Java and what we now have some 20+ years later.
a tremendous number of production systems written in Java, being used by a tremendous number of people, and making a lot of money for corporations?
That's the goal of Go. It's not for research, it's not for discovery: it's for dominating the marketplace. If Go replicates Java's fate, it will have succeeded at its goals, because it's goals are to be used in production systems run by corporations.
Re: A Farewell to Go
#831. Strict Enforcement of the Google Code Guidelines People who are undisciplined typically don't like discipline when they first encounter it. This doesn't restrict "Coding style" like the author suggests. Coding style and code format shouldn't be conflated. 2. Broken Package Management It's not broken; it's intentionally limited. A "vendor" directory is natively supported by Go to account for this; use Glide or simi…
Go binaries are small and don't do much initialization work but they don't run especially quickly, mostly due to GC and value->interface conversion and dynamic dispatch.
Thank you for the reply. Where can I learn more about that?
Re: A Farewell to Go
#84According to my opinion, a programming language should let a developer use his or her style. gofmt is the best part of Go. Everybody's code looks the same. Broken Package Management This is a solved problem with dep. Switch your Go projects to dep today. In the documentation there is no mentioning of those missing things, you expect from a modern HTTP library. Go's philosophy is "less is more." This is the journey of…
That is not a feature. Consistency and readability are not the same thing - it's a lazy substitute for readability, at best.
Re: A Farewell to Go
#85According to my opinion, a programming language should let a developer use his or her style. gofmt is the best part of Go. Everybody's code looks the same. Broken Package Management This is a solved problem with dep. Switch your Go projects to dep today. In the documentation there is no mentioning of those missing things, you expect from a modern HTTP library. Go's philosophy is "less is more." This is the journey of…
From a quick glance, `dep` seems to still be using source/repository URLs as dependency identifiers, which is a terrible idea. Other languages use a registry for a reason.