Live data from Hacker News

GoPlus – The Go+ language for data science

github.com

61–64 of 64 posts

Re: GoPlus – The Go+ language for data science

#61

Earlier quoted context omitted.

Yes, as a dev who started in Python and has done more JS recently, I’ve really come to believe that the chaining of in-line functions is a better approach in the end. Python theoretically has the advantage of working with lists or iterators, but in practice, all you really use are lists.

To be fair many tools use iterator types that are not lists like Django querysets. I feel the nice thing in Python is generator expressions, so for lots of code you can decrease the memory footprint and speed some code up through easy lazy evaluation. I do appreciate the clarity of function chaining, and I think Rust made particularly good decisions around iteration in that way. Function chaining ideally needs good w…

If you’re doing a list comprehension with a Django queryset, you’re risking having a million accidental DB requests

Re: GoPlus – The Go+ language for data science

#62
post #25

Earlier quoted context omitted.

> I'm surprised comprehensions in particular haven't spread to more modern languages. I've come to dislike list comprehensions. Simple ones are ok but they do not handle incremental complexity well. Invariably it means code slowly becomes really unreadable as time goes by because nobody wants to rewrite the list comprehension when one more little tweak stuffed in there will do the job. I much prefer object-functional…

Functional chaining (aka “fluent interfaces”) is very bad for dependency injection / mocking. In f(g(x)) you can directly access or patch f and g as top level names. In x.g().f() you have to patch methods internal to other structures, and this can lead to problems if the patching should only happen in a certain local scope. I encountered this recently with differences between pathlib.Path and os in Python. Consider d…

A very valuable insight, thank you.

Re: GoPlus – The Go+ language for data science

#63
post #51
post #44

Earlier quoted context omitted.

They're great until you find something like this in code: [x for y in z for x in zz if y in x] Then you begin to wonder how great they really are.

Also, most data scientists presumably have some advanced math background so it's akin to reading set-builder notation (albeit with listcomps the sets are sometimes nested). Your listcomp reads: {x : y ∈ z, x ∈ zz | y ∈ x} If you've read enough statistics/ML papers, this becomes second nature.

Interesting. I didn't know that!

Re: GoPlus – The Go+ language for data science

#64

I'm founder of the Go+ project. And thanks for your attention. We run this project very seriously. It will be released weekly until version 1.0 is released.

Thank you so much for this! I submitted it here because I stumbled across it and was really surprised that it hadn't been on HN yet! If we somehow get Go+ in a Jupyter Kernel that would be awesome!
Post reply on HN