Go

Firedrake969

Does anybody use Go? I have to learn it since I bought a Go t-shirt at Google

VoltageGames

… would've been nice if you told us what Go was.
https://code.google.com/p/go/ <– did you mean this?

Last edited by VoltageGames (Nov. 26, 2015 04:17:31)

Firedrake969

Yeah, golang

Firedrake969

Bump…

Anybody?

MegaApuTurkUltra

Nope

It seems nice though

Firedrake969

Helped me understand pointers, but structs and interfaces and function syntax take some getting used to

DrKat123

Firedrake969 wrote:
Does anybody use Go? I have to learn it since I bought a Go t-shirt at Google

duuude you don't have to do that

DrKat123

Ok try this

import "fmt"
func main() {
	fmt.Println("Hello, World")
	fmt.Println("I'm a n00b ATer")
}

I dare you ATers print this

Last edited by DrKat123 (Dec. 14, 2015 06:52:06)

MegaApuTurkUltra

@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.

Last edited by MegaApuTurkUltra (Dec. 14, 2015 13:49:26)

comp09

MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.

…which is what good programming practices are for…

Jonathan50

MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.

pls no

just debug it and write good code

comp09 wrote:
…which is what good programming practices are for…

^^^

MegaApuTurkUltra

Jonathan50 wrote:
MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.
pls no
just debug it and write good code
comp09 wrote:
…which is what good programming practices are for…
^^^

People are imperfect. If we could all write 100% good code then C++ would be great. The problem is that even though you try, you still create random bugs. A bit of safety greatly reduces the chance that a bug you introduce is going to be completely untraceable.

Jonathan50

MegaApuTurkUltra wrote:
Jonathan50 wrote:
MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.
pls no
just debug it and write good code
comp09 wrote:
…which is what good programming practices are for…
^^^
People are imperfect. If we could all write 100% good code then C++ would be great. The problem is that even though you try, you still create random bugs. A bit of safety greatly reduces the chance that a bug you introduce is going to be completely untraceable.

but what's wrong with that is then you will still use bad practices and you'll trip on it later, even with Go.

MegaApuTurkUltra

Jonathan50 wrote:
MegaApuTurkUltra wrote:
Jonathan50 wrote:
MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.
pls no
just debug it and write good code
comp09 wrote:
…which is what good programming practices are for…
^^^
People are imperfect. If we could all write 100% good code then C++ would be great. The problem is that even though you try, you still create random bugs. A bit of safety greatly reduces the chance that a bug you introduce is going to be completely untraceable.
but what's wrong with that is then you will still use bad practices and you'll trip on it later, even with Go.

Well yes, don't write serious code until you know how to use best practices.
What I'm saying is best practices can't possibly protect you from everything.

Firedrake969

Jonathan50 wrote:
MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.
pls no
just debug it and write good code
comp09 wrote:
…which is what good programming practices are for…
^^^

So then write good Go code. Use whatever tool you want as long as it meets your needs.

How to complain about Go:
https://medium.com/@divan/how-to-complain-about-go-349013e06d24#.3i3d89xrj

Last edited by Firedrake969 (Dec. 15, 2015 00:04:40)

Jonathan50

Firedrake969 wrote:
Jonathan50 wrote:
MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.
pls no
just debug it and write good code
comp09 wrote:
…which is what good programming practices are for…
^^^
So then write good Go code. Use whatever tool you want as long as it meets your needs.

I know that, I'm simply telling MATU that using Go isn't an excuse for writing bad code…

comp09

Jonathan50 wrote:
Firedrake969 wrote:
Jonathan50 wrote:
MegaApuTurkUltra wrote:
@ChocolatePi's comment which I'll assume was meant to GO here pun intended
https://scratch.mit.edu/discuss/post/1666130/

My response: Go is C++ for those who would rather not spend hours figuring out what the heck is causing a segfault 0.01% of the time they run their code.
pls no
just debug it and write good code
comp09 wrote:
…which is what good programming practices are for…
^^^
So then write good Go code. Use whatever tool you want as long as it meets your needs.
I know that, I'm simply telling MATU that using Go isn't an excuse for writing bad code…

I hear that Go is (annoyingly) designed in such a way to force Google engineers to code in a certain way.

Firedrake969

Where do you see that?

gdpr533f604550b2f20900645890

Go
…
wait for it…
…
ogle

There is also something called “Google Apps Script.” Does it have any relation to Go?

Jonathan50

Chibi-Matoran wrote:
Go
…
wait for it…
…
ogle

There is also something called “Google Apps Script.” Does it have any relation to Go?

No
Google Apps Script is something that (IMO) never should've happened.
It's JavaScript but supposed to be for Google Drive/Docs.

Last edited by Jonathan50 (Dec. 15, 2015 00:13:11)

Discuss Scratch

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

Go

About

Community

Resources

Legal

Scratch Family