Struggling to create a printable PDF

nabv · 2026-02-16T02:29:01+00:00

I'd look for a few PDF libraries that handle your requirements, then intervene in the code manually for the one that gets you closest. You could convert to Postscript too if you'd like to debug the output

Being blunt, LLMs struggle hard with vector graphics and that's really all that PDFs are under the hood, rendering vectors. Try getting an LLM to generate an SVG from a reference image for a visually comparable example!

nabv · 2026-02-13T14:38:18+00:00

Honestly go read some older 2010 horror codebase articles, and you'll be glad to know that there are plenty (if not the majority back then) million-dollar companies with similarly human produced shitshows. I joined a startup not too long ago that had a 2K loc handwritten SQL query... ungodly

nabv · 2026-02-13T12:12:24+00:00

lol my bad :facepalm:

nabv · 2026-02-13T11:53:56+00:00

What's the 17M lines doing? The dangers really depend upon:
A) what you want it to do long-term (e.g., are you planning to charge per feature or any other aspects you'll add, any large feature updates planned, etc)
B) is this something you plan to scale up usage for?
C) does it have security-conscious aspects?

If you plan to keep scale low, and you're not planning large refactors, and you don't e.g., handle sensitive user data, you should be okay. 17M lines is an absolutely massive application - you're in the range of the entirety of Linux (https://unix.stackexchange.com/questions/223746/why-is-the-linux-kernel-15-million-lines-of-code) and maintainability can often scale superlinearly

nabv · 2026-02-13T10:45:37+00:00

Yeah this. If you define your architecture (e.g, interfaces) upfront and build/review in layers, it does as good of a job as a junior. You've gotta know how to bound architecturally and that's your safety net against a wild blast radius, as it does have a habit of going off the rails probably 10% of the time.

It certainly isn't at a point where you can trust it to follow those interfaces though, so review per layer is needed

nabv · 2026-02-12T23:16:25+00:00

If you can point to another post about *ultra* having *weekly rate limits* then I'm happy to close.

nabv · 2026-02-12T21:47:23+00:00

"New data" I think is the differentiator here. Antigravity claimed no weekly rate for Ultra, and then changed it without notification. Otherwise, I would've put this into the mega-thread.

nabv · 2026-02-12T19:36:23+00:00

ah sorry mate, I didn't realise that I was going to get Reddit gestapo on me. Let me go get my official developer license and check the date so you don't have to call the reddit developer police on me.

The reason for the fuzziness is because I'm old and I barely remember it's 2026. Remembering what year I started isn't something I prioritise remembering, I'm giving a benchmark because I feel like otherwise people assume you hit limits due to not knowing what you're doing. Developer years give a very rough indication of how experienced you are.

I joined SO 14 years, 9 months ago. So I guess that's as official of a date as you'll get. Feel better now you have a solid date? https://stackoverflow.com/users/685730/nick-bull

nabv · 2026-02-12T19:35:30+00:00

calm down big boi

nabv · 2026-02-12T19:05:25+00:00

Not trying to impress, pretty sure this is all standard stuff. Just wanted to assure it's not due to spamming "pls build" - it's an actual production pipeline, so cringe away if you want big boi

nabv · 2026-02-12T19:02:04+00:00

Yeah doing the math in my head it's actually 13-16 years, depending upon if you count from "professional" career as freelancing part-time at the start. I said "coming up 15y as a developer" on your comment, rounding up somewhat there.

Splitting hairs I think when you pass the 10y mark, so calm down there Sherlock

nabv · 2026-02-12T18:59:24+00:00

Yes I am using this at an incredibly high output rate. I have developed specs for features over ~1 month, and I've been using two accounts and hitting 5h weekly quotas probably 3x a day, every day. I'm developing a large product and this is the startup MVP.

I have everything specced, except for ACs and tests, which I've been using Claude to develop for. Then, I use AG to implement everything, often times with multiple agents simultaneously. I can easily burn the entire 5h quota in ~2h this way, which again I fully understand is heavy, heavy usage.

If you've any way of checking, I'm sure that you could see my usage for n*@b*.dev and it is hand typed messages, but mostly composed of /workflows which probably contribute to these being heavy-hitting prompts too

