Discuss Scratch

Firedrake969
Scratcher
1000+ posts

Go

Well, yeah, it was made by Google.

(GAS isn't related though)
ChocolatePi
Scratcher
1000+ posts

Go

Firedrake969 wrote:

Well, yeah, it was made by Google.

(GAS isn't related though)
*snort*
Firedrake969
Scratcher
1000+ posts

Go

Regarding which line?

Lied, you can use Go in GAS. Oops.

Last edited by Firedrake969 (Dec. 15, 2015 00:19:12)

Jonathan50
Scratcher
1000+ posts

Go

comp09 wrote:

I hear that Go is (annoyingly) designed in such a way to force Google engineers to code in a certain way.
So basically a language designed around Google's Style Guides?
Firedrake969
Scratcher
1000+ posts

Go

Doesn't look like it. Languages are definitely independent from programming styles (except Python) xD

Last edited by Firedrake969 (Dec. 15, 2015 00:27:52)

Jonathan50
Scratcher
1000+ posts

Go

Firedrake969 wrote:

Doesn't look like it. Languages are definitely independent from programming styles (except Python) xD
No. Just because some languages are doesn't mean that it's impossible to design a programming language that isn't.
And haven't you wondered why Google doesn't have a Go style guide?
btw Python is
Firedrake969
Scratcher
1000+ posts

Go

“No” what? lol

So many pronoun references to seemingly absent nouns…

Google doesn't have a Go style guide because the Go style guide is here.
Jonathan50
Scratcher
1000+ posts

Go

Firedrake969 wrote:

“No” what? lol

So many pronoun references to seemingly absent nouns…

Google doesn't have a Go style guide because the Go style guide is here.
That's not exactly a style guide.
Go forces certain styles, eg:
One consequence of the semicolon insertion rules is that you cannot put the opening brace of a control structure (if, for, switch, or select) on the next line. If you do, a semicolon will be inserted before the brace, which could cause unwanted effects. Write them like this
if i < f() {
    g()
}
not like this
if i < f()  // wrong!
{           // wrong!
    g()
}
not that Go is bad, I haven't tried it…
Firedrake969
Scratcher
1000+ posts

Go

Thanks for your insights on something you haven't even tried, then

also check out gofmt
MegaApuTurkUltra
Scratcher
1000+ posts

Go

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…
Please read what I wrote again thanks
Jonathan50_test
Scratcher
10 posts

Go

MegaApuTurkUltra wrote:

Jonathan50 wrote:

I know that, I'm simply telling MATU that using Go isn't an excuse for writing bad code…
Please read what I wrote again thanks
I saw that, I was just explaining to @Firedrake969
DifferentDance8
Scratcher
1000+ posts

Go

this article explains the different reasons why Go isn't a great language
ajskateboarder
Scratcher
1000+ posts

Go

DifferentDance8 wrote:

this article explains the different reasons why Go isn't a great language
Nice bump

It's a good language for the most part. I just don't like the way you handle exceptions:
res, err := RunFunction()
if err != nil {
    panic(err)
}
It lets you handle exceptions well, but it shouldn't make you always handle them
bigspeedfpv
Scratcher
500+ posts

Go

DifferentDance8 wrote:

this article explains the different reasons why Go isn't a great language
holy mother of necroposts.
have you ever used go?
i'm assuming not
did you read the whole article?
also assuming not
the whole thing is just complaining that there's not much abstraction in the file library (good, the language was designed to be minimal)
the last part of the article is complaining that packages depend on more packages. interesting, seeing as how they constantly compare go to rust, whose compile time grows exponentially with the number of packages added lol
this article basically says “go is supposed to be simple but my code is long why
…except they don't realize a “simple” language doesn't mean short code, it means a language that does everything the same way… which is what the article shows
i'd be interested to hear *your* thoughts specifically on why go is bad
mybearworld
Scratcher
1000+ posts

Go

package main
import (
  "fmt"
  "os"
  "scratch/forums"
)
func main() {
  err := bump()
  if err != nil {
    fmt.Fprintln(os.Stderr, err)
    os.Exit(1)
  }
}
func bump() error {
  topic, err := forums.GetTopic(169982)
  if err != nil {
    return err
  }
  err = topic.Bump()
  if err != nil {
    return err
  }
}

Last edited by mybearworld (Sept. 30, 2024 05:16:12)

Jonathan50
Scratcher
1000+ posts

Go

mybearworld wrote:

...
Man, forcing me to read my excessively attituded posts from 9 years ago

On a serious note, I'd be interested if Go is still as relevant now, or perhaps moreso

Last edited by Jonathan50 (Sept. 30, 2024 07:52:22)

Powered by DjangoBB