Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
William Boxhall
@williamboxhall
@/all The 0.0.13 version is available. See https://github.com/getclump/clump/blob/master/CHANGELOG.md for details
William Boxhall
@williamboxhall
@/all The 0.0.14 version is available. See https://github.com/getclump/clump/blob/master/CHANGELOG.md for details
Steven Heidel
@stevenheidel
@williamboxhall @fwbrasil Take a look at getclump/clump#99 when you get some time
Flavio W. Brasil
@fwbrasil
@/all I’ve just pushed to maven central the 0.0.15 version. See https://github.com/getclump/clump/blob/master/CHANGELOG.md for details
Steven Heidel
@stevenheidel
@/all I've pushed the 0.0.17 version. See https://github.com/getclump/clump/blob/master/CHANGELOG.md for details
Flavio W. Brasil
@fwbrasil
@stevenheidel @williamboxhall considering that there are systems in production using Clump, do you think it’s time to release 1.0.0? We’d be more constrained in terms of breaking changes, but maybe we don’t have much to change anymore
Steven Heidel
@stevenheidel
I think it's a good idea, it would give people more confidence in using it in their systems. However, I am definitely worried about how difficult it will be to change the API. Perhaps we should take some time and go through it to double check everything makes sense? I was hoping to have a few of my co-workers try out Clump and see if any API patterns emerge organically from their usage.
In particular, I've never used any of the "inner join" capabilities of Clump (ie. the underlying option). I always use .optional to deal with missing resources at the call-site, and then use an apply() at the end and it is always defined. The API right now seems split between methods for people using "inner joins" and people using "outer joins"
William Boxhall
@williamboxhall
I definitely agree that further usage makes API patterns emerge
like the singletonSource
but I also can't see the core API changing much
Steven Heidel
@stevenheidel
Just used sourceSingle for the first time today :D. It's awesome because when the other team supports a batch API we can just swap out the source
William Boxhall
@williamboxhall
nice! yeah exactly
it just means your Clump compositions are written the same consistent way
Steven Heidel
@stevenheidel
@/all Just pushed the 0.0.18 version. See https://github.com/getclump/clump/blob/master/CHANGELOG.md for details
Steven Heidel
@stevenheidel
@fwbrasil @williamboxhall This is the final change which I think is needed before we can release a 1.0.0 version: getclump/clump#106 . Let me know your thoughts.
Steven Heidel
@stevenheidel
Released 0.0.19
FYI @fwbrasil @williamboxhall I set up sbt-sonatype plugin so now after running release you just have to run sonatypeReleaseAll instead of having to log in and do it manually
Flavio W. Brasil
@fwbrasil
thanks @stevenheidel
i’d suggest to give some time so people can update to the last release
if everything’s fine, we can release the 1.0.0
Steven Heidel
@stevenheidel
Cool, sounds good
William Boxhall
@williamboxhall
really awesome @fwbrasil and @stevenheidel , agree with everything
Steven Heidel
@stevenheidel

Anyone ever seen this error: [error] Could not run test io.getclump.(any test class): java.lang.OutOfMemoryError: Metaspace

I've only ever seen it in the tests. Hopefully it's a memory leak in SBT and not in Clump...

Flavio W. Brasil
@fwbrasil
@stevenheidel I always see this kind of problem with long runing sbt sessions, there are some known leaks in sbt
was it running for a while?
Steven Heidel
@stevenheidel
Ya
Do you see it only in Clump or in other apps as well?
Steven Heidel
@stevenheidel
On my mac it always happens after I run the tests ~6 times in a row
Makes me very nervous that there's a memory leak somewhere
Flavio W. Brasil
@fwbrasil
@stevenheidel maybe you could analyse the heap dump
Steven Heidel
@stevenheidel
Released 0.0.20
Steven Heidel
@stevenheidel
@fwbrasil @williamboxhall - has the latest release been working well for you guys? Shall we release 1.0.0?
Flavio W. Brasil
@fwbrasil
hey @stevenheidel, I’m changing jobs and don’t have access to the codebase anymore. I think @williamboxhall is on holidays. I’d say that if you don’t have problems with the latest release, we should move forward and release 1.0.0
Steven Heidel
@stevenheidel
Released 1.0.0 :sparkles:
Flavio W. Brasil
@fwbrasil
\o/
Richard Chuo
@forthy
\0/
Steven Heidel
@stevenheidel
@/all Are you using Clump at your company? If so, let me know and I'll add you to the list of users in the README.
Richard Chuo
@forthy
You shall know later. 😉
Steven Heidel
@stevenheidel
@/all Just released 1.1.0 which includes a new .sourceTry method
Flavio W. Brasil
@fwbrasil
@stevenheidel thanks!
William Boxhall
@williamboxhall
\o/
William Boxhall
@williamboxhall
hey @stevenheidel , how is Clump adoption going at LinkedIn?
Steven Heidel
@stevenheidel
@williamboxhall - I should log into this more often :P They're sort of stalled given that LinkedIn is moving away from Scala. However, it is running in the backends of 2 highly used products.
Richard Chuo
@forthy
👍 Too bad that LinkedIn is moving away from Scala, though...
William Boxhall
@williamboxhall
Agree, cool to hear about Clump bad too bad about moving away from Scala. @stevenheidel what are you moving to?
Steven Heidel
@stevenheidel
Java 8. There's still Scala where it makes sense, like for Spark
William Boxhall
@williamboxhall
ouch. how do you feel about that? what was the rationale?
Steven Heidel
@stevenheidel
It sucks, but Java 8 is not that bad
Tharindu Galappaththi
@TharinduDG
Hi,
I have a simple question.
What are the most critical 5 moves/things that you would suggest to a person who want to become a pure functional programmer?