I can't agree more. Linus position here is not dissimilar to CEOs and alike. He's trying to deal with R4L using his (allegedly) 100% technical and 0% political perspective but in this case it simply doesn't work. R4L is a political challange that require political discussions; who decides? what's the bar? who maintains what? etc
By not answering this questions and saying he doesn't want to have anything to do with the arguments, Linus simply decided that he doesn't want to solve the problem that only him can solve. The result is clear: R4L will fail if Linus decides that any maintainer can stop the "cancer" to spread and block Rust changes.
R4L implies that Rust will be present in the kernel and will need to be maintained. If Linus is ok with maintainers that have a deep/fundamental problem maintaining/coordinating the maintenance of Rust code, R4L will never happen.
Really solid program. I bought a license years ago because it is the only software that correctly remuxes media for direct play in Chromecast, including surround sound and HDR.
I wish Jellyfin could catch-up with the compatibility level AirFlow has to offer.
Jellyfin has slowly been getting better. Client also makes a big difference. I fought issues with Roku advertising capabilities properly before eventually hitting limits (100Mbps Ethernet) and moving to Nvidia Shield which has been working better (but still had an issue with HDR)
Exactly! And it was obviouslly written by (or with help of) a LLM. The first definition is even gramatically incorrect! Lets see what gemini thinks of the first paragraph if I force it to criticize it:
I don't see any grammatical errors, just some possible missing punctuation. The arguments Gemini gives are just opinions about stylistic choices. Could you point out the specific grammar mistakes you see?
These are just grumpy posters, while I was not expecting the post to get all of this attention, its usually the ones who are reactive or trolling who respond here. They want to find so many mistakes just so they don't have to admit to themselves that they don't understand what the project is or how it works.
Have you seen GPU prices lately (last 5 years)? A RTX 4080 super with merely 16 GB of VRAM is at least 1k, there's no way a 32 GB next gen flagship would be released at this price range.
Could not import my 10 year + google history hosting it in my raspberypi 5. The number of pending tasks was over 2 million after one day. I guess it was not optimized for large imports, sadly :(
I think SmoothLife and Lenia are great fun -- lots of highly watchable "eye candy" tends to get produced by those types of experiments. The better you get at running experiments, the more new behavior you can turn up:
https://www.youtube.com/c/Slackermanz
There's a channel on the ConwayLife Lounge on Discord called "#exotic-ca" that's devoted to these kinds of explorations. I just simply haven't had time to dig into those topics much, but if I could clone myself I'd definitely assign one copy to playing around with that kind of thing.
Awesome write-up! I wonder how much simpler and/or unnecessary some of the snippets would be by using typst.app instead of latex. The figure creation pipeline is also great, in this case a custom plugin for typst would need to be added to inkscape.
By not answering this questions and saying he doesn't want to have anything to do with the arguments, Linus simply decided that he doesn't want to solve the problem that only him can solve. The result is clear: R4L will fail if Linus decides that any maintainer can stop the "cancer" to spread and block Rust changes.
R4L implies that Rust will be present in the kernel and will need to be maintained. If Linus is ok with maintainers that have a deep/fundamental problem maintaining/coordinating the maintenance of Rust code, R4L will never happen.