How can a programming language be so based ?

How can a programming language be so based ?

>fully opensource
>made by Pike and the gang
>mogs java in servers due to first class concurrency support
>mogs other niche languages with superb package management and a ton of libraries
>supports incorporating C code, allows nearly seamless C code integration in to the codebase

Attached: Go_gopher_mascot_bw.png (1200x1200, 141.31K)

Other urls found in this thread:

tip.golang.org/doc/go1.18
github.com/dariubs/GoBooks
twitter.com/SFWRedditGifs

WHERE THE FUCK ARE MY GENERICS, ROB?

tip.golang.org/doc/go1.18

>Go 1.18 is not yet released.
ROB, WHERE THE FUCK ARE THEY

>not lisp
DOA

>lisp
DEAD IN THE PRESENT

somewhere feb, i believe
obsessing over lisp is midwit thing, go as impartive language with *some* oop and fp elements is much more flexible and expressive
t. read sicp

Beta was released almost 2 months ago

What's your personal usecase?

infrastructure for online banking

I mean, INFRASTRUCTURE FOR ONLINE BANKING

>*some* oop
FAKE NEWS, Go team would never allow such bloat into the language
>fp elements
Other than first class functions, there is nothing

Wouldn't you want things to be more heavily typed rather than dealing with generics?

kek

Dumb rat poster.

Question doesn't make sense IMO because you're only 'supposed' to use generics in a situation where any type already makes sense. I specifically want to use them in my data layer so I don't need to write a get,update,delete,etc method for every single struct that maps to a SQL table, which is what I'm having to do now. Any type makes sense for that. They all have a Table_name and Id attribute that can be referenced in the prepared statement that runs. A lot of array and map operations can also be abstracted out into functions which will clean things up but that's just gravy. Maybe I'm not understanding your question.

Generic containers and algorithms

Can't you just use the beta releases to prototype it now?

interfaces are oop, if you think objects are oop, you're wrong
for FP, you need
* recursion, which is de facto present in pretty much every modern language because of how it is essential for certain algorithms
* first class functions
lazy eval, lambda, macro processing is not essential
so i'm right

clearly he needs concepts.

> go build

Attached: F4927196-90F1-4C8C-8796-84227385E98F.jpg (1920x1200, 183.39K)

github.com/dariubs/GoBooks
now tell me Any Forums which books should i read out of these

You also need immutability.