One of the very few good things from the AI race has been everyone finally publishing more data APIs out in the open, and making their tools usable via CLIs (or extensible APIs).
They aren't doing that though. At least not yet. It's generated from the discovery tool, which amounts to the spec of the existing API. If they want a high powered CLI they need to dig into the servers behind Google Workspace like they have when they've improved the web apps.
Around where I live, we have electric car ferries.
To avoid having to upgrade the grid massively, we use large battery banks shoreside which are being charged at a sustainable (to the grid) rate, then the ferry charges rapidly by depleting the battery bank, leaving the grid alone.
Electrifying all transport in the nation would increase electricity load by 20%.
But even if 100% of all vehicles sold today was electric, it would still take ~20 years before almost 100% of vehicles on the road were electric. And it's not, so we're probably looking at > 30 years to increase electricity load by 20%.
That annual increase is far less than the increase caused by data centers. It's about the same as the annual increase in load caused by increased use of air conditioning.
The entire point is to add friction. Accepting code into public projects used to be highly frictive. RMS and Linus Torvalds weren't just accepting anyone's code when they developed GNU and Linux; and to even be considered, you had to submit patches in the right way to a mailing list. And you had to write the code yourself!
GitHub and LLMs have reduced the friction to the point where it's overwhelming human reviewers. Removing that friction would be nice if it didn't cause problems of its own. It turns out that friction had some useful benefits, and that's why you're seeing the pendulum swing the other way.
Linux powers the world in this area and bash is the glue which executes all these commands on servers.
Any program or language you write to try and 'revolutionise CI' and be this glue will ultimately make the child process call to a bash/sh terminal anyhow and you need to read both stdout and stderr and exit codes to figure out next steps.
Why? We've spent years upon years upon years of building systems that enshittify processes. We've spent years losing talent in the industry and the trends aren't going to reverse. We are our own worst enemy, and are directly responsible for the state of the industry, and to an extent, the world.
To not call out bullshit where one sees it, is violence.
Voting is one of those things that people care very little about but it's extremely important as it can determine who is the head of state (a position that has a lot of power an influence).
A single compromise once can have incredibly bad long term consequences for the majority of a ruling elite gain power indefinitely.
You're being downvoted because not everyone has CLI access to a server and the required ghostscript binaries etc.
Realistically, most 'normal users' have PDF needs like these links and we as tech people can safely give these sites to non-technical people and have confidence their data isn't being stolen on remote dodgy servers (think gas / electricity bills, invoices, bank statements etc which is a PII gold pot).
Server? what server? Ghostscript is available in virtually any Linux distro, on Mac with and without brew and even on Windows.
I have no confidence in any website, especially the one that claims to be local-only but can technically change on a whim of the developer once it starts getting enough traffic from users.
OTOH, I trust 30+ years old software sitting on on my hard drive not to phone home on every keystroke.
reply