Thank god

[u/Frosty-iron-0405]

Thank God the no 5-hour limits and same weekly usage is going to win. I don't know about y'all but I'm quite happy with the weekly limits, to be honest. At least if I had 5-hour usage limit barriers, that would interrupt my work a lot more than having less weekly usage. Thank God that the no 5-hour limits and same weekly usage low-key won. The voting is going to end in 30 minutes but it seems like it won

[u/Frosty-iron-0405]

5 hour limits are stupid

Think about it- there are certain times in the week that you work more than certain other times.

for eg. My usage is a lot less during the weekend, compared to week days
So now, I'm budgeting my usage over a course of 5 days, not 7
With 5 hour limits
I have to budget my tokens in so many other ways during the day, not just the week

[u/Da_ha3ker → u/Frosty-iron-0405]

Never said they weren't, but how many times did you hit the 5 hour limit on the Pro plans? I only hit it like 1-2x and I HAMMERED my account at the time. Like 7-8 concurrent sessions with /goal mode running. How many concurrent sessions are you running to hit 5hr limits on the Pro account? Plus account, sure, get rid of the 5hr window, it makes no sense for plus and go users and makes it unuseable.

[u/Icy_Distribution_361 → u/Da_ha3ker]

I'm not being provocative here, genuine question; what do you use it for, and what were you doing when you 'hammered' it?

[u/Da_ha3ker → u/Icy_Distribution_361]

😏

[u/Icy_Distribution_361 → u/Da_ha3ker]

Lol. I was being serious though!

[u/Da_ha3ker → u/Icy_Distribution_361]

I have microservices architecture, so I can spin up separate agents in parallel working on different repos/services entirely. They have shared data types and common libraries to communicate with each other, but having such a strong split, it is easy to have multiple separate changes happen at the same time, as long as the common libraries used for cross service communication is respected. Lots of people hate microservices. Problem is most of them don't actually commit to microservices so they have a "modular monolith with a micro service backbone" and get the worst of both worlds lol. Agentic workloads do great with smaller codebases. Microservices is how I keep the codebases small and focused.

[u/Icy_Distribution_361 → u/Da_ha3ker]

Cool. What kind of service and what code base is it?

[u/Da_ha3ker → u/Icy_Distribution_361]

https://willplatform.com/ I am the founder. (Not promoting, just answering your question) Horizontal scaling is big when you self host. You need high availability for everything, and some customers need better scaling of services than others (some have 300 mcp servers, others have 300 rag sources that need ingestion, some need meeting transcription, etc... you don't want to spin up all the resources for every customer when they only use 50% of the product features)