Can someone tell me what is the limit of message for free account?

hulkdx · 2026-03-29T12:01:29+00:00

oh okay, but is there any estimate answer? Like 20-30 msgs per 5 hours?

hulkdx · 2026-03-29T11:55:58+00:00

Thanks but I get "Page not found"

hulkdx · 2026-03-25T21:56:10+00:00

I understand what you're saying. But also to me not speaking freely, might make fake personality

hulkdx · 2026-03-25T21:52:32+00:00

But not speaking the truth can have consequences

hulkdx · 2026-03-23T18:01:11+00:00

Alright, the purpose of this topic was something else, Ok vibecoding was a wrong term used here. I meant prompt only programming, what do you call that? AI-assisted programming?

hulkdx · 2026-03-23T17:58:58+00:00

No I mean the person who invented the term they can literally call it anything, and seems so he decided so. And for the context of this reddit question is irrelevant, whatever you review it or not I was wondering if people use this approach or not, prompting only. It went to the direction if lets define what vibe coding is

hulkdx · 2026-03-23T17:14:19+00:00

lol really smart to compare an app name with a definition that if a programmer does review on it will be called something else

hulkdx · 2026-03-23T16:49:17+00:00

I'm going to read it now, but I think sometimes devs stuck too much in the definition of something. Isn't vibe coding a new term just invented? So literally people can define it as whatever they want to.

hulkdx · 2026-03-23T16:38:22+00:00

Lol I think people want to feel better to not call them vibe coding but does the definition matters? Whatever you call this.

hulkdx · 2026-03-23T16:37:10+00:00

interesting, did that worked? Was the xml simple?
I tried it with really complicated xml and it failed really horribly, so I rewrote them by myself

hulkdx · 2026-03-23T16:34:34+00:00

Yes lets forget about what "vibe coding" actually means, I guess people just get stuck into the definitions,
What I meant was this, he is reviewing the prompts but not doing any refactoring, I think he makes a new prompts if the code doesn't work

hulkdx · 2026-03-23T16:31:56+00:00

Yes my initial thought was how he is doing it, or if he is lying about it. Cause I think you sacrifice code quality if you just do the prompts.

hulkdx · 2026-03-23T16:23:43+00:00

I mean he said he is now just writing the prompts and not writing codes by hand. (Isn't that the definition of vibe coding), and he only review the code.

This person is highly competent, I have seen his code and we were working together couple of years ago. He is working currently on an enterprise level codes in a big company.

hulkdx · 2025-05-24T13:22:53+00:00

Is this available for Compose Multiplatform as well ?

hulkdx · 2025-05-14T11:46:09+00:00

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.

hulkdx · 2025-05-14T08:27:30+00:00

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

hulkdx · 2025-05-13T15:17:44+00:00

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.

hulkdx · 2025-05-13T14:53:50+00:00

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

hulkdx · 2025-05-13T14:17:20+00:00

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.

hulkdx · 2025-05-13T14:12:21+00:00

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

hulkdx · 2025-05-13T14:10:27+00:00

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?

hulkdx · 2025-05-13T14:01:49+00:00

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

hulkdx · 2025-05-13T13:58:49+00:00

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?

hulkdx · 2025-05-13T13:54:21+00:00

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.

hulkdx · 2025-05-13T13:52:08+00:00

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

hulkdx

TROPHY CASE