It was Conservatives ushered in most of the 19th C worker protections
The Health and Morals of Apprentices Act 1802 - limited pauper apprentice children to 12 hours of work a day and banned night work for them - radical at the time
The Factory Act of 1833 - banned employment of children under 9 in textile mills and, crucially, created factory inspectors (enacted by Whigs but due to pressure from the Torys)
The Mines and Collieries Act 1842 was the work of Lord Shaftesbury (Anthony Ashley-Cooper, 7th Earl of Shaftesbury) under Robert Peel's Conservative government. It banned women and girls from working underground entirely, and boys under 10.
The Ten Hours Act 1847 limited women and young persons to a 10-hour working day — which effectively did the same for men, since factories couldn't run without them. This was driven by Shaftesbury and Tory backbenchers, and it passed against fierce opposition from free-market Liberals who called it an intolerable interference with liberty of contract.
The Chimney Sweepers Acts (various, 1834-1875) banning the use of children as young as 4 being sent up chimneys. (Lord Shaftesbury again)
Disraeli's Conservative government of 1874–1880 passed a burst of social legislation including the Factories Act 1874, the Artisans' Dwellings Act 1875 (slum clearance), and the Conspiracy and Protection of Property Act 1875, which effectively legalised peaceful picketing — a Conservative government giving trade unions legal protections.
Read a good biography of Disraeli. Can't help looking his arc being "couldn't make up his mind about the corn laws" but maybe a good politician can't make up his mind when the public can't.
I am still laughing my ass off that The Economist gets flagged today as a left leaning publication when it was founded to advocate for free trade and still does... And of course they are politically homeless in the UK these days!
Guess they really do want to become the next Google after all.
Selling ads and shutting down products that people are using.
I wonder if it would recommend a competitor if you'd asked it.
It's very odd though, isn't it? Although I can understand it. I do feel like I have a "relationship" with Claude. I enjoy its personality. And often I'll just chat with it rather than trying to get anywhere, even Claude Code.
But there's always the nagging thing in my mind. Someone else could be reading this. Will be reading this. And even though you might trust that the people of today won't do anything with that chat, who has the keys tomorrow?
> Is running a piece of software with such a set of instructions a crime?
Yes.
The Computer Fraud and Abuse Act (CFAA) - Unauthorized access to computer systems, exceeding authorized access, causing damage are all covered under 18 U.S.C. § 1030. Penalties range up to 20 years depending on the offence. Deploying an agent with these instructions that actually accessed systems would almost certainly trigger CFAA violations.
Wire fraud (18 U.S.C. § 1343) would cover the deception elements as using electronic communications to defraud carries up to 20 years. The "lie and deceive" instructions are practically a wire fraud recipe.
> Imagine taking a picture on autoshot mode and refusing to look at it.
I don't have to imagine it, I did it for decades. You went on holiday and you had a budget 26 photos, all shot on auto and each one was precious.
I've got tens of thousands of lines of code I've never looked at, and it wouldn't matter if I did look at them because I don't even understand the languages that they're written in. I get Claude to write in Rust because the edit-compile cycle is shorter due to great error messages. I don't know it at all. I've got projects written in Erlang and Scheme - I've never written a line of Erlang either, and I only know Scheme from reading SCP.
"But it doesn't work." - This entire comment was written using a voice to text system Claude produced in Rust. My firewall was set up using Claude, my i3wm setup was done with it, I've had it installed Debian for a PXE using iScsi - an iScsi server Claude also wrote in Rust.
I then have it go to a central location because I use multiple machines and it creates a website so I can see what I've been working on.
Project | Prompts | Tools | Files | Words In | Words Out | Tokens In | Tokens Out | Cache R/W | Last Activity
Nawin | 10688 | 74568 | 7724 | 1201.3k | 1379.5k | 592.0k | 83.3k | 3221.4M/199.5M | 2026-01-30 20:31
Crabbit | 3232 | 14252 | 1348 | 310.4k | 259.1k | 82.7k | 17.6k | 755.0M/51.2M | 2026-01-30 08:22
Reading these figures now, I think it counts its own prompts, you know it talks to itself. There's no way I've typed ten thousand prompts on that project
Tiling window managers used to be a thing in the old days, they predate the invention of overlapping windows, there is a reason it is only a minority that reaches out to them nowadays.
Tilings are no better or no worse than floating. There are many users who would benefit from them (people who typically keep all their windows maximized), but have had literally zero exposure two them due to MacOS and Windows.
Complaints about lack of window snapping in MacOS vs Windows, a loose copy of tiling, are consistent across the internet. If MacOS and Windows had native tiling support, you'd see a fight fiercer than tabs vs. spaces.
The reason floating windows are used is because "that's the way it is done." Windows 95 wowed the world and established the status quo.
Not to mention the direction that the likes of Paper and Niri are going, these are things that very few users get to experience and therefore couldn't possibly have an informed decision on what they prefer.
> Not to mention the direction that the likes of Paper and Niri are going, these are things that very few users get to experience and therefore couldn't possibly have an informed decision on what they prefer.
niri is great because it gives you the best of all worlds.
Scrolling by default but you can easily float and tile things as needed. It feels so intuitive for how I use computers.
Having used Windows for 25 years, there's no chance I'll ever go back. This environment is already substantially better. That's after tricking Windows out with virtual desktops, global hotkeys, window positioning tools, launchers, multiple clipboards, heavily WSL 2 driven, etc..
I tried to switch a few times over the last decade but was always blocked by hardware issues on this machine, those blockers are gone now.
Yes, which is why people complain about MacOS vs Windows. People wouldn't complain about the lack of quasi-tiling in MacOS if they didn't care about it (which is the gist of your gp comment). The only reason they have experienced it is because Windows has quasi-tiling.
That reason being that there is a minority of people who reach out to anything instead of just using what they're given. Compounded by baby duck syndrome, of course.
Yup, but "normies" do need menus or at least some way to do things that has some degree of visual affordance (e.g. a persistent cmd/ctrl+p, which I think Office has/had).
You aren't telling us anything about how you're using it. So how can we tell you what you're doing wrong? You're just reporting what happened.
You haven't even said what programming language you're trying to use, or even what platform.
It sounds to me like you didn't do much planning, you just gave it a prompt to build away.
My preferred method of building things, and I've built a lot of things using Claude, is to have a discussion with it in the chatbot. The back and forth of exploring the idea gives you a more solid idea of what you're looking for. Once we've established the idea I get it to write a spec and a plan.
I have this as an instruction in my profile.
> When we're discussing a coding project, don't produce code unless asked to. We discuss projects here, Claude Code does the actual coding. When we're ready, put all the documents in a zip file for easy transfer (downloading files one at a time and uploading them is not fun on a phone). Include a CONTENTS.md describing the contents and where to start.
So I'll give you this one as an example. It's a Qwen driven System monitor.
reply