Practical nil panic detection for Go

Re:Practical nil panic detection for Go by tome on Tuesday November 21, 2023 @07:11AM (#38362578)

Yes, I can read the title thanks. The article is about Haskell. The first sentence makes it clear it's speculative fiction presented as if from the year 2030. The article draws a hypothetical analogy between what could happen to Rust in 2030 and what is contemporaneously happening to Haskell.

[ Parent | on HN ]

Re:Practical nil panic detection for Go by usrbinbash on Tuesday November 21, 2023 @09:07AM (#38363768)

Yes, I read the article, thanks.

Yes, it is a speculative fiction, with a good reason, because the analogies are pretty clear.

[ Parent | on HN ]

Re:Practical nil panic detection for Go by tome on Tuesday November 21, 2023 @12:23PM (#38366770)

And to return to the topic at hand, despite that article pointing to some weakness in the Haskell community, Haskell is thriving, so "We're suggesting that people should just use Rust (or Haskell, or F#, or any other robust functional programming language) instead" seems like reasonable advice to me.

[ Parent | on HN ]

Re:Practical nil panic detection for Go by usrbinbash on Wednesday November 22, 2023 @05:24AM (#38377405)

> Haskell is thriving

https://news.ycombinator.com/item?id=38360177

So, according to what metric is Haskell "thriving"?

[ Parent | on HN ]

Re:Practical nil panic detection for Go by tome on Wednesday November 22, 2023 @03:36PM (#38384750)

I'm not sure what you mean. Are you saying that something that occupies 0.3% of an ecosystem can't be thriving? "Thriving" is not the same concept as "widely used" or "popular"!

[ Parent | on HN ]