Still having these issues very recently.

Given her condition it’s possible she never left hospital after her diagnosis

Read the article again. It said early on her chances were actually quite good, something like 80%

The first point is correct. The second one is shown to be wrong in the second paragraph.

The issue here is you need to have stopped 6 months or more before, and she was only diagnosed 5 months before she died.

They said it was viable in the early stages, and with a decent success rate. Just not the success rate they wanted, and for some daft reasons you need to be eligible for a full transplant from a dead patient to get a partial transplant from a living donor. Makes no sense.

Yes these people should indeed be killed for letting another human die for no good reason.

Has lesser liver performance? What? Do you understand how a living transplant works? You both regrow a full liver after the procedure, because livers are so regenerative you can make a full one from less than half. This makes no sense to me.

Also she quit for 5 months after she found out she had liver failure.

Their boyfriend was willing to be a living donor for them. So you aren’t talking about a scarce resource here.

Their boyfriend volunteered as a live donor. They weren’t asking to be put on the general register.

Wait what happens if you admit to smoking weed? I thought we had doctor patient confidentiality. I’ve had some mental issues in the past, though not to the point of self harm. What happens if I admit these? I also live in the UK and this is concerning.

That’s absurd. Refusing someone a transplant because they used to drink more than 3 drinks a week before they knew they even had liver problems is completely absurd. Calling her an alcoholic for that is even more absurd. What in the world are these people or you thinking?

I believe that’s an established procedure. Both the donor and the recipient regrow full livers from the portion they have. You can only donate once though because of how the new liver tissue is structured. I believe the arteries in the new one aren’t in the same place.

Edit: if you read the article it actually tells you her boyfriend was willing to be a live donor.

People don’t drink because it tastes good. People drink it because they like getting high and alcohol is one of the few legal drugs you can do. People who drink it because it’s the cool thing to do are being idiots.

If alcohol isn’t your thing you should probably get out there and try other drugs. The good thing about drugs is how many different kinds there are. There really is a substance for almost everyone if you look hard enough. Now if only stuff was legalized and people didn’t abuse it to the nth degree and get themselves in trouble.

Edit: also forgot to mention that brewing is probably the easiest and cheapest way to make a psychoactive substance known to man, and is an entire hobby people (such as myself) have. While lots of homebrewers spend money on fancy equipment and ingredients you don’t need to spend much at all to make alcohol that will get you drunk it can literally be done using a used plastic bottle and a fucking balloon. You can make pretty drinkable stuff with even fairly basic equipment like a hydrometer, couple of plastic or glass fermenters, yeast + nutrients ordered online, and supermarket ingredients.

I like how being able to drive a car has become the metric that decides if you are retarded or not. Like come on. Cars are killing the planet and even if they weren’t they are the most dangerous form of transport by far. Stop hyping cars.

Also you can have physical issues, coordination issues or attention issues that make driving difficult, but can still be more level headed than the average person.

That’s already being attempted in the form of Redox OS. Though I don’t think it’s 100% POSIX compliant. Linux has so much inertia though, and Linus seems all for including Rust in Linux.

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.

I could be being daft but I thought this is more or less what the Rust guys were asking for. Tell us the current symantics of the system, and if it changes in future let us know what the new semantics are and we will fix the Rust code accordingly.

I do understand what you mean though about enforcing restrictions on what the C guys can do without breaking the Rust code. I think you run into situations wherever two languages meet. The way most projects handle this is the upstream releases a new version, or a release candidate of a new version with their breaking changes documented and then downstream updates their stuff accordingly when they get time. Obviously this is one project, but I imagine it’s possible for the C guys to update stuff in a pull request and then drop an email in LKML to the Rust guys so they know stuff needs fixing. None of this seems that hard to me.

Ultimately though everything here is Linus decision. Either your in or your out. If Linus says yes to Rust doing whatever then that’s what’s going to happen. Likewise if he says no, then it’s not going to happen that way. Until he weighs in no one can really say how this will end.

