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.
areyouevenreal
I find it fascinating that with AI people call out even real photos as being fake
That to me sounds like exactly the reason why developers like the above have left. They are having to take on the burden of gently letting down other devs who are angry over a simple misunderstanding. A misunderstanding that wouldn't have happened if they had been listening or bothered to ask first before jumping to conclusions. Imagine someone heckles you on stage and you have to respond kindly. I certainly wouldn't. If someone had listened to my talk, misinterpreted it, then heckled me over it you can bet I would be angry and would respond in kind. To then see this misinformation being spread again would drive me nuts. I can see why they left.
The bottom line for me is that Rust devs who work on this stuff for free shouldn't be getting hounded by C devs just for asking for proper documentation that frankly they should have provided in the first place. I say this as someone who is skeptical of Rust for various reasons.
This isn't a disagreement. One person is stating something incorrect. You can disagree on opinion, but facts are facts. The person being referred to here isn't asking others to learn Rust, they are just asking for more information about the already existing C code so that they can write their Rust code to interoperate with it. This misunderstanding is exactly why that developer was getting heckled on stage, and is the reason why now one has left the project. I would appreciate it if you didn't make a misunderstanding sound like a valid opinion. Enough damage has already been done.
That's not at all the case in my experience. Sure virtual box modules can be harder to install, but libvirt has so many issues that the average user has no idea about. I've had networking issues, display issues, and so on. At one point it read the display scaling information and scaled down the VM display instead of scaling it up. Furthermore RedHat don't even support virt manager anymore. They want you to use Cockpit. Honestly the all around best virtualization solution is probably VMWare or something like Gnome boxes or QuickEmu.
Do you know which bootloader you have? There are two popular ones in use currently, one called systemd boot, the other is called grub. From reading this post only grub seems to be affected. I don't really know which one fedora defaults to at the moment, and it likely depends on what happened during the installation process as well.
It's gotten to the point though that it actually works better on older hardware as the system can't actually fully utilise the new hardware because it's not programmed to do that. It's actually such a sad state of affairs. I don't know how the Windows devs can cope anymore. If I worked on that product I would hate my life.
What ThinkPad is this?
That explains why Nix despite being parallelized takes a long time to install packages and rebuild the configuration.
It varies a lot between different groups of feminists. There are plenty that unironically want a system where some rich women are in charge instead of just rich men. In fact I would say this is the majority of feminists as communists and anarchists aren't that common plus lots of communists are against identity politics to begin with.
However "it worked on other distro X, thus is should work on other distro Y" probably isn't a helpful way of thinking to get things working.
I am talking about the kernel here. It tells me that the device is actually supported. If something works on other distros driver wise, that means the one it doesn't work on either has an old kernel or is doing something strange.
NixOS ships a very minimal kernel and relies on you to declare what modules you want to load (or sometimes relies on nixos-generate-hardware to find some of those modules), so even if it is really standard hardware that "just works" on other distros, you still may need to dig out some kernel modules and explicitly load them.
That explains it. Still is an odd choice. The whole point of Linux being modular, and knowing how to load stuff automatically, is that shit like this isn't necessary. I can understand if this was Gentoo and we were talking about manually compiling kernels, but this is a pre compiled generic kernel. The expectation is that it just works.
Do you have a source on where to configure these kernel settings?
Still having these issues very recently.