"Let scaling-aware Xwayland clients scale themselves..." merged in Gnome
Let scaling-aware Xwayland clients scale themselves with "scale-monitor-framebuffers" (!3567) · Merge requests · GNOME / mutter · GitLab
Based on this branch from Jonas Ådahl, main commit: Apply custom scaling to...GitLab
like this
The coolest new space pictures: August 2024
The coolest new space pictures: August 2024
The Juice spacecraft accomplished a historic “double” gravity assist and took photos to prove it.The Planetary Society
like this
Researchers Map 50,000 of DNA’s Mysterious ‘Knots’ in the Human Genome
like this
I've spent a good amount of time studying various DNA processes and never once made a connection between i-motifs and clippy. Great catch! lol
The thing is, our cells create these "knots" to make room for enzymes to access our DNA. They're quite common as it's required for DNA transcription + replication, chromosome segregation in cell division, telomere maintenance, and to alter gene expression. Not sure how I overlooked what happens if they form more often than intended. Wild to learn it can lead to cancer, neurodegeneration, and heart disorders! Guess I missed two massive aspects when studying all this, the imapct of DNA forming i-motifs too often, and the resemblance to clippy hahaha.
Come venivano dal regime fascista strumentalizzati i fumetti...
Grottesco anche il caso di Dick Fulmine, di matita italiana, personaggio italo-americano operante dapprima negli USA, ma che nel luglio 1942 si trova nella fantasia di queste pubblicazioni non si sa come a combattere a fianco delle Forze dell'Asse.
Aggiungo una copertina, quella di "Albo dell'Intrepido" del 23 maggio 1942, perché nella nuova versione degli anni '50 era uno dei miei giornalini preferiti.
Alcuni fumetti continuarono ad essere pubblicati, altri vennero recuperati dopo le censure del fascismo, nuovi ne emersero, più di settant'anni fa...
LWN report about the "Rust for filesystems" session which a Rust for Linux maintainer referred to for context when retiring from the project this week
Their resignation is already being discussed in another post here from yesterday: One Of The Rust Linux Kernel Maintainers Steps Down - Cites "Nontechnical Nonsense"
...but I think this LWN reporting (from back in June) deserves its own post as it makes it easier for those of us who are not kernel hackers to follow what is going on.
reshared this
like this
like this
It's an interesting read to see how Kernel developers argue and think.
It's an important goal to adjust to how kernel devs discuss kernel issues.
Please don't trivialize the efforts of a smart person in a very underestimated discipline.
It's an interesting read to see how Kernel developers argue and think.
You sound like some mad scientist experimenting with kernel devs.
Large organizations always have politics—it's human nature. 1700 people is quite a large organization. Therefore, the kernel maintainers have politics. The presence of politics always means that some people will get stomped on unfairly.
This is all business as usual, in other words, and it will not go away. At best, you can shift the culture of the group and the politics along with it, but that takes time and effort and people-handling.
Academics on Mastodon
Academics on Mastodon
A list of various lists consisting of academics on Mastodonacademics-on-mastodon
Elasticsearch is Open Source, Again
Elasticsearch is Open Source, Again
Elastic is adding AGPL as an open source license option to Elasticsearch alongside ELv2 and SSPL....Elastic
like this
reshared this
On Rust, Linux, developers, maintainers
On Rust, Linux, developers, maintainers
There's been a couple of mentions of Rust4Linux in the past week or two, one from Linus on the speed of engagement and one about Wedson...Dave Airlie (Blogger)
like this
reshared this
Talks about different developer styles, slightly interesting and not too long winded I guess, but not much about the actual situation.
I think this is still not such a great look for Rust. I had expected interfacing Rust to C to present fewer problems than it seems to. I had hoped the Rust compiler could produce object code with almost no runtime dependencies, the way C compilers can. So integrating Rust code into the kernel should be fairly painless from the C side, if things were as one would hope.
It does sound to me in the earlier post that there was some toxicity going on. Maybe it had something to do with the context being a DRM driver.
I looked at a few Rust tutorials but they seemed to take forever to get to any interesting parts. I will keep looking.
like this
Your point about it being a culture issue is spot on. Many maintainers who are established in the kernel have made it clear they'd rather keep the status quo and the comfort of stagnation rather than bring a new technology forward to improve the security of their systems.
If it wasn't Rust, but some other language with similar benefits, the same people would've thrown their hands in the air and complained that they're being forced to rewrite everything or some other hyperbole.
Because it's a FOSS project, for some reason it's acceptable for maintainers to be entitled arseholes who abuse anyone they personally have a vendetta against.
In any other workplace, this behaviour wouldn't be called "nontechnical concerns" it would be called workplace bullying. And as much as Linus wants to say he's working on his anger issues, he is personally one of the contributors who has set this culture of aggression and politicking as much as any other.
LLMs produce racist output when prompted in African American English
LLMs produce racist output when prompted in African American English
Large language models exhibit racial prejudices on the basis of dialect.Talat, Zeerak
like this
like this
Everyone saying llms are bad or just somehow inherently racist are missing the point of this. LLMs for all there flaws do show a reflection of language and how it's used. It wouldnt be saying black people are dumb if it wasn't statistically the most likely thing for a person to say on the internet. In this sense they are very useful tools to understand the implicit biases of society.
The example given is good in that it's probably also how an average person would respond to the given prompts. Your average person who is implicitly racist when asked "the black man is" would probably understand they can't say violent or dumb, but if you rephrase it to people who sound black then you will probably get them to reveal more of their biases. If your able to get around a person's superego you can get a sense of their true biases, it's just easier to get around LLMs "superego" of no-no words and fine tuning counter biases with things like hacking and prompt engineering. The id underneath is the same racist drive to dominate that is currently fueling the maga / fascist movement.
Rocket launch discovers long-sought global electric field on Earth
Rocket launch discovers long-sought global electric field on Earth - British Antarctic Survey
An international team of scientists, including a researcher from British Antarctic Survey (BAS) has, for the first time, successfully measured a planet-wide electric field thought to be as fundamental to …British Antarctic Survey
like this
“
On May 11, 2022, Endurance launched and reached an altitude of 477.23 miles (768.03 kilometers), splashing down 19 minutes later in the Greenland Sea. Across the 322-mile altitude range where it collected data, Endurance measured a change in electric potential of only 0.55 volts.
“A half a volt is almost nothing — it’s only about as strong as a watch battery,” Collinson said. “But that’s just the right amount to explain the polar wind.”
”
like this
Possibly linux
in reply to Leaflet • • •setVeryLoud(true);
in reply to Possibly linux • • •TheGrandNagus
in reply to Leaflet • • •setVeryLoud(true);
Unknown parent • • •You're talking about extensions.
Extensions that don't come from GNOME are not supported at all, they've made that clear. If they wanted to, they could just stop allowing third party extensions altogether.
This is because they hook directly into GNOME Shell's' internal JS, which changes every release as they refactor it for performance or feature changes. Developers have a few months before release to adjust their extensions for the newer version.
Personally, I just raw dog vanilla GNOME for stability, and it works fine.
Semperverus
in reply to Leaflet • • •We've had this on KDE for a year or two now, and it's mostly been great.
It won't mean no more blurry apps unfortunately, but games will render at the correct resolution and some xwayland apps will look a lot better.