computers

27 May 2026

Slashdot

Nvidia To Spend $150 Billion a Year In Taiwan

Nvidia CEO Jensen Huang says the company plans to spend around $150 billion a year in Taiwan, calling it the "epicenter of the AI revolution." "Four years ago, five years ago, Nvidia was spending about $10, $15 billion dollars a year in Taiwan. Now we're spending $100, going to $150 billion dollars in Taiwan each year," Huang said. Reuters reports: Huang was speaking at a launch celebration in Taipei for the chip company's planned Taiwan headquarters, which he said will break ground this year and aims to become operational in 2030. He did not provide a timeframe for the number of years the company plans to invest $150 billion. The Taiwan headquarters will bring Nvidia closer to TSMC, the world's largest contract chipmaker which makes many of the advanced semiconductors powering the trend towards AI and is a major supplier to the U.S. tech company. "Taiwan is booming," Huang said on stage at the celebration which was attended by his parents, wife, daughter and son in addition to around 1,000 employees. "Taiwan is the epicentre of the AI revolution. This is where the chips come, packaging comes, this is where the systems are made, this is where AI supercomputers were created. The number of partners we work with here in Taiwan, incredible."

Rust Will Save Linux From AI, Says Greg Kroah-Hartman

Linux stable kernel maintainer Greg Kroah-Hartman says Rust can help Linux deal with a flood of AI-discovered security bugs (namely Dirty Frag, Copy Fail, and Fragnesia) by preventing common C mistakes around memory, locking, error handling, and untrusted data at build time rather than during human review. It's "not a silver bullet" and does not mean rewriting the whole kernel, but he said new drivers and subsystems will increasingly use Rust as Linux evolves forward. ZDNet reports: Kroah-Hartman illustrated those pitfalls with real C bugs in the kernel, including a 15-year-old Bluetooth bug that dereferenced a pointer without checking it and a Xen bug where "we forgot to unlock" in an error path. "The majority of the bugs in the kernel are this tiny, minor stuff," he explained. "Error conditions aren't checked, locks aren't forgotten, unreleased memories leak, and vulnerabilities add up over time. They crash the kernel. This is what we live with in C. This is why we don't like it." Kroah-Hartman argued that the "best beauty of Rust" is catching those mistakes at build time rather than in review. For example, when it comes to locking, he highlighted Rust's locking abstractions in the kernel: "The only way you can get access to inner pointers of structures is by grabbing that lock, and releasing the lock automatically. The compiler does it, it's guarded, the lock happens, everything's happy. You just can't write code to access these values...without grabbing the lock. The compiler will not let you." Those properties, he argued, directly remove a huge fraction of the bugs he sees: "This is going to save us those two things. First, 60% of the bugs in the kernel right there, they're gone. Thank you." The payoff is earlier, more automated enforcement: "If this happens at build time, not review time, don't make me a maintainer who has to read your code [and] say, 'Oh, then you properly check that error value. Oh, did you properly grab the locks in the right spot?' Rust gives us that for free. This is the best thing ever." Even if Rust vanished tomorrow, Kroah-Hartman argued, it has already forced the kernel to clean up C code and interfaces. He credited Rust's influence outright: "We stole this from Rust. Thank you. It's a good idea, so if Rust disappeared tomorrow, we have cleaned up the C code in the kernel so much and taken in the ideas. We thank you, you've made Linux better with it just by existing." [...] What ultimately sold a number of core maintainers, including him, on Rust was how it "makes reviewing code easier." With CI [Continuous Integration] bots enforcing builds and Rust's type system enforcing key invariants, maintainers can "focus on the logic" rather than resource bookkeeping: "I can care about that one function. I don't have to worry about the rest of this stuff, because I assume that it works properly, because it was built properly." Internally, he said, the top maintainers have already made their call on Rust's status: "The Linux kernel maintainers, we get together every year and talk about what the processes are doing. Last year, we said the Rust experiment is over. It's not an experiment. This is for real." The rationale: "The people behind it are real. We trust them. We know what they're doing. They've shown and put in the work to make Rust a viable language in the kernel, and we're going to make this stick. Let's go full speed ahead. And, as always," he said wryly, "world domination proceeds." "If you never remember anything else in my talk, just remember these four words. It came from Microsoft Security many, many years ago," Kroah-Hartman told attendees. "They realized all input is evil. You have to validate all input."

Ars Technica

Websites have a new way to spy on visitors: analyzing their SSD activity