Personally though I disagree with the C guys. Safety features are important and should be used where it is practical to do so. Until now C has had the justification that it’s still the fastest language and by a significant margin. Now a somewhat safe language like Rust exists with the same speed and capabilities I don’t think we can afford to continue ignoring safety for the sake of a few bruised egos. If this was a proper industry like aviation safety would always come first, and if that means adopting new technologies and forcing people to adapt. I can understand if C devs have a hard time adapting, I don’t expect it to happen overnight. The expectation though should be they should learn some Rust eventually, even if it’s just enough to know the type signatures and what not that they might break with their changes to C code. Kernel devs are supposed to be some of the smartest computer people out there. If they can’t learn even that small amount of another language then should they really still be kernel developers?

They aren’t asking C devs to write Rust code, which is what the guy being a heckler was claiming. Why don’t they want to right Rust? For exactly the reasons you describe. The thing is though that’s not currently being asked of them, all they actually want is the documentation to create that code themselves.

You really don’t have to explain any of the culture clash to me lol. I’ve written both C/C++ and Rust. My C and C++ coding skills are demonstrably better (or at least used to be, it’s been a while) than my Rust skills. Why? Because of how complex those guardrails are. The difference is I have the self awareness to know that my lack of Rust skills doesn’t mean that the language is bad, or that C is a safe language to use. Rust tutorials could be improved. Perhaps an easier to use language like Zig might be more useful for some people. I feel like it’s a good compromise between safety and ease of use. Rust though is still incredibly progressive for the industry, and will improve systems security, maintainability and reliability going forward if only people would stop getting in the way.

Netflix is using FreeBSD for servers. You can’t blame everything they do wrong as being a problem with the new hires. They are using an OS older than Linux that changes more slowly than Linux, simply because it performs the best for their specific application. Rate of change isn’t the issue here.

In fact that’s 90% of what this comment is. Blaming new people and new techniques for problems when you aren’t a part of that organisation and don’t actually know what’s happening.

Working with computers is not the same as working with construction equipment. Some degree of fluid intelligence is needed in this field, no matter how experienced you might be, just like how a surgeon needs steady hands. The people you call greybeards aren’t nearly as old as your father is. We are talking about people who are in their 50s and 40s. They don’t have that level of cognitive decline yet. Likewise some things like ext4 aren’t likely going to be ported to Rust now or even ever. They can keep maintaining them as they are now for the foreseeable future. Plus I don’t want people to have to keep working into their 70s and 80s. At some point it becomes elder abuse. Let people retire man.

C has existed for a long time now. We’ve been trying to replace it for ages, for most of it’s lifespan even. C++ actually was one of the new options at one point. I get it seemed immovable only a decade ago, and I think that has lulled people into a false sense of security. In truth it was inevitable it would have to be replaced one day. It’s already well outlived the life expectancy of a programming language. Just think about Ruby: created long after C yet has already become mostly irrelevant. You talk about the maximum rate of tool change, but C is one of the oldest tools we have, keeping it around would be almost 0 rate of tool change over decades. If you can’t see that C is very slowly dying then you haven’t seen the writing on the wall for the past several years. It’s on you at that point.

We should look back with pride at everything that has been accomplished with C, and just how long it’s been relevant. We can do this while still acknowledging it needs to be phased out gradually.

No one is asking for change that rapid either. Linux started adopting Rust four years ago now. It’s probably still going to have C code inside it for at least a decade from now. This isn’t some quick change, it’s a gradual process. People have plenty of time to adapt, and those who are too old to do so will be around retirement agent if not already dead by the time C is fully phased out.

We of course play plenty of video games together to keep him sharp. We also eat mushrooms, paper when necessary, and he works out a lot. We do all we can, believe me.

Honestly you take more care of yourself and your father than I do. I am only in my 20s and suck at video games. If I took mushies or LSD I would probably lose my mind, assuming it’s all still there in the first place. I suspect there is a good reason why people like me only have a life expectancy of 58 or so.

C has been around for a very long time. I don’t think wanting to replace a 1970s language, that was old when current gray beards were young is a bad thing. People have had more than enough time, and still have a good decade or two to make their careers writing and maintaining C code. Sometimes things have to change, old people be damned. It’s diatribes like this that remind me the human race advances one body at a time as those holding us back die out.

Edit: also we aren’t talking about people in their 70s and 80s here. Most of these “greybeards” are in their 40s and 50s at most. Linux itself is from the 1990s and is therefore more modern than C.

That might be true but it’s not what happened at that specific conference. I beg you watch the clip to see what happened. Also fuck programmers with the attitude you describe. It’s been proven wrong over and over again with so many C memory safety vulnerabilities.