An anonymous reader quotes a report from TechCrunch: A study by the Pew Research Center found that Americans' views of Elon Musk and Mark Zuckerberg skew more negative than positive. While Zuckerberg has sparked chatter in Silicon Valley with his sudden interest in high fashion, the Meta CEO is less popular than President Trump's right-hand man, Elon Musk, the report found. While about 54% of U.S. adults say they have an unfavorable view of Musk, 67% feel negatively toward Zuckerberg. [...] But Zuckerberg, the Facebook founder, is more universally disliked, though he draws more ire from the left-leaning demographic. While 60% of Republican and Republican-leaning respondents hold an unfavorable view of Zuckerberg, 76% of their Democratic counterparts share that sentiment.

So, while Zuck may be playing the part of the cool guy, Americans haven't been fooled by his gold chains or musical ambitions, it seems. Pew's study involved a panel of 5,086 randomly selected U.S. adults. The survey was conducted from January 27, 2025, through February 2, 2025, so these responses reflect people's recent opinions.

[ Read more of this story ]( https://tech.slashdot.org/story/25/02/22/0048209/mark-zuckerbergs-makeover-didnt-make-people-like-him-study-shows?utm_source=atom1.0moreanon&utm_medium=feed ) at Slashdot.

The U.S. Space Force released the first-ever public image of its secretive X-37B space plane in orbit, captured during its ongoing seventh mission that launched on December 28, 2023. Space.com reports: The photo, released on Thursday (Feb. 20), was taken by a camera onboard the X-37B while the secretive space plane orbited high above the African continent. One of the plane's solar panels is visible on the left side of the photo, while what appears to be its open payload bay is visible along the top edge. The vehicle has been in orbit for well over a year now, having launched on its seventh mission on Dec. 28, 2023 atop a SpaceX Falcon Heavy rocket.

And now, the X-37B has notched another milestone with the Space Force's release of this photo, the first-ever image of this space plane in orbit that has been shown to the public. While the photo contains scant details about the vehicle and what it's currently testing, it offers a look at Earth far in the background, revealing just how high the vehicle is flying on its seventh mission. We've gotten only one other glimpse at the X-37B in orbit prior to this. During the livestream of its most recent launch, a brief shot of the spacecraft deploying from Falcon Heavy's upper stage was seen while its service module was still attached.

[ Read more of this story ]( https://science.slashdot.org/story/25/02/22/0056236/first-look-at-secretive-x-37b-space-plane-in-orbit?utm_source=atom1.0moreanon&utm_medium=feed ) at Slashdot.

Scientists have discovered evidence of ancient, shallow lakes on Mars that once had liquid water exposed to the atmosphere, challenging previous theories that all Martian water was covered in ice. Live Science reports: The patterns, which were photographed by NASA's Curiosity rover, are known as wave ripples -- minute ridge-like structures that form along the shores of lakebeds. This means that exposed liquid water must have flowed across Mars' surface at some point in its history. The ripples were present in two separate lakebeds in Gale Crater, which Curiosity has been exploring since Aug. 2012. "The shape of the ripples could only have been formed under water that was open to the atmosphere and acted upon by wind," study first author Claire Mondro, a sedimentologist at CalTech, said in a statement.

The researchers also analyzed the height and spacing of the ripple waves to determine the size of the lake that formed them. The structures are approximately 0.2 inches (6 millimeters) tall and about 1.6 to 2 inches (4 to 5 centimeters) apart, indicating they were left by small waves. Based on these dimensions, the researchers believe the Martian lake must have been less than 2 meters (6.5 feet) deep. Both dry lakebeds appear to have formed around 3.7 billion years ago, indicating that Mars had an atmosphere dense and warm enough to support liquid water for longer than previously thought -- which could have intriguing implications. "Extending the length of time that liquid water was present extends the possibilities for microbial habitability later into Mars's history," Mondro said. In other words: living organisms may have had a longer window in which they could have evolved on the Red Planet. The findings have been published in the journal Science Advances.

[ Read more of this story ]( https://science.slashdot.org/story/25/02/22/013239/nasa-rover-discovers-liquid-water-ripples-carved-into-mars-rock?utm_source=atom1.0moreanon&utm_medium=feed ) at Slashdot.

Microsoft's newly announced Muse AI model for game development has triggered immediate backlash from industry professionals. "Fuck this shit," responded David Goldfarb, founder of The Outsiders, arguing that such AI tools primarily serve to "reduce capital expenditure" while devaluing developers' collective artistic contributions.

Multiple developers told Wired that the tool is aimed at shareholders rather than actual developers. "Nobody will want this. They don't CARE that nobody will want this," one AAA developer said, noting that internal criticism remains muted due to job security concerns amid industry-wide layoffs.

The resistance comes as developers increasingly view AI initiatives as threats to job security rather than helpful tools. One anonymous developer called it "gross" that they needed to remain unnamed while criticizing Muse, as their studio still depends on potential Game Pass deals with Microsoft. Even in prototyping, where Microsoft sees AI potential, Creative Assembly's Marc Burrage warns that automated shortcuts could undermine crucial learning experiences in game development.

[ Read more of this story ]( https://games.slashdot.org/story/25/02/22/0244244/game-developers-revolt-against-microsofts-new-ai-gaming-tool?utm_source=atom1.0moreanon&utm_medium=feed ) at Slashdot.

Linus Torvalds responded Thursday to kernel developer Christoph Hellwig, who had claimed Torvalds merged Rust code into the kernel even over his objections as the original C code's maintainer. Highlights from Torvalds' response:

The fact is, the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL. It was literally just another user of it, in a completely separate subdirectory, that didn't change the code you maintain in _any_ way, shape, or form... Honestly, what you have been doing is basically saying "as a DMA maintainer I control what the DMA code is used for".

And that is not how *any* of this works. What's next? Saying that particular drivers can't do DMA, because you don't like that device, and as a DMA maintainer you control who can use the DMA code? That's _literally_ exactly what you are trying to do with the Rust code. You are saying that you disagree with Rust — which is fine, nobody has ever required you to write or read Rust code. But then you take that stance to mean that the Rust code cannot even use or interface to code you maintain...

You don't have to like Rust. You don't have to care about it. That's been made clear pretty much from the very beginning, that nobody is forced to suddenly have to learn a new language, and that people who want to work purely on the C side can very much continue to do so. So to get back to the very core of your statement:

"The document claims no subsystem is forced to take Rust"

that is very much true. You are not forced to take any Rust code, or care about any Rust code in the DMA code. You can ignore it...

You can't have it both ways. You can't say "I want to have nothing to do with Rust", and then in the very next sentence say "And that means that the Rust code that I will ignore cannot use the C interfaces I maintain".... So when you change the C interfaces, the Rust people will have to deal with the fallout, and will have to fix the Rust bindings. That's kind of the promise here: there's that "wall of protection" around C developers that don't want to deal with Rust issues in the promise that they don't *have* to deal with Rust.

But that "wall of protection" basically goes both ways. If you don't want to deal with the Rust code, you get no *say* on the Rust code. Put another way: the "nobody is forced to deal with Rust" does not imply "everybody is allowed to veto any Rust code".

Torvalds also made sure to add some kind remarks, including "I respect you technically, and I like working with you."

[ Read more of this story ]( https://linux.slashdot.org/story/25/02/22/0524210/torvalds-rust-kernel-code-isnt-forced-in-over-maintainers-objections?utm_source=atom1.0moreanon&utm_medium=feed ) at Slashdot.