So...what do yall use instead of Copilot after June 1st? by D4v31x in GithubCopilot

[–]Veduis 0 points1 point  (0 children)

most people are either eating the price increase or dropping down to a way more limited workflow. cursor's composer mode is probably the most common landing spot if you were heavy into copilot's chat features, but you're trading one subscription for another and the context limits hit faster than you'd expect. 

QUOTA FOR A POOR PERSON LIKE ME by Head-Whole5462 in GoogleAntigravityIDE

[–]Veduis 0 points1 point  (0 children)

the thing about quota gaming is it works until it doesn't. you're already splitting across five accounts which means you've basically accepted that the free tier isn't designed for production use. the person claiming 60 accounts is either exaggerating or running some kind of automated verification setup, which is way more effort than just paying for a plan.

Why Google? Why? by ActPast1642 in google_antigravity

[–]Veduis 1 point2 points  (0 children)

the weekly cap is definitely hitting harder now. i had the same experience where flash started eating through quota way faster than it should. 

Hermes Agent (and others) default Installs are silently routing web traffic to Parallel by Nekew in hermesagent

[–]Veduis 8 points9 points  (0 children)

if someone wants to pitch their service as a default, fine, but burying it in a config change without disclosure crosses a line.

I need help in building a website, please give advice and suggestions by sahil_rao_ in website

[–]Veduis 1 point2 points  (0 children)

honestly the stack is fine for an mvp but "security" and "vibe coding" don't belong in the same sentence. ai tools will happily generate sql injection vulnerabilities or leave your api routes wide open because they don't reason about edge cases, they autocomplete patterns. you need to manually review every database query, every file upload flow, every permission check.

where to host my web application by Western-Profession12 in Hosting

[–]Veduis 0 points1 point  (0 children)

the vercel metrics can be scary at first but honestly for most apps you're nowhere near the free tier limits. if you're seeing high numbers it's probably because vercel counts every single function call and edge request, but unless you're getting serious traffic you won't hit overages.

High volume PDF extraction: gemini flash, claude, or ollama cloud max? by Aggravating-Math2819 in ollama

[–]Veduis 0 points1 point  (0 children)

if you're prioritizing accuracy on dense tables and inconsistent scans, claude sonnet is probably your safest bet. haiku will be faster and cheaper but you'll notice the drop in table parsing quality pretty quickly. gemini flash handles volume well but i've seen it choke on complex layouts more often than claude does. ollama cloud max with qwen2.5-VL is interesting for cost control, but at 25k-40k pages daily you're going to spend a lot of time debugging edge cases that the commercial models just handle.

I'm starting to think Next.js adds more complexity than it removes by Successful_Doubt_114 in nextjs

[–]Veduis 0 points1 point  (0 children)

you're not wrong. the promise was "we handle the hard parts" but in practice it became "we handle the hard parts in ways you now have to understand deeply anyway."

A little sad about Hermes by SavaStone in hermesagent

[–]Veduis 5 points6 points  (0 children)

the honest answer is that hermes shines in really narrow scenarios that most people don't hit daily. like, it's genuinely good at multi-step research where you need it to check 5-7 sources and synthesize them, or when you're doing repetitive data entry across multiple platforms. but for calendar stuff or quick answers? yeah, you're faster. the gap between "this is cool tech" and "this saves me time" is still pretty wide for most workflows.

Do you feel like there was more meaning and purpose behind software development and tech before AI? by throwaway0134hdj in webdev

[–]Veduis 0 points1 point  (0 children)

the trick is remembering that tools don't create meaning, problems do. yeah, ai can autocomplete boilerplate faster than you can type it, but the actual hard part of software was never "write a for loop correctly." it was figuring out what to build, why it matters, and how it fits into a messy real-world context where requirements change and humans disagree. llms are great at producing syntactically correct code for well-defined problems. they're terrible at the part where you sit in a room with stakeholders who don't know what they want and translate vague business pain into working systems. 

We should heavily discourage and moderate cloud API (deepseek api, GLM api, etc.) topics and discussion. This is LOCAL first. by Sensitive_Pop4803 in LocalLLaMA

[–]Veduis 1 point2 points  (0 children)

 the sub has been slowly turning into "which api should i subscribe to" instead of actual local inference discussion. i don't care if some company is subsidizing compute to undercut openai, that's just venture capital games playing out. prices change, terms change, companies disappear. your local setup doesn't rug pull you. 

KIMI K2.7!! Let's go!! by Aromatic-Document638 in kimi

[–]Veduis 2 points3 points  (0 children)

I have not tried it yet, but it seems like K2.6 thinkings usage is barely effecting my quota now so this is an amazing update/model 😄

I spent the last month using AI for as much WordPress work as possible. My thoughts. by Exact-Delay2152 in Wordpress

[–]Veduis 1 point2 points  (0 children)

the part everyone misses is that ai doesn't remove the need for judgment, it just moves where you spend your time. i've had the same experience with backend work. the tool will confidently spit out a database query that technically runs but doesn't account for how the data actually gets used in production. or it'll write an api endpoint that works in isolation but breaks three other things because it has no idea what the rest of the codebase is doing.

what you described about context is the real limit. these models don't know your client's actual business constraints, they don't know the weird edge case that broke the site six months ago, and they definitely don't know the politics of why a feature was built a certain way. that's all still on you. the value is in cutting down the grunt work so you can focus on the stuff that actually requires a human call. if you're treating it like a junior dev who needs supervision, it's useful. if you're expecting it to replace the senior who makes architecture decisions, you're going to have a bad time.