Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    matrixbot
    @matrixbot
    BarrOff Interesting. 😂
    Hugo Granström
    @HugoGranstrom
    Haha there are apparently more than two sides on this coin 😂🙈 poor maintainer 😬
    Bug fixes are the least fun part of coding 😅
    Vindaar
    @Vindaar
    Hello there! Just noticed you have a gitter room for numericalnim :)
    Hugo Granström
    @HugoGranstrom
    Good afternoon 😄 Yeah it was BarrOff's idea to use Gitter for discussions rather than cluttering Issues and PRs.
    Vindaar
    @Vindaar
    Yeah, it makes sense for some things, especially simpler "how to do x" questions and this sort of stuff
    Hugo Granström
    @HugoGranstrom
    Yeah definitely :)
    The data science packages for Nim is starting to stack up now, Arraymancer and ggplotnim is a really promising start to make Nim more attractive to new users when they see we got both a great Dataframe/Plotting library and a nd-array library.
    The key now I guess is to make sure they all cooperate with each other, that is one of the main strengths of the Scipy ecosystem that everything works together
    So I think mratsim's question to us and brentp this morning was really good. To make sure his changes doesn't break the other stuff that's out there.
    Vindaar
    @Vindaar

    Thanks for the kind words :)

    The key now I guess is to make sure they all cooperate with each other, that is one of the main strengths of the Scipy ecosystem that everything works together

    and yes, this is something I've been thinking about more and more, since I rewrote ggplotnim's data frame

    I agree
    The thing I've been wondering about most lately however is whether we should strive for a single library "which does everything", kinda like scipy itself, you know?
    That is regarding pure numerical calculations of course
    data frames and plotting don't belong in there
    but integration routines and a lot of stuff I have in my seqmath fork here: https://github.com/vindaar/seqmath
    that would both help to maintain code working together, put more eyes on the written code and most importantly would help more with discoverability of the functionality for newer nim users
    Essentially people will certainly stumble over arraymancer, if they check out nim in regards to data science. And it might help to make use of that
    Vindaar
    @Vindaar
    sorry for the ramble :D
    Hugo Granström
    @HugoGranstrom
    A single big library would probably work really good in Nim as it only compiles the code which is used so the binaries doesn't blow up in size just because of it
    So iI think that would be a great idea! SciNim or NumNim could be two possible names 😂 (the reason I didn't go for NumNim instead of NumericalNim was actually so that there wouldn't be any name conflicts in the future) 😅
    Having multiple people working together rather than in separate packages is also a really neat thing we would get from this
    Hugo Granström
    @HugoGranstrom
    As it is right now it's really easy to miss cool packages like your seqmath simply because they aren't mentioned that often (although I do recall it being mentioned quite a bit in the past)
    So uniting all these packages into a God Package would definitely help with bringing functionality to the users
    Vindaar
    @Vindaar
    yes, definitely!
    for the single big library I think one has to do one thing though. At least if I consider arraymancer. At the moment arraymancer has a single arraymancer.nim, which imports and exports all submodules. But due to how nim imports work, I think one cannot actually import only parts of arraymancer, e.g. import arraymancer / tensor just doesn't work for some reason.
    And obviously importing everything for each piece is not really a good idea. But that should be easy to solve
    We should chat with @mratsim (does cross channel pinging work in gitter?) and whoever else writes code in this domain
    Hugo Granström
    @HugoGranstrom
    Right, the project structures are a bit odd sometimes in Nim :/
    Haha cluttering the namespace with several houndred thousands of lines of code, what could go wrong 😂🙈
    A solution is needed indeed
    No idea actually if it works 😬 we'll see I guess. What other people are there out there that you know of?
    Vindaar
    @Vindaar
    regarding the imports I think it should be solvable by having all major submodules one might want to import in the src/ directory directly. So like src/tensor.nim etc. and arraymancer.nim is also sitting there, which just imports those submodules and exports them.
    I think nimble will complain about "bad project structure" or whatever it is, but well
    Other people? Hm, from the top of my head maybe @bluenote10 and @brentp. Aside from that not sure right now
    Brent Pedersen
    @brentp
    hi, guys. didn
    t know about this channel til now..
    Hugo Granström
    @HugoGranstrom
    Hi Brent! Would've been surprised if you did... 😅 Not much has happened here 'til today
    (cross channel pinging seems to work at least)
    Vindaar
    @Vindaar
    haha, that's established :D
    matrixbot
    @matrixbot
    BarrOff Hello Vindaar and Brent! Great to see some new faces on here. 😀
    Mamy Ratsimbazafy
    @mratsim
    Hey there
    yes cross channel pings seem to work
    I learned that nimble can handle monorepo: for example https://github.com/nim-lang/graveyard
    so that's one way of having multiple modules
    If we do a monorepo I don't recomment using the src approach as long as nimble eats the directory, @Vindaar and me had troubles with that
    otherwise we don't need an actual monorepo, just an umbrella organization
    and we put all the stuff under it, it could be SciNim for example
    NumNim is a bit hard to pronounce :p
    doesn't roll off the tongue
    Hugo Granström
    @HugoGranstrom
    Haha yeah it has the risk of turning into Nomnom if you say it often enough 😂 We could go with the slogan "The tastiest Numerical package" then 🤪
    Oh monorepos was new to me