Are we, though? Going to want to scale this up, I mean.
Unless economic systems around the world change significantly very soon, this AI replacement you so cavalierly mention would cause significant portion of human population to reach poverty, causing much unrest and mass deaths.
I don't buy into demonizing the rich, including Altman, Amodei, Musk and co.
I am not concerned that this will be the outcome of the productivity surge.
We will have enough for everyone, and ensuring comfortable living standards for the general population is going to be in the interest of those in power, even if you assume very selfish motivations.
I'd also like to point out that both Anthropic and OpenAI created frameworks to monitor labor market impact and propose responses.
How much of what you list has been "democratized"? Apart from the forum, and probably the browser, nothing. And both of those things are of questionable goodness to humanity.
> How much of what you list has been "democratized"? Apart from the forum, and probably the browser, nothing
Depends on what you mean by "democratized". It's surely at least as "democratized" as LLM access is, and that was the base line in this discussion. Probably meaning "everybody can use it for not-insane-money instead of just a small elite". (I don't necessarily agree with that notion, but at least we should use the same standards for things.)
> And both of those things are of questionable goodness to humanity.
If you think HN is bad for humanity, why do you participate? I can immediately list 100 things that are worse for humanity. Same thing with your browser.
That depends on your definition of winning. Some of us couldn't give a rat's ass about speed, and for me Chrome lost because it's not an user agent (as in agent working for me, the user) anymore, it's a Google agent (as in working for Google to spy on me, the user).
KDE Connect is a great program in this regard, allowing you to share all kinds of things, including contacts or clipboard contents, between connected devices.
KDE Connect is great. It just does all the little sync tasks between devices on the same network - like I assume Apple devices do - and I mean all of them. Want to transfer a file, or clipboard contents? It does that. Read battery level? It does that. Read SMS on your laptop? It does that. It even does remote input. Every feature separately optional to enable, and only between explicitly paired devices, of course.
I suspect that at the time they had to make a decision, Rocky Linux was not in good enough state, so they went with Debian, and now they already standardized around Debian, so no need to change.
Debian is to be used for some legacy systems because RHEL introduced microarchitecture restrictions. Rest of their infra is on AlmaLinux (a RHEL-compatible distro ala Rocky).
That's like not putting protective guardrail on a staircase, and instead having first aid kits and emergency phone number on hand. In other words, dumb and irresponsible. Possibly illegal, depending on the case.
It's become so bad that even quality history youtube channels are frequently using euphemisms like "moustache-man" instead of just saying "Hitler", to avoid their videos being buried by The Algorithm, and therefore cut severely into their viewership.
> even quality history youtube channels are frequently using euphemisms like "moustache-man" instead of just saying "Hitler"
That can be quite confusing. You had German mustache-man, Russian mustache-man, French mustache-man (Petain), French small-mustache-man (de Gaulle), Spanish small-moustache-man (Franco)
I'd like to add: we can't know a priori what will be needed to be known and what can safely remain behind an abstraction you just use.
That is revealed when our mental models grind against reality. Avoiding that friction at all costs is a problem because it will happen and you'll be unprepared when it becomes unavoidable.
Trusting some abstractions that have earned it but not all is how we deal with it. Limit your focus, and adapt. If you just trust all abstractions thrown in front of you until something breaks irreparably, you will be (person or organization) between a rock and a hard place and without any knowledge or skill on how to get out of that predicament.
That to me is the biggest risk in accepting the fallacy of general automation.
I’m in two minds about this, in some sense they did and it’s the same way in which the C code I write is mine, but the assembly underneath is an artifact of my intent, but I owe the compiler authors for it. On the other hand the cognitive distance between my C and the assembly is likely lower, but that’s because I’ve spent time staring at what was generated in order to figure out why my code was misbehaving. Which is itself not that dissimilar to figuring out how to get better at writing code with llms.
If you ask LLM to code something for you, and you then work on the code, then yes, there is partial ownership. Just like if you had asked another, maybe junior, developer to write a piece of code, and then you helped them make it better.
I think the difference involves how many layers of stuff someone claims is "theirs" and whether that claim of credit and expertise is valid.
Imagine a coworker writes some decent C code, but then at a meeting they start taking credit for the bytecode and the default optimizations done by the compiler.
That's analogous to people who write LLM prompts and then claim the same level of authorship over the code which was all generated and edited on an indirect level.
Unless economic systems around the world change significantly very soon, this AI replacement you so cavalierly mention would cause significant portion of human population to reach poverty, causing much unrest and mass deaths.
reply