Google recruiters have been doing this sort of thing for years. Most google SWE roles advertised in San Francisco didn't exist there, they just advertised to dupe you into taking the bus to Mountain View. I was told that if my interview was successful I'd need to work in Mountain View for a while, then apply to work in SF.
I asked a friend who works there, he said that requested to move to SF as soon as he was done with his first few month. He's a there 3 years, fairly senior and with three kids, commuting from the east bay (he loved covid), but he's still on the "waiting list".
- Namespace system strongly favours single-word names
- Type embedding allows for single-dot access (not this.path.is.long())
- Zero-elements allow for elegant, zero-line initialization and existance checks, alleviating in part the need safe navigatorion operators.
Also I'd argue that the lack of map and filter are programmer nudges towards more elegant, compact solutions, but that's hard to prove. I've been annoyed with the lack of standard ways of doing things as well, but most often it turned out that I was simply doing it wrong, and Go was carefully designed to make the wrong way annoying to use. The compactness doesn't stem from using fewer lines to express simple constructs like if else, but the overall code organisation and structure that are the result of nudges like this one, as well as the code encapsulation they use (no classes, but interfaces and structs) and acyclic dependencies.
Generics will come out with the next version, though.
> No map or filter functions (meaning you have to implement these in like 5-6 lines of code)
I like that Go doesnt have these. Many programmers seem to want these big bloated programming languages. So thats what you end up with, a bunch of slow bloated programming languages. Personally I just want something like C, but with a couple of minimal extra features (maps, built in package management, bounds checking). For me, Go is the closest thing I have found to C, without many of the C pitfalls.
> Golang relies on built-in generator comments to help alleviate all of the typing.
I have been programming Go for a few years, and I have like one file in all of my code that uses a generator comment. That file is to interface with the Windows API. Regarding pure Go code, I dont use generator comments at all, so I think this comment is overblown.
> I like that Go doesnt have these. Many programmers seem to want these big bloated programming languages. So thats what you end up with, a bunch of slow bloated programming languages.
Those features are added to remove bloat from your source code.
I don't think you understand what bloat is. Just because an end user program has less lines of code, doesn't mean bloat is reduced. That code gets made up in the API, or the language itself.
Well, obviously. GP used the phrase “compact and pretty”. It’s a bit of a stretch to interpret that as an objective statement. The charitable interpretation is that GP meant it to be subjective.
Edit: I got confused which post you were replying to. My apologies.
I asked a friend who works there, he said that requested to move to SF as soon as he was done with his first few month. He's a there 3 years, fairly senior and with three kids, commuting from the east bay (he loved covid), but he's still on the "waiting list".