Not sure I like the generics proposals, they seem really complex, writing pseudo code which is never going to be executed to cover all the usage of the variables within seems odd. Why can't they use some extension of interfaces instead?
The error changes will be welcome though - no more if err != nil {return err} which you do see a lot in go code.
I mostly agree with this post, postgresql > time series databases for the reasons given - people know SQL, performance is good enough for most workloads, and it is rock solid.
Anyone using go for machine learning? I'd like to get into it, is this a good introductory guide for those who don't know anything about machine learning?
There are actual use-cases for generics in go, and mixing the debate up with just bypassing the type system with empty interfaces is not very helpful. Enough newcomers get seduced by empty interface as it is.
This should really be called config, it looks like it is for reading config files, not environment variables. If it's called env it should probably have some ability to override with env variables if they are defined for a given key.
Have to agree about the lack of inheritance - it's the best thing about Go is avoiding all that abstraction that people pile on top of simple concepts, leading to logic being spread around lots of different files. You can go a long way with just structs and functions.
Not sure I like the generics proposals, they seem really complex, writing pseudo code which is never going to be executed to cover all the usage of the variables within seems odd. Why can't they use some extension of interfaces instead?
I mostly agree with this post, postgresql > time series databases for the reasons given - people know SQL, performance is good enough for most workloads, and it is rock solid.
Anyone using go for machine learning? I'd like to get into it, is this a good introductory guide for those who don't know anything about machine learning?
Hope no-one takes this seriously.
This should really be called config, it looks like it is for reading config files, not environment variables. If it's called env it should probably have some ability to override with env variables if they are defined for a given key.
What legal issues are there that restrict recruiting outside the US?
Have to agree about the lack of inheritance - it's the best thing about Go is avoiding all that abstraction that people pile on top of simple concepts, leading to logic being spread around lots of different files. You can go a long way with just structs and functions.
Looks like a file upload service. Link didn't work for me the first time. What are you using this for?