Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Spf13 is leaving Google

spf13.com

Post reply on HN
Print view View original

111–120 of 179 posts

Re: Spf13 is leaving Google

#111

Post by konart »

noisy_boy wrote: post #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 operator…

>Add simple conveniences - e.g. "contains" to check if a key is present in a map.

Why though? it doesn't even save you much space compared to standard use:

if _, ok := m[key]; ok { }

vs

if contains(m, key) { }

I'm not strictly against it, but it can open pandora's box of all kinds of weird sugar flavors.

Re: Spf13 is leaving Google

#112

Post by anitil »

frob wrote: 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!

It's the first I've heard of it. What am I missing out on as a (fairly vanilla) vim user?

Re: Spf13 is leaving Google

#113

Post by pjmlp »

rfeague wrote: post #45

This article made me _really_ curious what manner of awesomeness is going on at Two Sigma, but couldn't figure it out from the website. @spf13, any pointers on where to find a good article on why TS is cool?

Looking at their careers postings, it seems spf13 will have to spend some time refreshing his C++ and Python skills.

Re: Spf13 is leaving Google

#114

Post by shepherdjerred »

hoten wrote: post #100
frob wrote: 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?

I’d recommend lunar vim

Re: Spf13 is leaving Google

#115

Post by pjmlp »

spoonjim wrote: post #61

Say what you will about Google but at least it's not a complete fucking parasite on society and the economy like a hedge fund.

Nah, it just does data mining across all their platforms to feed their ads infrastructure, what is wrong about that.

Re: Spf13 is leaving Google

#116

Post by giveupitscrazy »

konart wrote: post #111
noisy_boy wrote: post #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 operator…

>Add simple conveniences - e.g. "contains" to check if a key is present in a map. Why though? it doesn't even save you much space compared to standard use: if _, ok := m[key]; ok { } vs if contains(m, key) { } I'm not strictly against it, but it can open pandora's box of all kinds of weird sugar flavors.

I know zero go, despite having worked with it professionally for a short stint that I try and block out of my memory (not go's fault), anyway that first example looks like gibberish to me while the second is super clear.

Re: Spf13 is leaving Google

#117

Post by tptacek »

giveupitscrazy wrote: post #116
konart wrote: post #111

Earlier quoted context omitted.

>Add simple conveniences - e.g. "contains" to check if a key is present in a map. Why though? it doesn't even save you much space compared to standard use: if _, ok := m[key]; ok { } vs if contains(m, key) { } I'm not strictly against it, but it can open pandora's box of all kinds of weird sugar flavors.

I know zero go, despite having worked with it professionally for a short stint that I try and block out of my memory (not go's fault), anyway that first example looks like gibberish to me while the second is super clear.

It is deeply idiomatic in the language.

Re: Spf13 is leaving Google

#118

Post by [deleted] »

DoreenMichele wrote: post #85
wawjgreen wrote: post #84

Earlier quoted context omitted.

i don't know why your answer got downvoted. is HN community so devoid of a good sense of humor?

This is a super tired comment that gets posted endlessly. HN appreciates humor, but it loathes noise. A lot of humorous commentary is noise that adds no value. If you don't want your funny remarks down voted here, up your game.

[deleted]

Re: Spf13 is leaving Google

#119

Post by IshKebab »

tptacek wrote: post #117
giveupitscrazy wrote: post #116

Earlier quoted context omitted.

I know zero go, despite having worked with it professionally for a short stint that I try and block out of my memory (not go's fault), anyway that first example looks like gibberish to me while the second is super clear.

It is deeply idiomatic in the language.

But only because there's no `contains` function!

Re: Spf13 is leaving Google

#120

Post by konart »

giveupitscrazy wrote: post #116
konart wrote: post #111

Earlier quoted context omitted.

>Add simple conveniences - e.g. "contains" to check if a key is present in a map. Why though? it doesn't even save you much space compared to standard use: if _, ok := m[key]; ok { } vs if contains(m, key) { } I'm not strictly against it, but it can open pandora's box of all kinds of weird sugar flavors.

I know zero go, despite having worked with it professionally for a short stint that I try and block out of my memory (not go's fault), anyway that first example looks like gibberish to me while the second is super clear.

Well, that's because you do not work with go much I guess?

I can say the same about Fennel, List or Haskell.

The first example is the way to go in Go. It's idiomatic, not a hack. And it works the same way for many things (for example checking if a channel's closed)

Post reply on HN