Right, people misuse this term "democratized" all the time. Because it sounds nice. But it's incorrect.
Democracy is about governance, not access.
A "democratized" LLM would be one in which its users collectively made decisions about how it was managed. Or if the companies that owned LLMs were ran democratically.
It can be about both meanings. The additional meanings of democratize to describe "more accessible" are documented in Oxford and Merriam-Webster dictionaries:
I've been wondering recently if there's some practical path forward for some sort of co-op based LLM training. Something which puts the power in the hands of the users somehow.
The claim isn't that the LLMs are democratized. The claim is that LLMs are causing software development to be democratized. As in, people who want software are more able to make it themselves rather than having to go ask the elites for some. As in, the elites in IT now have less power to govern what software other people can have.
(Or alternatively, it's getting harder to stamp out "shadow IT" and all the risks and headaches it causes.)
But the LLMs are quite the opposite: People should not bother with developing software, but ask the big LLM providers to do it for them instead.
In all aspects of the term, software is getting less democratized. But that is in line with a decades long trend, where computers used to ship with BASIC installed and now you need a specialized IDE tool which has a learning curve.
It used to be that you could dabble with HTML but now you need to learn a few javascript frameworks just to modify existing code. You used to start a piece of software by running it, modern server software is a fragile jigsaw that is delivered to production in the cloud. The list goes on. The future we are being promised is that you ask your paid-for development agent to make the necessary changes you require and deliver in to production in the cloud.
Which is fine, in a way, but it shifts power to the professionals. Just as Google, Apple or Microsoft owns your identity and your data, and you pay to use it, they can also decide to deny access for any reason. They are private companies, after all, and it is their data.
If software development were democratized, then decisions that software developers make would be made democratically. On or off the job. On the job, the workplace would be run democratically, instead of as it is now, dictatorially. Or off the job, groups of engineers would be coming together to create governance and make collective decisions about the software they use, like the Debian project or the recent Nix governance. Neither is the case.
Building yourself a table using some new carbon fiber hammer isn't democracy. That's just consumerism.
Hard to state that LLMs "democratize" software development when LLM companies can ban you from software development for any reason or no reason at all, and without recourse of any kind. The HN frontpage currently showcases an Antigravity ban that applied across Gemini, and there's few companies that provide affordable LLM services.
The actual elites greatly extended their control over software development, that's the opposite of democracy
This only remains true so long as open weight models lack significant utility.
Access to compilers was almost as controlled as access to LLMs to prior to the GNU toolchain and Linux putting a C compiler and unix (ish) machine in the hands of anyone who cared for one.
The problem is compute and memory. I think OpenAI bought RAM supply mainly to choke the ability of consumer hardware to run open weight models (that hit the memory bottleneck before other constraints). Now there's a shortage in other components as well. I don't see how local AI can compete in usefulness.
Democracy is about governance, not access.
A "democratized" LLM would be one in which its users collectively made decisions about how it was managed. Or if the companies that owned LLMs were ran democratically.