Re: [go-nuts] Re: Looking Backend Dev Learning Resources

2022-12-05 Thread Christoph Berger
> that would mean the progress made did not invalidate any of effective Go (which seems not possible given the addition of generics) Adding new features makes Effective Go *incomplete* but not *invalid*. There is separate documentation available for Generics and other new features. Go documenta

Re: [go-nuts] Re: Looking Backend Dev Learning Resources

2022-12-05 Thread 'Dan Kortschak' via golang-nuts
On Mon, 2022-12-05 at 14:54 -0600, Robert Engels wrote: > Can you elaborate on that reference? At first review, it means you > are putting in lots of effort making lots of progress (anti red > queen) but that would mean the progress made did not invalidate any > of effective Go (which seems not pos

Re: [go-nuts] Re: Looking Backend Dev Learning Resources

2022-12-05 Thread Robert Engels
Can you elaborate on that reference? At first review, it means you are putting in lots of effort making lots of progress (anti red queen) but that would mean the progress made did not invalidate any of effective Go (which seems not possible given the addition of generics). I’m doubting you impl

Re: [go-nuts] Re: Looking Backend Dev Learning Resources

2022-12-05 Thread 'Dan Kortschak' via golang-nuts
On Mon, 2022-12-05 at 09:27 -0800, Tsvetomir Lazarov wrote: > How relevant is Effective Go actually, given the January 2022 update > that this document has not been updated significantly since 2009? Still relevant. This is one of the virtues of having a language that is not built on the Red Queen