6 ms·
I taught Go to 3 fresh new computer engineers, where they had no real-life programming experience. It was different to them: channels, no traditional oop and no
by CSDude 10y ago
I taught Go to 3 fresh new computer engineers, where they had no real-life programming experience. It was different to them: channels, no traditional oop and no generics, but they picked it up very quickly, and with them we were able to produce a very large application. We tried to keep things as much as simple as possible, avoided coding magic as much as possible and using Go was a nice experience for us. Not saying this proves anything, it is just a real-life example from us. Most of the times people do not need all the interesting things you think you should have in a language, and may like their "opinoniated" way of approaching to problems.
- EpicEng 10y agoJust curious... If they had no prior programming experience, why was go 'different'? Different compared to what?
- znpy 10y ago> Just curious... If they had no prior programming experience, why was go 'different'? Different compared to what? Probably compared to what they were shown in university/bootcamp/whatever. 'no programming experience' could esily mean 'no professional programming experience' which is very close to 'no programming experience'. I am enrolled in a computer engineering course, and I can tell you the amount of code we get to write is ridiculously low.
- CSDude 10y agoThey had only experience from university courses.
- johan_larson 10y agoA year and a bit into coding in Golang full time after many years in C++ and Java, I like the language too. Compared to both of those languages, it feels simple and clear, probably because it is fairly young and very opinionated. I can think of a few things I miss (single-line IFs, IMPLEMENTS clauses for structures, MAP/FILTER for collections, ...) but they are all fairly minor things.