Live data from Hacker News

Spf13 is leaving Google

spf13.com

91–100 of 179 posts

Re: Spf13 is leaving Google

#91
post #79
post #16

> 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…

No post body was provided.

Re: Spf13 is leaving Google

#92
When 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 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

#93
post #91
post #79

Earlier 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.

I am giving you concrete examples challenging his version of events. How is that not grounded in reality?

Re: Spf13 is leaving Google

#94

When 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

#95

When 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…

[deleted]

Re: Spf13 is leaving Google

#96
post #94

When 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.

also https://github.com/samber/lo

Re: Spf13 is leaving Google

#97
post #79
post #16

> 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…

Google search turned up https://www.mongodb.com/docs/manual/ as the MongoDB user manual.

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

#98
post #72

Earlier 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.

Honestly, most boutique, government-involved security consulting firms have similar requirements. Given how much of tech is outsourced these days, obscurity is often the only line of defense some organisations have.

Re: Spf13 is leaving Google

#100
post #36

About 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!

As someone who uses VS Code as their daily driver, I'm starting to tire of it and was considering trying out emacs or vim. Would you say spf13-vim is a good starter resource (curated plugins and all) or should I look elsewhere as a beginner?
Post reply on HN