Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

The Go programming language

Name: Anonymous 2011-01-22 23:02

So I played a little bit with http://golang.org and I must say I like it. So please tell me why it is shit because I know /prog/ knows better.

Name: Anonymous 2011-01-23 13:05

YHBT

Name: Anonymous 2011-01-23 13:05

YHBT

Name: Anonymous 2011-01-23 13:06

YHBT

Name: Anonymous 2011-01-23 13:53

>>12
THE FORCED CAPITALIZATION OF EXPORTED SYMBOLS.? Sounds retarded: I'm imagining all sorts of problems between case sensitive and case insensitive platforms.

Name: Anonymous 2011-01-23 13:57

>>44
It is retarded.
When you want to use some module, you'd need to do
Func(ExportedSymbol, my_local_symbol(Exported));
my_function(YourValue);
MyExported(YourExported, my_local);


It's multicase crapfest.

Name: Anonymous 2011-01-23 14:26

>>44
What ever shall we do on systems where bit 5 is masked on all the registers? It was that or some comment about doing all symbol lookups using the filesystem.

>>45
It's not that bad in my opinion, but I'd rather use a qualifier though, or even take something from C++ and use a section. Perl's solution is nice too, declarations start with short (usually 2 or 3) letter keywords.

They went too far on the "no qualifiers" thing but I guess they blamed C for the Java and C# mess.

Name: Anonymous 2011-01-23 15:01

>>46
They could make something like CL or Racket or some other Scheme implementation here and make a fucking sane package/module system. In fact, ``Go'' takes nothing from Lisp, whereas almost all the programming languages out there are taking ideas from it, even Sepplecocks with lambdas.

Name: Anonymous 2011-01-23 16:25

THE GOLAN HEIGHTS PROGRAMMING LANGUAGE

Name: Anonymous 2011-01-23 18:55

>>44
Protip: The Go compilers are case-sensitive on all platforms. Just like C compilers.

Name: Anonymous 2011-01-23 19:18

>>49
One word: The forced capitalization of exported symbols.

Name: Anonymous 2011-01-23 20:29

>>1
I'll probably stick with Haskell as my "heavy lifting" language (and C for system software/trivial things that need to go fast).

Still, I don't see any reason to despise Go outright, and if it becomes popular it might be more tolerable than the current host of popular mid-level languages. The loss of low-level control will be intolerable for some highly skilled C/Assembly programmers, but in general it's better to not give the retards too much to shoot themselves in the foot with.

Overall, I'd take it over Java for a mediocre general-purpose language, but nothing more. The low-level guys will still have C, and the functional nerds still have Haskell/Scheme.

Name: Anonymous 2011-01-23 21:11

I don't think it brings much new to the table.
It has light-weight threads and channels, which isn't really my preferred concurrency paradigm. And it compiles faster than C++, which is almost a tautology.
I think it might be geared toward servers/services, but then why not use Erlang?

Name: Anonymous 2011-01-23 22:01

>>52
Erlang is RUBY AS FUCK

Name: Anonymous 2011-01-23 23:50

>>51
Still, I don't see any reason to despise Go outright
It doesn't actually solve a problem. Soon you may be able to use it for Android, which would be preferable to Java. Then again, soon you may be able to use CLR/whatever for Android, which would be preferable to Go, since you could pick your poison.

There's still the matter of performance, but Go has yet to beat the least-awful JVMs--I would think that includes Android's. ARM chips make this situation worse; many of them will run bytecode directly. It's not quite a JVM-on-chip, but Go already compiles to native code so there's no room to accelerate it in the CPU.

Name: Anonymous 2011-01-24 1:14

Go is great.

A statically-typed language that isn't either verbose or frustrating.
Good concurrency support.
Sane, minimal syntax.
Simple type system.
Consistent style.
Control over allocations, lets you write efficient code.

I use it for everything now.

Name: Anonymous 2011-01-24 1:39

Go: no exceptions.
That's so 1960.

Name: Anonymous 2011-01-24 2:54

>>53
thanks, you make me want to try it, now.

Name: Anonymous 2011-01-24 10:22

>>55
ONE WORD: import { "fmt" "os" }; func main () { fmt.Printf("THE FORCED CAPITALIZATION OF EXPORTED SYMBOLS"); fmt.Printf("THE FORCED STRINGIZATION OF IMPORTED MODULES"); os.Stdout.WriteString("THREAD OVER"); }

Name: Anonymous 2011-01-24 10:39

>>58
That's the only problem you see with it?

Name: Anonymous 2011-01-24 11:27

>>59
Now you have |ℝ| problems.

Name: Anonymous 2011-01-24 13:53

>>59
Of course not, but these are the more stupid ones, therefore memeable.

Name: Anonymous 2011-01-26 5:44

the forced "stringification" of the forced fmt.fumpt of the forced Capitalization of Printf of the forced meme lol xD of the forced removal of semicolons of the gofmt of the forced THREAD OVER

Name: Anonymous 2011-01-26 6:07

lol xD

Just go away.

Name: Anonymous 2011-01-26 6:13

26 get

Name: Anonymous 2011-01-26 8:18

Ascii 'A' GET

Name: Anonymous 2011-01-26 9:45

case 'B': GET();

Name: Anonymous 2011-01-26 9:54

>>66
I lol'd

Name: Anonymous 2011-01-26 10:06

Name: Anonymous 2011-01-26 11:11

>>68
Optimize yo'ure quotes!

Name: Anonymous 2011-01-26 11:11

>>68
nice.

Name: Anonymous 2011-01-26 11:12

CHECK DEM DUBS! -->

Name: Anonymous 2011-01-26 11:21

^
FAGGOT

Name: Anonymous 2011-01-26 11:24

>>69

Don't you know that -funroll-quotes is considered an optimization?

Name: Anonymous 2011-01-26 11:48

-funroll-quotes considered optimised!

Name: Anonymous 2011-02-04 18:23


Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List