#metabrainz

/

      • piwu1 has quit
      • 2023-07-15 19615, 2023

      • piwu1 joined the channel
      • 2023-07-15 19601, 2023

      • aerozol
        akshaaatt: btw, did you want the Android updates shared to MeB social channels?
      • 2023-07-15 19645, 2023

      • aerozol
        mayhem: don’t forget to look at my proposed press release re. metadata matters. Because it’s ‘spicy’ I want to run it by you before sending… https://docs.google.com/document/d/1ONWFAgDebp-NO…
      • 2023-07-15 19654, 2023

      • aerozol
        “Press Release 2023-07-14 - The music industry is failing musicians”
      • 2023-07-15 19606, 2023

      • aerozol
        🌶️
      • 2023-07-15 19644, 2023

      • aerozol
        Anyone who cares: I’m going to start reposting stuff we put on Twitter via my personal mastodon account, see what the engagement is like (even if we never make an official account there I might just keep it up anyway)
      • 2023-07-15 19626, 2023

      • aerozol
        Holiday news: Watched a national emergency go down here in Japan yesterday! Dog poo in the train station! Five employees, a gallon of disinfectant, and we are safe again - the offender is in newspaper, in a plastic bag, in another really big plastic bag, and safely disposed of. Great work tīmu
      • 2023-07-15 19630, 2023

      • aerozol
        Last.fm x Spotify integration is apparently very bad? My takeaway: ListenBrainz devs kick ass + let’s make sure we never overextend: https://www.reddit.com/r/lastfm/comments/14y7qr7/…
      • 2023-07-15 19611, 2023

      • aerozol
        Pretty nifty - apparently you can swipe right to scrobble a whole album (to last.fm) on this Discogs-centric app: https://apps.apple.com/jp/app/discographic-for-di…
      • 2023-07-15 19626, 2023

      • Maxr1998 has quit
      • 2023-07-15 19609, 2023

      • Maxr1998 joined the channel
      • 2023-07-15 19628, 2023

      • akshaaatt
        Sure aerozol! That sounds like a good idea
      • 2023-07-15 19621, 2023

      • aerozol
        Akshaaatt: yus, let's do it! Fill out this form for me please, don't spend more than a minute on it, no need to fill in text just link to the blog post: https://community.metabrainz.org/t/breaking-news-…
      • 2023-07-15 19617, 2023

      • akshaaatt
        On it
      • 2023-07-15 19649, 2023

      • OrbitalTeapot joined the channel
      • 2023-07-15 19614, 2023

      • OrbitalTeapot has quit
      • 2023-07-15 19650, 2023

      • OrbitalTeapot joined the channel
      • 2023-07-15 19623, 2023

      • OrbitalTeapot has quit
      • 2023-07-15 19633, 2023

      • d4rkie joined the channel
      • 2023-07-15 19650, 2023

      • d4rk has quit
      • 2023-07-15 19656, 2023

      • mayhem
        sorry aerozol , I've now read it and damn, that quote is spicy. who wrote that stuff? Lol.
      • 2023-07-15 19602, 2023

      • mayhem
        Looks great to me, fire at will!
      • 2023-07-15 19607, 2023

      • Maxr1998_ joined the channel
      • 2023-07-15 19605, 2023

      • Maxr1998 has quit
      • 2023-07-15 19615, 2023

      • jasje
        akshaaatt: merge with main pls so I can work with latest main. Some bugs im facing that i want to make sure are not caused by my code.
      • 2023-07-15 19629, 2023

      • jasje
        if you want I can do it
      • 2023-07-15 19619, 2023

      • ApeKattQuest
        man I wish they put in a quarter the effort japan does about dog-poo here. it's gross some places
      • 2023-07-15 19624, 2023

      • OrbitalTeapot joined the channel
      • 2023-07-15 19631, 2023

      • OrbitalTeapot has quit
      • 2023-07-15 19610, 2023

      • OrbitalTeapot joined the channel
      • 2023-07-15 19608, 2023

      • OrbitalTeapot has quit
      • 2023-07-15 19651, 2023

      • orbitalteapot joined the channel
      • 2023-07-15 19609, 2023

      • akshaaatt
        Hi jasje
      • 2023-07-15 19619, 2023

      • akshaaatt
        You had mentioned about a discussion on github
      • 2023-07-15 19625, 2023

      • jasje
        akshaaatt: will ping you outside rn
      • 2023-07-15 19606, 2023

      • akshaaatt
        Cool
      • 2023-07-15 19648, 2023

      • Maxr1998_ has quit
      • 2023-07-15 19618, 2023

      • jasje
        akshaaatt: yo
      • 2023-07-15 19600, 2023

      • akshaaatt
        Hi
      • 2023-07-15 19652, 2023

      • Maxr1998 joined the channel
      • 2023-07-15 19640, 2023

      • jasje
        so
      • 2023-07-15 19648, 2023

      • jasje
        about the singleton annotation
      • 2023-07-15 19633, 2023

      • akshaaatt
        Yeah
      • 2023-07-15 19646, 2023

      • akshaaatt
        Any reasoning you have for removing it?
      • 2023-07-15 19656, 2023

      • jasje
        i would like you to give this one a read: https://dagger.dev/hilt/components
      • 2023-07-15 19610, 2023

      • akshaaatt
        I have
      • 2023-07-15 19630, 2023

      • akshaaatt
        Please point out the reason for the removal of
      • 2023-07-15 19642, 2023

      • akshaaatt
        Omit of*
      • 2023-07-15 19656, 2023

      • jasje
        So basically when we scope all of our stuff to singleton
      • 2023-07-15 19610, 2023

      • jasje
        stuff -> dependencies
      • 2023-07-15 19618, 2023

      • jasje
        one instance is created
      • 2023-07-15 19628, 2023

      • jasje
        which reamins until app is destroyed
      • 2023-07-15 19631, 2023

      • akshaaatt
        Yeah that is correct
      • 2023-07-15 19640, 2023

      • jasje
        since we have listen submitter service
      • 2023-07-15 19654, 2023

      • jasje
        which causes the app to never call onDestroy
      • 2023-07-15 19618, 2023

      • jasje
        those dependencies remain forever (metaphor)
      • 2023-07-15 19609, 2023

      • jasje
        thus memory is always occupied for those objects as long as onDestory isn't called
      • 2023-07-15 19625, 2023

      • jasje
        even though they aren't even being used
      • 2023-07-15 19640, 2023

      • akshaaatt
        From my understanding, singleton just prevents the application from creating more than one instance and reuses the existing resources
      • 2023-07-15 19602, 2023

      • akshaaatt
        How is it related to the lifecycle?
      • 2023-07-15 19615, 2023

      • jasje
        but it still retains the instance even though it isn't being used'
      • 2023-07-15 19657, 2023

      • jasje
        lifecycle is what the Installin() part defines
      • 2023-07-15 19625, 2023

      • akshaaatt
        Even if I were to create multiple instances, do you mean to say that even those won't be destroyed?
      • 2023-07-15 19651, 2023

      • jasje
      • 2023-07-15 19620, 2023

      • jasje
        akshaaatt: if we scope them to singleton, no
      • 2023-07-15 19628, 2023

      • jasje
        but any other should be good
      • 2023-07-15 19605, 2023

      • akshaaatt
        I think service component should be the one to use here then?
      • 2023-07-15 19613, 2023

      • jasje
        usually hilt recommends don't scope bindings that don't require concurrency or are not heavy to create instance of
      • 2023-07-15 19630, 2023

      • jasje
        service component is used for brainplayer
      • 2023-07-15 19641, 2023

      • jasje
        yellowhatpro made sure of that
      • 2023-07-15 19647, 2023

      • jasje
        for rest
      • 2023-07-15 19659, 2023

      • jasje
        I think no scoping should be good
      • 2023-07-15 19603, 2023

      • jasje
        because hilt says
      • 2023-07-15 19628, 2023

      • jasje
        the amount of extra code for scoping usually outweighs the benefits
      • 2023-07-15 19641, 2023

      • jasje
        thus decreasing the performance
      • 2023-07-15 19648, 2023

      • jasje
        also
      • 2023-07-15 19609, 2023

      • jasje
        a component is only scoped if it has component and scope defined
      • 2023-07-15 19639, 2023

      • jasje
        if we just do Installin(singletoncomp){ // and not annotate @singleton here }
      • 2023-07-15 19653, 2023

      • jasje
        then the dependency wont be scoped
      • 2023-07-15 19601, 2023

      • jasje
        it'll be factory
      • 2023-07-15 19610, 2023

      • jasje
        i.e., new instance is created
      • 2023-07-15 19613, 2023

      • jasje
        everytime
      • 2023-07-15 19649, 2023

      • jasje
      • 2023-07-15 19632, 2023

      • jasje
      • 2023-07-15 19612, 2023

      • akshaaatt
        I think the services we create should be scoped
      • 2023-07-15 19631, 2023

      • jasje
      • 2023-07-15 19601, 2023

      • jasje
        this is very interesting to me and if you'd give some time figuring this stuff out i'd love to improve the code
      • 2023-07-15 19628, 2023

      • akshaaatt
      • 2023-07-15 19631, 2023

      • jasje
        bec my interpretations are half baked as well
      • 2023-07-15 19624, 2023

      • akshaaatt
        Don't get too much into this rn. Focus on the gsoc project first
      • 2023-07-15 19645, 2023

      • akshaaatt
        I feel we would end up falling off track with the project if you don't focus
      • 2023-07-15 19657, 2023

      • akshaaatt
        These changes can be done in a day or two later
      • 2023-07-15 19608, 2023

      • akshaaatt
        But yeah, I do think it'll be good
      • 2023-07-15 19612, 2023

      • jasje
        akshaaatt: dw
      • 2023-07-15 19628, 2023

      • akshaaatt
        I don't think services should be allowed to have multiple instances, and the way I see it is scoping them currently or resuing somehow.
      • 2023-07-15 19659, 2023

      • jasje
        alright
      • 2023-07-15 19603, 2023

      • jasje
        first of all
      • 2023-07-15 19628, 2023

      • jasje
        lets call the repositories something else
      • 2023-07-15 19658, 2023

      • jasje
        Im getting confused with the android services again and again xD
      • 2023-07-15 19606, 2023

      • jasje
        so
      • 2023-07-15 19608, 2023

      • akshaaatt
        Like?
      • 2023-07-15 19633, 2023

      • jasje
        in your above sentence, you mean the retrofit instances right?
      • 2023-07-15 19648, 2023

      • akshaaatt
        Yes
      • 2023-07-15 19652, 2023

      • jasje
        yes
      • 2023-07-15 19610, 2023

      • jasje
        so we need to scope retrofit instances to something else
      • 2023-07-15 19620, 2023

      • jasje
        not singleton agree?
      • 2023-07-15 19642, 2023

      • akshaaatt
        I don't agree yet. Need to read more on this
      • 2023-07-15 19655, 2023

      • jasje
        alright
      • 2023-07-15 19626, 2023

      • akshaaatt
        But I know for sure that these should only be created once throughout the app
      • 2023-07-15 19606, 2023

      • jasje
        i mean we can
      • 2023-07-15 19626, 2023

      • jasje
        because retrofit is heavy'
      • 2023-07-15 19647, 2023

      • jasje
        but can we scope it to activity?
      • 2023-07-15 19604, 2023

      • jasje
        because our app is single activity arch
      • 2023-07-15 19609, 2023

      • akshaaatt
        No. Multiple activities can use one service/repo
      • 2023-07-15 19610, 2023

      • jasje
        architecture
      • 2023-07-15 19626, 2023

      • jasje
        our app has only one activity
      • 2023-07-15 19631, 2023

      • akshaaatt
        jasje we need to do something about it though. It's not perfect yet
      • 2023-07-15 19640, 2023

      • jasje
        yess
      • 2023-07-15 19644, 2023

      • akshaaatt
        No. About, etc are separate activites for now
      • 2023-07-15 19608, 2023

      • akshaaatt
        Compose is still new and we need to see what is the best practice for all this
      • 2023-07-15 19639, 2023

      • jasje
        akshaaatt: our main activity isn't destroyed when we open about tho
      • 2023-07-15 19643, 2023

      • jasje
        so no problem there
      • 2023-07-15 19645, 2023

      • akshaaatt
        I hate that a composable cannot manage it's lifecycle yet
      • 2023-07-15 19600, 2023

      • jasje
        akshaaatt: true (fragments are noice)
      • 2023-07-15 19609, 2023

      • akshaaatt
        yeah
      • 2023-07-15 19622, 2023

      • jasje
        our main activity only gets destroyed when we close our app
      • 2023-07-15 19629, 2023

      • jasje
        thats what we want
      • 2023-07-15 19651, 2023

      • jasje
        except for the service (retrofit instance) that our submitter uses
      • 2023-07-15 19659, 2023

      • jasje
        that should be singleton
      • 2023-07-15 19605, 2023

      • akshaaatt
        Google should be working on getting compose right there. Because iOS has swiftui (jc counterpart) which does all of this perfectly
      • 2023-07-15 19628, 2023

      • akshaaatt
        Not just the submitter, but other stuffs are also a singleton
      • 2023-07-15 19648, 2023

      • jasje
        yim service doesn't need to be singleton
      • 2023-07-15 19607, 2023

      • akshaaatt
        Okay. That sounds fair
      • 2023-07-15 19614, 2023

      • akshaaatt
        But social and login stuff does
      • 2023-07-15 19649, 2023

      • jasje
        social service also doesn't need to be singleton
      • 2023-07-15 19603, 2023

      • jasje
        only listensService is required to be singleton
      • 2023-07-15 19611, 2023

      • akshaaatt
        for now it doesn't. But soon it will
      • 2023-07-15 19622, 2023

      • jasje
        how?
      • 2023-07-15 19632, 2023

      • jasje
        any future plans i don know hehe?
      • 2023-07-15 19643, 2023

      • akshaaatt
        Let me just look at how service scoping and singletons are different
      • 2023-07-15 19610, 2023

      • jasje
        refer the screenshots above
      • 2023-07-15 19616, 2023

      • jasje
        for quick snippets
      • 2023-07-15 19601, 2023

      • akshaaatt
        If the listens submitter were not there, singletons would have been fine for the app
      • 2023-07-15 19620, 2023

      • jasje
        akshaaatt: yes
      • 2023-07-15 19622, 2023

      • akshaaatt
        But I get your point as to how resources are left even though the app is closed
      • 2023-07-15 19607, 2023

      • akshaaatt
        I mean, if our app is single activity, we can scope all these services to the activity then
      • 2023-07-15 19613, 2023

      • jasje
        yes
      • 2023-07-15 19654, 2023

      • akshaaatt
        But I am certain this is not how things are going to be for long. Single activity app in itself is bad currently.
      • 2023-07-15 19644, 2023

      • jasje
        akshaaatt: why?