> I led the team that designed MongoDB’s pioneering user experience As someone who has used mongo, genuinely curious about which part of the user experience is being highlighted here. Thanks for all your work with the Go community and good luck with the new team!
“I led the team that designed MongoDB’s pioneering user experience." Let's break this down and I'll explain why he is a total liar and bullshit artist. This makes it sound like he designed the mongodb query language. Only he could pass off inflicting the crappy Drupal website as designing MongoDB's pioneering user experience. He can't be talking about MongoDB the company, it was 10gen so obviously insinuating it was…
Spf13 is leaving Google
91–100 of 179 posts
Re: Spf13 is leaving Google
#921. Functional operators like map/filter/reduce - all of these would be optional but would save SO many lines of code.
2. Add simple conveniences - e.g. "contains" to check if a key is present in a map. Again those who don't want to use these, don't have to.
3. Error handling boilerplate - something to the tune of "?" operator in Rust
Re: Spf13 is leaving Google
#93Earlier quoted context omitted.
“I led the team that designed MongoDB’s pioneering user experience." Let's break this down and I'll explain why he is a total liar and bullshit artist. This makes it sound like he designed the mongodb query language. Only he could pass off inflicting the crappy Drupal website as designing MongoDB's pioneering user experience. He can't be talking about MongoDB the company, it was 10gen so obviously insinuating it was…
Quoted post unavailable.
Re: Spf13 is leaving Google
#94When I initially started Go, it felt so easy to pick up. Then I wrote a component in it and it felt overly verbose. Then I had to revisit the component and had to do some heavy refactoring/additional testing and realized that the language, to certain extent, didn't stand in the way. After all these iterations, I think Go is leaving an-even-bigger-adoption on the table for the want of following: 1. Functional operator…
I'd love to see less verbose error handling too, but Rust's ? IMHO is not the best way to go - it adds quite a bit of magic and makes debugging difficult, when a question mark at the end of a line "injects" an unexpected return statement.
Re: Spf13 is leaving Google
#95When I initially started Go, it felt so easy to pick up. Then I wrote a component in it and it felt overly verbose. Then I had to revisit the component and had to do some heavy refactoring/additional testing and realized that the language, to certain extent, didn't stand in the way. After all these iterations, I think Go is leaving an-even-bigger-adoption on the table for the want of following: 1. Functional operator…
Re: Spf13 is leaving Google
#96When I initially started Go, it felt so easy to pick up. Then I wrote a component in it and it felt overly verbose. Then I had to revisit the component and had to do some heavy refactoring/additional testing and realized that the language, to certain extent, didn't stand in the way. After all these iterations, I think Go is leaving an-even-bigger-adoption on the table for the want of following: 1. Functional operator…
1 and 2 are now possible to implement, since 1.18 - I'm using this and it does save quite a bit of boilerplate: github.com/life4/genesis I'd love to see less verbose error handling too, but Rust's ? IMHO is not the best way to go - it adds quite a bit of magic and makes debugging difficult, when a question mark at the end of a line "injects" an unexpected return statement.
Re: Spf13 is leaving Google
#97> I led the team that designed MongoDB’s pioneering user experience As someone who has used mongo, genuinely curious about which part of the user experience is being highlighted here. Thanks for all your work with the Go community and good luck with the new team!
“I led the team that designed MongoDB’s pioneering user experience." Let's break this down and I'll explain why he is a total liar and bullshit artist. This makes it sound like he designed the mongodb query language. Only he could pass off inflicting the crappy Drupal website as designing MongoDB's pioneering user experience. He can't be talking about MongoDB the company, it was 10gen so obviously insinuating it was…
According to Github, he even contributed to it https://github.com/mongodb/docs/graphs/contributors
There's a lot of evidence that his claims are at least plausible if not credible.
You created a burner account and anonymously keep spreading obscure attacks and lies without any evidence.
Re: Spf13 is leaving Google
#98Earlier quoted context omitted.
In terms of "tightlippness", they don't come close to TGS Mgmt. All of their employees can't even list their employment at TGS Mgmt on LinkedIn.
I worked at a firm who had the same policy in 2014. It was more common than you may have realized.
Re: Spf13 is leaving Google
#99Re: Spf13 is leaving Google
#100About 10 years ago, spf13-vim showed me what vim could be and changed my coding life forever. I finally ejected it and spun my own .vimrc a few years ago, but I wouldn't be where I am today without it. Thanks a bunch!