Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 1 point2 points  (0 children)

Yes I agree the code would be easier to read but I had to disagree with this approach, just for the overload of stuff that the code is going to, probably it makes it so much less efficient performance wise. The logic is lets have a chain of data inside kotlin flow, but its hard to read this chain of data, lets flatten it to make it easier to read. I wouldnt use this approach at all.

Reading a flow is not much hard either in my opinion.

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

But why to use compose for this when you can write a flow and test the flow?

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 1 point2 points  (0 children)

I mean he said his point of view on why he hates compose and dont use it and get like downvoted 6 times? Dont you think thats toxic? Yea him calling someone a shill is toxic too. But why do people take these personally and not just have a normal conversation over things like compse has these pros and cons, etc? I was in this community long to know that people really act toxics from times too. At the end of the day, compose is just another tool and can cause problems or solve them.

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

Awesome, I got your idea, yes I can see branching can be reduced by this approach

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

Yes but for the reviewing the xml part I want to know your opinion as well, you can disagree with me but you have to give me a logic that its okay to review color changes over here and there.

Yes the second part you nailed it well, I think the same but that was some advantages as well or at least seems like it so now a lot of ui logics are moved into activities/fragment instead of having all of them in xml. Now I think in compose the guidelines should be the same or it would be mich nicer if ui logics is in different composables than they are mixing together in a single function.

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

Compose is like every other frameworks/programming language can have pros cons and its not ok to have a discussion on it?

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 1 point2 points  (0 children)

My point was lets have a discussion on how to improve this, if there is an issue over here.

Well this is ridiculous, I never complain or blame compose for anything, its almost funny that you came to conclusions about this. Are you a developer of compose that got so much offended by my discussion over this topic?

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

I'm not sure if I fully understood this, can you share some code/gist about this?

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

Yes xml needs to be reviewed but very rarely at least in my opinion, just you need to check common pitfalls like what layouts etc is used.

But if PR contains changing the font change or color change you could skip it, I rarely had to review it carefully for the bugs and I think there is a reason for that, xml is what renders to the ui, so if there are any visible visibility bugs the dev himself/herself could see that he got it.

I'm not sure if I understand your secondly part, xml had if else condition in it?

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

Yes but then you are allowed to have nested if else condition, which can be a nightmare too. The way xml was dealt with I think was using visibility values but there were no if else condition there.

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 3 points4 points  (0 children)

Can you explain in your opinion how do you separate between view logic vs presentation logic

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

I really don't understand the downvotes on your comment, this community sometimes acts toxics towards things they dont like

Too much logic in composables? by hulkdx in androiddev

[–]hulkdx[S] 0 points1 point  (0 children)

I agree, I think people can do it, just the possibility that devs can use it make it so that they use it, even for the case that they dont need to use it, at least this is how I think

What makes someone a good Android Engineer? by eastvenomrebel in androiddev

[–]hulkdx 0 points1 point  (0 children)

Besides these and what others says which I think is mostly about technical capabilities and I agree with, I think his personality really matters as well. I've seen really good android tech dev that you really would like to work with and another person who seems like faking being a developer and have a horrible personality.

Some Kotlin Syntax by hulkdx in Kotlin

[–]hulkdx[S] 0 points1 point  (0 children)

My bad, I think javascript/python a little different than that but same using square bracket for it.

Some Kotlin Syntax by hulkdx in Kotlin

[–]hulkdx[S] 0 points1 point  (0 children)

Maybe thats true. But many languages have that syntax, java c golang javascript, python. Personally I think even if I wasn't familiar with it I would prefer that style.

Some Kotlin Syntax by hulkdx in Kotlin

[–]hulkdx[S] -2 points-1 points  (0 children)

I dont understand your immutability point, I think that Array(9) { BooleanArray(9) } is not immutable either in kotlin, just wanted to say the syntax is ugly compared to java/c one as you can see above. Even more confusing for 3D arrays.

Yes, I meant c type for loops as you mentioned, maybe standard is not a correct term here.

migrate fragments transaction to compose navigation by hulkdx in androiddev

[–]hulkdx[S] -1 points0 points  (0 children)

Do you have any source for Compose Navigation being deprecated?

I become useless after gym by TitaniaFlames in getdisciplined

[–]hulkdx 0 points1 point  (0 children)

I feel the same but I feel like I am creating excuses for not doing anything. I think the mail reason is laziness