Welcome to the Lounge

Rage wrote:

I have never understood how you can program anything by placing white and black stones on a board...

raddevus wrote:

makes it very easy to build to a native Exe --

GOOS=windows GOARCH=amd64 go build hello.go

GOOS=linux GOARCH=arm go build hello.go

1. Error handling. I just don't like the way they do it, with a pair of error/return value. I prefer the Rust way, having a tagged union that is either error code or return value.
2. Type system. Not just a lack of generics - I like the flexibility that sum types give you.

Stuart Dootson wrote:

I'm not so keen on Go. Mainly because of

Quote:

This article also resonates with me...

Quote:

I, on the other hand, would see the only sensible thing as highlighting an error condition that needs to be handled, probably at a higher level of abstraction in the program.

func main() 
{
	sum := 0
	for i := 0; i < 10; i++ 	
	{
		sum += i
	}
	fmt.Println(sum)
}

den2k88 wrote:

In 2020 a language that forces a particular style of indentation should be hanged, burned, shredded and used as cat litter.

den2k88 wrote:

Also, apparently there is no while, only for.

Quote:

That's why Go even with all Mozilla's money still "nothing", but a toy for students.

C: 0.73 new features per year, measured by the number of bullet points in the C11 article on Wikipedia which summarizes the changes from C99, adjusted to account for the fact that C18 introduced no new features.

Go: 2 new features per year, measured by the number of new features listed on the Wikipedia summary of new Go versions.

C++: 11.3 new features per year, measured by the number of bullet points in the C++17 article which summarizes the changes from C++14.

Rust: 15 new features per year, measured by the number of headers in the release notes of major Rust versions over the past year, minus things like linters.