So sorry, there’s a typo in your second sentence and I can’t figure out what you meant to say.

There wasn’t any way he could have communicated this that the Torygraph wouldn’t turn into “Strarmer lied and broke his promises to working people”. Saying it the precise way doesn’t make for good campaign slogans.

I suspect they planned this. If he had said “we won’t raise income tax and we won’t raise employee national insurance contributions”, he’d be giving a massive hint as to what he was planning, and the inevitable interview question would be about employer contributions and he wouldn’t be able to rule them out, and then all the headlines would be about “Starmer promised to not raise national insurance but now he’s let on that he’s planning to after all” and all the news would be about Labour’s tax rises and all this arguing would be happening before the election. A bit of ambiguity and headline management is unfortunately necessary.

Your claim to be a worker because you did half an hour’s work in a month for a landlord’s income that’s so large you can afford to discount it by £300 a month isn’t the winning argument you think it is.

Yesterday I heard they were reducing the amount people on universal credit can have their payment reduced for utility debt etc, which is good. It’s not all completely horrible, there are some silver linings.

Then your income wouldn’t be affected in any real way by raising taxes on those shares and getting cross that Starmer taxing unearned income is affecting you badly is bothincorrect and missing the point.

Starmer is raising tax on unearned income instead of working people’s taxes, which is very fair for a change, and you’re splitting hairs over definitions of who counts as workers. You’re so missing the point.

Why are you so cross about this? He only means that he’ll tax their unearned income a bit more, and if they really are working people out won’t affect them much.

The extent to which it affects workers is the extent to which they aren’t workers. It isn’t the logical gotcha you seem to think it is.

If Starmer suggested taxing football income you would be being a bit daft if you claimed that it was going to hurt the guy you just replied to on the grounds that he earned fifty quid from football.

“But he’s a worker too and he’s not rich and you promised not to tax him” is sillier than saying that he isn’t covered by the promise to not raise taxes on working people.

That’s because (and this is the bit that’s not quite got through to you somehow yet) the vast, vast, vast majority of his income is from working, not from football.

But if he said “income from owning shares isn’t eligible for PAYE taxation and therefore isn’t covered by a pledge to not increase taxes on workers’ earnings” he wouldn’t have a headline and you would be accusing him of talking like a politician and breaking promises.

But no, he was asked this in the context of some disingenuous question like “bbbut you promised not to raise taxes on working people, and this will hurt working people, aren’t people with a hardworking fast food day job and a tiny bit extra from a few shares or renting out their spare bedroom just to make ends meet exactly the working people you promised not to raise taxes on?”

And Starmer says no, and now we have a headline because a bunch of shareholders who are experts at hoarding money because it’s all they really care about are as pissed as they ever get because tHe GovErNmunT iS tAkiN aLL MY mUnnY.

It’s the daily telegraph, for goodness sake. When did they ever care about ordinary people’s finances?!

Owning a house isn’t a job but maintaining one is.

I think you just agreed with each other a little bit.

Thank you.

Yes, before Brexit, we were able to return asylum seekers to France because under EU rules, you didn’t have the right to claim asylum in one country if you had also passed through another safe country, and guess what, France counts as safe. The French helped enforce this because they were obliged to.

But now we’re a third party country, we can no longer send them straight back, hence the massive growth in channel crossings under the Conservatives. But the Brexiteers didn’t really want to reduce migration at all, because keeping you blaming some poor person in a boat for your problems keeps you from blaming rich people and corporations for taking all your money.

Why

I can answer that in one word: Brexit.

Oh yeah, rust has to win, but I think this was an empathy-free paradigm war masquerading as an innocent request for information. I think trying to bolt rust into Linux is a strategic error. It’s going to cause quite a lot of unnecessary friction and an awful lot of unnecessary technical complication and will be absolutely riddled with complexities and ways of doing things that are inherently unsafe. Instead build a posix compliant OS as rust from the bottom up and it’ll knock the spots off Linux and will be rock solid. It’ll take well over a decade but it’ll be far, far better.

TL;DR: Vast culture clash that rust guys didn’t perceive and C guys hated and false assertion that “you don’t need to learn rust” based on inexplicably naive lack of understanding that maintenance might be necessary.

If someone builds a rust api on top of your C code inside your project, you have exactly five choices: (1) preserve the assumptions the rust code is making (2) only change your code if you have a rust expert to collaborate with handy (3) edit the rust code yourself (4) break the rust assumptions leading to hard to find bugs (5) break the build. The C guys hated all five of those options, and the rust guys told them they didn’t need to worry their pretty little heads about it. ON, they weren’t as dismissive as that, but they either didn’t understand those as issues or didn’t care about them or dismissed them.

The rust guys were asking the C guys to tell them the semantics so that they could fix the type signatures for their rust functions and the C guys were reluctant to do that because they wanted to be able to change the semantics of that turned out to be useful to them. They didn’t want to commit so something that was documented in a way they weren’t familiar with because they felt that even if they wanted to, they couldn’t ensure their code was compliant with this specification going forward because they didn’t understand the rust type signature fully. (They got hung up on the self argument and launched a rant against OOP.)

