Ah, you new 'round these parts? It's unfashionable to speak directly--we must fragment, hypothesize, add complexity and nuance rather than simply leave someone's slightly vague statement uncorrected. -_-
Has docling improved? I had a bit of a nightmare integrating a docling pipeline earlier this year. Docs said it was VLM-ready, which I spent lots of hours finding out was not true, just to find a relevant github issue which would've saved me a ton of hours :/ allegedly fixed, but wow that burned me bigtime.
our team has tested docling pretty extensively, works well for simpler text-heavy docs without complex layouts, but the moment you introduce tables or multi-column stuff it doesn't maintain layout well.
Interesting perspective. I've mainly felt like i have 'American privilege' regarding the ease with which i open accounts of basically any sort on a whim, usually with little friction.
Oh no, this is just a Google thing. I've done the same verification bs for four different companies now, multiple times for each of them. I just keep an image of my license on my computer so I can upload it on demand. Google's payment verification is byzantine.
It'll trigger when you sign up.
It'll trigger if you create an Android developer account.
It'll trigger if you get a new phone.
It'll trigger if your card expires.
It'll trigger the month before your card expires. Why? Fuck you, that's why.
And it just happened to me again. I got a new phone and my personal payment account went into some verification status and I can't use my wallet. Even though Google itself moved the card. And I was able to add the card and use the wallet with my gmail account. Wtf.
As critical as I am of LLM use, the nice thing about it here is your configs can be version controlled, and rolling back changes is pretty painless.
I'd still want to go through any changes with a fine tooth comb to look for security issues and to make sure I know what it is adding and removing, but it's saner than letting an LLM run amok on a live system.
Hilarious and frightening. I don’t want LLMs anywhere near anything remotely important. We’ve already had to remove a few dependencies from our projects because of CVEs caused by careless LLM usage upstream.
Exactly.
I'm a little interested to see if perhaps designer's eyes will continue to open to the power of licensing terms and control of their work with the whole AI conversation. The only designers i've heard say they care about open source are on the web side of design.
For many folk's workflows, I'd wager that hypervisors are there and ready. I had a nice time setting up xcp-ng before deciding microk8s fits my needs more betterer; they're just plum good, well documented, and blazing fast.
I think the possibilities are huge with this area. I'd love to see more 'manager' layers that build on top of any 'cloud' system, even a local one, to give you a standard stack that is easy to move. Imagine something that lives at the hypervisor level (that you trust and was mature) taking control of your various cloud accounts to merge them and make it easy to migrate/leave one provider for another. I know that is the promise of terraform but we all want a good, consistent, interface to play with and then build the automation tools on top of. Maybe that is a good direction for proxmox? integrating with cloud providers in a seamless way. Anyway, a lot of promise in this area no matter the direction it takes.
reply