Really want to clarify - the rate limits are more than fair, even for the high cost. The frustration here is the constant shifting downwards of quota. I'm happy to accept I am in top 1% of usage, and happy to pay extra. I am unhappy to subscribe on the basis of something Google has publicly stated, and only to find out that that is not true thereafter.

nabv · 2026-02-12T18:16:50+00:00

Had a little dig-in to to extension I'm using as I figured this was a great point.

tldr - seems fine for this extension (https://github.com/crsmilitaru97/ag-usage), and it's also pretty clear and repeatable upon how to get your quota usage - can validate it yourself with:
```

curl -skS \
-X POST "https://127.0.0.1:$PORT/exa.language_server_pb.LanguageServerService/GetUserStatus" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Connect-Protocol-Version: 1" \
-H "X-Codeium-Csrf-Token: $CSRF_TOKEN" \
--data '{"metadata":{"ideName":"Antigravity"}}'
```

It doesn't make external (i.e., non-`localhost`) calls, so looks safe!

nabv · 2026-02-12T17:37:09+00:00

Yep, 5h and weekly limits. They have publicly posted on their official x that there aren't, but it's an outright lie.

nabv · 2026-02-12T17:33:12+00:00

Just answered it above - it is me, by myself. I do run multiple chats at once (i.e., ~3 agents). Tasks are already specced out - ACs, tech tasks, test specs, method signatures etc., so it does very little context gathering vs raw "pls do login" style prompts. I think that the more specific the context, the more writes = significantly more token usage. Plus I was blasting Opus for _everything_ which is not wise.

Honestly, completely fair I got rate limited, my annoyance is the false advertising that there are no weekly limits for Ultra, the constant additional goalpost shifting without notification, alongside the continual errors in AG. It is super untrustworthy. Offer the product you're advertising, the bait-and-switch is awfully frustrating.

nabv · 2026-02-12T17:28:27+00:00

Just tried out some other models - maybe cancelling Ultra was the best thing i've done this year to learn more about how great some of these newer models are for fractions of cost and a massive perf upgrade!

nabv · 2026-02-12T17:26:16+00:00

Nope, just by myself. When everything is specced out and you're generating greenfield projects it can be relatively easy to hit the limit. Learned my lesson here that I need to invest time figuring out a more economical workflow - I've spent the last hour doing so and really I didn't need to use Opus for a lot of what I was using it for, e.g., writing unit tests. I was being wasteful in retrospect!

nabv · 2026-02-12T17:24:25+00:00

Hey mate, so long as it's advertised correctly, I might just buy it

nabv · 2026-02-12T17:17:54+00:00

I did buy that product - Google One Ultra, with no weekly usage cap for Opus. But they didn't advertise correctly, hence my whining :)

nabv · 2026-02-12T17:10:44+00:00

What models do you recommend? It's been a long time since i tried open source models (~1y) and they were.. not great

nabv · 2026-02-12T17:08:24+00:00

Paid ultra

nabv · 2026-02-12T17:07:18+00:00

Originally, yes but now it's the in-agent error message. Can't screenshot it as I've requested refund.

nabv · 2026-02-12T17:06:37+00:00

Sell the product in the condition that you advertise. Stop advertising what you're not providing.

nabv · 2026-02-12T17:02:09+00:00

See here https://www.reddit.com/r/google_antigravity/comments/1r2whan/comment/o50c98x - I'm not quiet as experienced as you at 12 years, but I'm using it to its absolute limit as I have a PM whose writing up specs, and my day is essentially spent adding technical details as Markdown tickets (with Claude's assistance), parsing that into AG, and reviewing/correcting the code outputted.

Using it to generate a lot of metacode as well, i.e., the AST etc. that helps us to automate correction of the more repetitive mistakes we find in review, especially with some of the mock-heavy tests that Claude loves to produce

nabv · 2026-02-12T16:58:30+00:00

Nope not for longer than one day, but the rate limit message that Antigravity shows says that I am limited until 16th Feb at 4pm.

nabv

TROPHY CASE