The rust guys knew instinctively that the Result return type meant that the operation could fail and could tell from the two arguments to that both in what ways it could fail and every kind of answer it could produce if it succeeded, but the C guys found almost none of that obvious. This was for just one function in the rust API, but it also radically changed the way of doing it. This one rust call replaced the whole algorithms of ask, check answer, if none, check this and that, otherwise do this blah blah blah. The C guys are used to keeping everything lean and simple with a single purpose and were being asked to think of a while collection of procedural knowledge and edge cases with a handle everything monolith. But they were audibly reluctant to commit to that being all the edge cases because they don’t think of all of those tests as one thing and instinctively wouldn’t write something that checks for all of the edge cases because (a) in a lot of circumstances the code they’re writing only needs to know that there was a problem and will give up quickly and move on and (b) they want to be able to freely choose to add other edge cases in the future like they normally do without having to worry about the rust code breaking.

They weren’t complaining that they were being asked to write rust, they were complaining that they didn’t want to learn rust, and they were complaining this because they could see that to preserve all the rust API type signatures they would have to understand them, the expectations around them and memory safety principles, so that a rust programmer in the future wouldn’t have to change the rust type signature.

The rust guys would have gained a lot more traction by just asking the C guys to keep a bunch of comments up to date detailing the semantics and error checking procedures, and promising to edit their rust API if the C code changes, but I suspect they didn’t ask for that because they know that no guarantees come from a comment and they want to be sure that the rust code works across all the possible scenarios and in rust culture, that is always documented in the type system where it can be enforced.

The rust guys spoke like it was self evident that having a monolithic API with a bunch of stuff guaranteed by the rust compiler was best, but seem not to have realised that this is a massive culture clash because the C guys come from a culture of rejecting the idea of compiler guarantees anyway (because they have long had confidence in their ability to hand optimize their code to be faster than some prescriptive compiler’s output and look down on people who choose to have the guardrails up).

They felt like they were being asked to help write an interface definition in a monolithic style that they have always rejected, to achieve goals that they have long resisted, in a language that they find alien, with no guarantees for them that the rust guys were going to stick around to agree and implement the rust changes necessary if they changed the C code, and with no confidence that they understood what would count as a breaking change at the rust level.

This perceived straightjacket made them particularly cross. They complained about the inability to change their C code and its semantics and the need to learn enough rust to understand quickly what not to change, but they didn’t want to not change things and would need to edit the rust API at the same time as editing the C code if they didn’t want the rust build to break, and then there would be even more downstream changes from that, so realistically they would need not only to be able to understand the rust type signatures, they would need to be able to edit both the type signatures and the functions themselves, and basically maintain all the downstream rust, and they would want to be sure they were writing efficient rust, well aware that it took them decades to get to the level of extreme efficiency they write in pure C, a much simpler language.

The rust guys said “Just tell us what your code means so we can write our type signatures”, but the C guys didn’t want to help create for themselves a prison whose walls were of a strange and intricate design they found hard to perceive, made out of materials they didn’t have experience working with. They felt like the first guys were asking them how all the doors, windows, chimneys, air vents etc of the house that they built by hand would ever be used, so they could encase it in a stainless steel shell and make it part of a giant steel city. The C guys said “but I might want to build an extension or a wider garage!” They claimed that the C guys didn’t have to learn how to weld or manufacture steel sheets, and that their house would be much safer, but for some reason this didn’t win the C guys round to the plan, and there’s a bunch of people online calling the C guys tech luddites for not liking the whole thing and saying that they were incorrect that they needed to learn rust just because the rust guys made that claim, but that claim is actually completely incorrect unless you think that it’s OK to stop the project compiling with your pull request or you think that changes to the C code should be banned wherever a rust API is built on top of it.

I saw the clip previously. The rust guys are absolutely assuming that the C guys would go for something because (a) the compiler guarantees it’s memory safe (b) the semantics would be encoded in the type system. They demonstrate this using rust terminology and algebraic data types. Algebraic data types are the bees knees, (but not with that syntax and clumsiness), and compiler guarantees are the bees knees, but that’s not how a C programmer who’s middle aged sees the world, it just isn’t. Your typical middle aged C programmer grew up telling pascal programmers that automatic array bounds checking is for wimps and real men use pointer arithmetic and their programs run five times as fast. They were always right because their programs did really run significantly faster, but now rust comes along and its fast and safe. Why wouldn’t C programmers like it? Because the speed was the excuse and the lack of guardrails was the real reason they liked C.

I said it’s a massive culture clash that the rust folks didn’t realise they were having because they just assume that “memory safe” wins people round, whereas C folks value their freedom from automatic compiler-based safety, and here you are, sounding like a rust person, saying it isn’t a culture clash at all and that the rust folks are right about memory safety and the C folks are just being irresponsible.

Expecting C programmers to like a compiler-based approach to memory safety is like expecting petrolheads to like a car purely because it’s electric. They have always viewed compiler based memory safety techniques as guard rails for novices. In their view, good bowlers don’t need guard rails at the bowling alley. It’s a massive massive clash of cultures and the rust folks come into the discussion with an assumption that C devs would leap with joy at the chance to automate memory management. Rust and C are complete opposites, but rust programmers seem to assume that just because rust is fast C programmers will love it.

I take that as a compelling recommendation for Signal.

Google never had any intention whatsoever of prioritising your privacy over their advertising revenue. This technology was 100% designed to shut other operators out of the tracking and advertising market and 0% to reduce their ability to track you and advertise to you. Never in a million years were they going to spend a lot of time, effort and money destroying the source of their money. Hobble competitors, yes. Hobble themselves? Never. Not even a little bit.

Bad headline, it’s just split into three sections now:

will be asked to answer why they want to study the course or subject, how their studies or qualifications helped them to prepare for the course and what experiences they have had outside of education that will be helpful

The cheapest form of energy just got the green light. This will do a lot of good further down the line.