Telltale SSD activity can be measured in the browser using simple JavaScript.

27 May 2026 8:56pm GMT

Mystery GPS jammer in Iran becomes test for NASA satellites’ capabilities

NASA science satellites show dual use in locating sources of GPS interference.

27 May 2026 8:43pm GMT

Mina the Hollower is the best old-school action adventure I've played in a while

Smooth movement, compelling combat, and tons of secrets make for an innovative throwback.

27 May 2026 8:22pm GMT

Slashdot

The AI Fight Brewing Inside the New York Times

An anonymous reader quotes a report from The Verge: How newsrooms should use AI -- or if they should at all -- has been a recurrent debate within the media industry over the last several years. Increasingly, these rules are being hammered out at the bargaining table between unions and publishers. Right now, employees at The New York Times are gearing up for a fight. Unionized staff with the Tech Guild say Times management has refused to provide the union with information related to how the company has used AI, its plans for AI use in the future, and how it will affect employees' jobs and workflow. (The union filed an unfair labor practice charge earlier this month.) The Tech Guild, a NewsGuild of New York unit of around 700 software engineers, designers, product and project managers, and data analysts, also filed grievances saying Times management violated their collective bargaining agreement when it started using two internal AI tools that track and evaluate employee performance and activity. [...] Both the Tech Guild and the Times Guild (which represents 1,500 editorial, ad sales, and support staff at the Times) filed unfair labor practice charges against the Times, saying that company violated labor law by refusing to respond to their requests for information around AI use at the outlet. The Times did not respond to specific questions about how it uses DX and Glean, but spokesperson Danielle Rhoades Ha said in an email that the company disagrees with the characterizations made in grievances and that it would respond as part of its "normal contractual process." "Likewise, we will respond to this Request for Information (RFI) in due course as we've done with 80+ other RFIs from the Guild in recent years," Rhoades Ha said. The Times Guild is currently bargaining a new contract, pushing for robust protections against AI, like requirements that a human is behind any AI tool being used, that any journalism utilizing AI is transparently labeled, and that staff are compensated for AI model training deals the company might make. The Times deploys artificial intelligence tools for some reporting, like using it to parse millions of documents related to Jeffrey Epstein or scan satellite images of Gaza to try to find where Israel had dropped a specific kind of bomb. [...] [Ben Harnett, a software engineer at the Times and chair of the unit's generative AI committee] emphasizes that the unit's position is not that AI shouldn't ever be used, but that workers should have a say in how it's deployed. Metrics like how many tokens an employee uses or how often they're using AI to do their jobs create pressure to do more and incentives that don't align with doing quality work. "It's going to distract [you] from actually doing a good job, which is what we think the company should want," he says. Two of the contentious AI tools mentioned in the report are DX and Glean. DX is an engineering productivity tool that tracks a developer's output, generative AI use, efficiency, and other related metrics. Meanwhile, Glean is an internal knowledge-search tool that indexes materials like wikis, GitHub documents, Google Docs, and emails so employees can query company information. The concern, according to Times Tech Guild members, is that data meant to measure broader developer experience is now being applied to individuals and cited in performance or disciplinary contexts. There's also worry that it could be used to monitor individual contributions and produce false or misleading results.

OSnews

Microsoft tries to obscure “AI” features behind flowery design language

Now that my one-month sentence of using Windows 11 has begun (you can follow along!), I'm also a bit more perceptive of news and developments regardingMicrosoft's latest and greatest operating system version. Despite claims to the contrary, we already know the company isn't really removing "AI" features from Windows, merely renaming them instead, but it turns out they're planning something more all encompassing: the Copilot Design System. Long-time Microsoft veteran Jon Friedman published a blog post introducing this new concept. As Copilot steadily evolves into a thought partner-an intelligent presence woven into your workflow-its backbone will become the Copilot Design System, an AI-forward design system we're crafting to feel intentional and humane. From orchestration patterns to iconography, the experience we're building will ultimately have components that work together to amplify thinking, guide decisions, and unlock creativity-seamlessly, wherever you work. Anchored in customer feedback around creating better experiences, a fundamental question guides our system's evolution: how would a thoughtful partner look and behave? ↫ Jon Friedman at Microsoft's design blog I've read the whole post and I still have no idea what most of it is supposed to mean in practice. It feels like the written equivalent of someone trying to put lipstick on a pig, and pretty much anyone is going to see right through the fancy words and phrases and realise what we're really dealing with here: a company trying to figure out just how far they can shove "AI" down your throat before you gag reflex kicks in. You can hide behind flowery language all you want, but if you're selling shit, it's going to stink regardless. The only concrete user interface idea that's come out of this Copilot Design System was a floating Copilot button that permanently floated on top of your workspace area in Word, Excel, and so on, obscuring the actual things you were working on. Users hated it so much that Microsoft had to quickly release what is essentially a hotfix to give people the ability to remove that floating button, putting it in a toolbar instead. Like I said: people see right through these thinly-veiled attempts at baiting them into using your pachinko machine. Anyway, yes, I'm working from Windows 11 now, just as you people paid me to do. Here's the proof: Only 30 days left to go. I can do this.

27 May 2026 6:45pm GMT

26 May 2026

OSnews

Sailfish OS reviews are always the same

João Carrasqueira at XDA Developers has taken a look at the current state of Sailfish OS, and concludes: As an idea, I love Sailfish OS. Not only does it bring a wholly unique interface to mobile devices at a time when things seem more unified than ever, but it also has the potential to bring the full power of Linux to a smartphone you actually want to use. But the lack of apps makes it hard for it to become anyone's daily driver, and the power of Linux is somewhat hampered because it relies on dedicated repositories that, again, don't get much support. The community as a whole would benefit if the UI for Sailfish OS could also be open-sourced and made available as a desktop environment other distros could adopt. I can see a world where many more Linux distros might be ported to mobile devices using this UI, and leading to more apps being ported to the platform as well. It's unlikely, but taking that step could make a big difference. ↫ João Carrasqueira It seems like Sailfish OS, much like any other mobile operating system that isn't Android or iOS, is still stuck in application hell, where they've always been. Windows Phone, BlackBerry 10, postmarketOS, Sailfish OS - they all suffer from the fact that the services and associated applications people actually need to use in their day-to-day life just simply aren't there, and never will be unless something utterly drastic happens. You're pretty much forced to fall back on possible Android application compatibility layers, at which point you're basically just running Android in an worse way. As an extremely early customer of the original Jolla Phone, and owner of the very rare Jolla Tablet, I considered if I should add the new Jolla Phone as an incentive for the current fundraiser, but I decided against it because I already know what the review is going to be like. Interesting user interface, very limited set of often buggy native applications, constant reliance on often buggy Android compatibility layer, €750 is a lot of money for a barely mid-range phone. Oh, and the UI layer is closed source. I don't need an expensive phone I won't use after the review period to write any of that. There's very little new to write about or discover when it comes to mobile operating systems other than Android and iOS, and that's not through the fault of the people developing these platforms. All the smart developers working on postmarketOS, Salfish, Ubuntu Touch, and others are doing a great job and the very best they can, but in the end these platforms are limited by the fact that the services we all depend on just do not work on any of them. I don't have the solution for the problem - other than very heavy-handed regulation to demand open APIs, which I support but will never happen - so the status quo will remain as it is. It's a sad state of affairs when even Google-free Android is almost a non-starter at this point.

26 May 2026 10:13pm GMT

25 May 2026

OSnews

The Nokia N8 has a brand new, modern, actively maintained, and regularly updated Symbian ROM

I have a Nokia N8, and it's one of my favourite retro (?) devices I own. It was one of Nokia's last efforts to make Symbian happen in the post-iPhone era, and while the hardware was quite nice, Symbian just wasn't made for multitouch devices. It didn't move the needle much for an already dying Nokia, and things just got worse from there. A bright spot with the Nokia N9, some decent Windows Phone devices, and then the end. We all know the story. The Nokia N8, though, seems to have been given a new lease on life recently. This smartphone, released in 2010, can be turned into a usable, capable device again, thanks to a brand new, modern custom Symbian ROM called Reborn. It takes the latest stock Symbian version for the N8, removes any and all applications/links/etc. that don't work anymore, and then proceeds to make a ton of things work again. Modern TLS for HTTPS support, updated certificates, modern email support, a brand new application store, a new update application with a steady stream of OTA updates to fix issues, a bunch of security fixes, a whole slew of quality-of-life touches, and so, so much more. This is absolutely amazing work. Clearly a labour of love, there's already been tons of updates over the past year since the ROM's initial release, and I obviously can't not install this on my own N8, assuming it still works. A video by Janus Cycle covering the project is also available, for the more visually-oriented among us.

25 May 2026 11:18pm GMT