Apple has transitioned its hardware products to the AArch64 processor architecture and is phasing out support for x64. Oracle engineers will thus stop maintaining the macOS/x64 port as of JDK 27. Maintaining the port is a significant burden. ↫ JEP 541: Deprecate the macOS/x64 Port for Removal The port won’t yet be removed, but will be in a future release. Considering the number of Intel Macs that must surely still be in use today, this does seem a little premature to me.

That is the first line of the 80s microcomputer BASIC game The Wizard’s Castle initially written for the Exidy Sorcerer platform. It’s a REMark statement, a comment in that particular language. 10 is the line number, if you’re unfamiliar with languages that had such things. But the interesting part was this "_(C2SLFF4 mess. A typo or garbage? No. It appears verbatim in the source code as originally published in the July, 1980 issue of Recreational Computing. What the heck is it? ↫ Brian “Beej” Hall A fun investigation to brighten up your Monday.

Given that Android phones have been around for nearly two decades now, there comes a time when Google has to end support for one of its older software versions. For a couple of years now, Google Play services has been supported on devices running Android 6.0 Marshmallow or newer. That has changed over the past few weeks, with Google deciding to retire this software version after a nearly 11-year run. ↫ Chethan Rao at Android Authority At some point, an operating system version needs to be left behind – and I don’t think it’s entirely unreasonable to no longer support Google Play Services on an operating system version that’s 11 years old. However, this is Android we’re talking about, and devices running Android 6.0 were probably sold much more recently than 11 years ago, when the operating system version was new. Hell, I wouldn’t be surprised if devices running Android 6.0 are still being sold today. I doubt this is something that will affect many people who read OSNews, but there’s bound to be edge cases – Android 6.0 devices silently doing their job that are now just a little less useful. I’m thinking of really cheap tablets that can still play video just fine, retro gaming handhelds that don’t magically lose the ability to emulate SNES games, that sort of stuff. The numbers will be small, but if you happen to be among them, this can be a really annoying deprecation.

A rather unusual announcement was made late last night: the FreeBSD project has frozen their ports repository. For more than 48 hours now, no changes have been accepted or made to the tree, and here’s why. A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the ports tree in order to implement some clean up efforts. The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history. ↫ Kyle Evans in freebsd-announce While FreeBSD’s ports tree is not hosted by GitHub – it’s merely mirrored there – the FreeBSD team believes the community values the GitHub mirror too much, and as such, steps had to be taken to fix this. Ports has not been compromised and users’ systems do not appear to be at risk in any way due to this occurrence, which is good news. Curiously, the official announcement makes no mention of which 150MB file, exactly, was committed to ports, but it didn’t take for people long to pinpoint the offending commit (screenshot). It turns out someone committed the entire github-copilot-cli Linux binary to ports, as part of the github-copilot-cli port. This FreeBSD port is effectively a way to easily install and run this tool on FreeBSD using Linuxulator, FreeBSD’s Linux compatibility layer that allows you to run unmodified Linux binaries on FreeBSD. It’s important to note this FreeBSD port is not actually a port of the Linux version of github-copilot-cli to FreeBSD; the FreeBSD “port” merely acts as a setup script to run the unmodified Linux binary using Linuxulator. It’s not a “real” port because the tool isn’t open source and its license doesn’t allow for modifications. That’s why the announcement specifically mentions “questionable licensing” – github-copilot-cli is licensed under some custom license specifically made for this tool, and is not open source. Anyway, for whatever reason, the maintainer of this FreeBSD port accidentally made a commit that added the actual, full 150MB Linux binary to FreeBSD ports. I’m assuming that under normal circumstances, building and installing the github-copilot-cli FreeBSD port would merely download the binary off GitHub and set Linuxulator up so that it could run it. Mistakes happen, and since there’s clearly nothing malicious going on, there’s not much to worry about. In fact, this may lead to new checks and balances to prevent this from happening in the future, which would be good news. The FreeBSD team is working on rolling back, fixing the issue, and investigating how this could have happened. Ports is still frozen at the time of writing, but I’m sure we’ll have a more detailed account soon.

This post is about the evolution of Futhark’s type checker, motivated by a large refactoring I am about to merge. It is probably mostly of interest to other language designers, and contains some lessons I wish I had known when we first got started – although I am not particularly well-read in the type checking literature, so it’s possible all of this is old hat. ↫ The Futhark Programming Language blog That’s a clear introduction – you know what to expect.

Honestly, it feels like only yesterday that System76, Linux OEM and the company behind pop!_OS, announced it was going to develop its own desktop environment, COSMIC. We’re about seven months into the more general availability of COSMIC, and the company has put up a nice overview of the various improvements that have already made their way into the code since then. Of course, there’s a ton of visual improvements have been made to COSMIC, as well as a slew of new features: improved search, a brand new system monitor, drag and drop for tabs throughout COSMIC, and much more. COSMIC’s file manager and terminal have also seen a lot of work, with a ton of new small features and additions to bring them up to par with what people expect form a modern file manager and terminal emulator. There’s a ton more listed in the article, so it serves as a nice “while you were away” if you’ve not been following development.

If you want to develop an application for AmigaOS 3.x but don’t want to deal with real hardware, virtualisation and emulation are your friends. Apropos of nothing, I decided to set up an Amiga development environment. Since figuring things out wasn’t straightforward, I wrote down instructions for Linux about how to compile the first program and run it in an emulator. Enjoy! ↫ Daniel Kochmański It’s a great guide, easy to follow, and you’ll be up and running quickly. The emulator the guide uses – AmiBerry, a fork of WinUAE – contains slopcode, so you may want to consider alternatives. This doesn’t change much for the guide though, as whatever tasks you need to do outside and inside AmigaOS itself remain unchanged.

Drivers of cars from the Volkswagen Group using alternative Android versions like GrapheneOS, LineageOS, or /e/OS have been unable to use the VW app for some time. This means they can neither check their vehicle’s remaining range from their phone, schedule service appointments, nor control charging and air conditioning. The car manufacturer has made changes to the app’s backend that only allow devices with Google’s pre-installed Play Services. When asked by heise online, VW stated that affected users should not expect a timely reopening. “However, they are looking into it.” ↫ Andreas Floemer at Heise.de Clearly, this should be illegal. Then again, that has never stopped Volkswagen before.

One of the cool features of JPEG files is that there’s the option to save low frequency components first. This means that a partially downloaded image will be displayed at low resolution instead of being cut off. ↫ maurycyz.com Oh I know where this is going… Doing this, I can get Chrome to render around 90 frames before giving up. Other browsers like Firefox have more patience, but a 90 scan image seems to work almost everywhere. ↫ maurycyz.com Yes, you can abuse the mentioned feature to create a really odd type of video. Or animation? Well, it allows you to create something resembling a really low-resolution GIF. Useless, yes, but very novel.

The Verge reviewed the latest Surface Laptop, which only comes with 8GB of RAM at a higher price than the previous 16GB model, and they conclude that Windows isn’t really usable on 8GB of RAM. Whether that’s true or not I do not know – I would assume it depends a lot on your usage – but this quote from the review I found quite peculiar: I was on a Microsoft Teams call (using the app, not a browser) when the host streamed a brief video, which made the whole laptop hang for several seconds. At the time, I had about 10 Chrome tabs open across two desktops, alongside Slack and Signal — not an obscene level of multitasking. ↫ Antonio G. Di Benedetto at The Verge Excuse me, but that is actually an obscene level of multitasking because every single one of those “applications” is a complete Chrome browser. Just in the paragraph above, there’s four individual complete Chrome browsers running, with little to no optimisation. Why would anyone be surprised this scenario strains a mere 8GB of RAM? This isn’t merely a Windows problem; this is a programmers choosing suboptimal tooling × managers have no idea what they’re doing problem. If Teams, Slack, and Signal had been proper, native applications instead of websites running in terrible frameworks, Windows 11 would have handled this scenario just fine.

Speaking of OpenVMS and Alpha – and we like speaking about OpenVMS and Alpha, don’t we? – there’s now a port of DOSBox that runs on the Alpha version venerable operating system. Astr0baby has published both binaries and source code for the port, as well as a lovely set of screenshots to show it off working.

Well, this is new – but not at all unexpected considering the state of Windows and the wider technology industry. When you connect certain LG monitors to a Windows machine, Windows Update will pull in a bunch of adware promoting antivirus trash. Of course, all done without any consent, because Silicon Valley inherently does not understand nor respect consent. Windows Update first installed LG extension and software component packages. Windows Reliability Monitor showed that LG Monitor App Installer appeared one minute later. The installation did not display a consent prompt or require the user to approve the download. Gamers Nexus tested the application across 32 consecutive system boots. It displayed a McAfee promotion during 31 of them. On the remaining boot, it promoted one of LG’s own monitor utilities. The McAfee popup offered a 30-day trial that would convert into a paid subscription. ↫ WhyCry at VideoCardz Don’t use Windows.

A country selector looks simple because the interface reduces geography to one field. The infrastructure behind it is harder. In regulated digital products, location can affect access, content, payments, and account actions. That is why sweepstakes casino software by NuxGame should be viewed through a systems lens: geography is not a preference, but a changing signal that software must interpret. A Country Selector Knows Almost Nothing A country selection tells a platform what a user claims, not necessarily where the current session originates. IP data can suggest a region, browser geolocation can add precision when permission is granted, and account information can provide context. None of these inputs should automatically be treated as perfect. The design problem is therefore about confidence. A platform needs rules for what happens when signals agree, conflict, or disappear. That requires a source-of-truth policy rather than another front-end field. Product teams also need to decide which actions can continue under uncertainty and which should stop until location is resolved. Location Is A Confidence Decision A useful geolocation layer asks more than “which country is this IP in?” The system has to understand how trustworthy each signal is, how recently it was collected, whether the current action requires a fresh check, and what happens when evidence conflicts across a session. Useful inputs and controls can include: More checks can improve confidence, but they also create friction and more failure states. That trade-off matters for sweepstakes casino software by NuxGame because product, compliance, support, and engineering may all depend on the result. A stricter policy reduces ambiguity while creating more cases that need explanation or review. Sessions Move Even When Accounts Do Not An account can remain unchanged while the user moves between networks or countries. Mobile devices switch from Wi-Fi to cellular connections, and VPNs can alter the apparent origin of traffic. Treating location as a permanent profile attribute therefore creates a mismatch between account state and session reality. The legal and commercial question is separate from the engineering one. Research into which countries allow iGaming can help a business understand where different models may be permitted, subject to current local rules and professional advice. Software must then translate approved market decisions into executable controls: when to check, what to restrict, and how to handle uncertainty. Caching Can Make Regional Rules Dangerous Caching is useful for static assets, localization files, images, and content metadata. It becomes more sensitive when the cached value controls whether a user can perform an action. A location decision that was valid earlier may no longer describe the current network or device context. This creates a performance-versus-authority trade-off. Rechecking everything continuously would increase requests, latency, and operational cost. Trusting an old result indefinitely is simpler but weaker. A better design defines expiration rules according to risk: some content can tolerate stale regional data, while sensitive actions may require a newer location decision. The Back Office Needs To Explain The Decision Geolocation failures are difficult to support when the system stores only “allowed” or “blocked.” Operations teams need enough context to understand which signal was used, when it was collected, whether signals conflicted, and which rule produced the outcome. Otherwise, support can only repeat what the front end says. Auditability creates another balance. More detailed logs make investigations easier, but location data can be sensitive and should not be exposed widely. Access controls, retention policies, and clear event records therefore matter as much as the geolocation engine itself. The implementation should make decisions explainable without giving every employee access to raw location data. Geolocation Belongs In Product Architecture Geolocation should not be added at the end as a country dropdown plus an IP lookup. It touches session management, permissions, caching, logging, support workflows, regional configuration, and the interface shown when access changes. Once those dependencies are visible, the architectural problem becomes much clearer. For sweepstakes casino software by NuxGame, the practical lesson is simple: location should be treated as a decision with evidence, freshness, and consequences. A dropdown can collect a preference. A production system has to decide what is true enough to act on—and remain capable of explaining that decision when the answer changes. Resources:  NuxGame Legal iGaming Markets Guide – regional iGaming market considerations;  W3C Geolocation – browser geolocation standard;  IETF RFC 8805 – IP geolocation feed format;  MDN Geolocation API – browser geolocation implementation guidance.

Linus Torvalds, the creator of the Linux kernel and git, is employed by the Linux Foundation. This Foundation is a non-profit organisation dedicated to, as the name obviously implies, the promotion of Linux. The primary use of the funds it collects is to “help fund the infrastructure and fellows, including Linus Torvalds, who help develop the Linux kernel”. The list of megacorporations donating most of the Foundation’s funds is long. The Linux Foundation has twelve platinum members, which donate $500000 per year, followed by twelve gold members, who donate $100000 per year. Below these two primary tiers lie the silver peasants, who each donate $5000-$25000 per year, based on number of employees. Looking at the list of twelve platinum members, I noticed something interesting. Of the twelve platinum companies, six are “AI” companies or companies with massive investments in “AI”: Google, Huawei, Facebook, Microsoft, Oracle, and IBM/Red Hat. Then there’s Samsung Electronics, which is raking in stupendous amounts of money thanks to the “AI” bubble. Additionally, one of the gold members is Anthropic, another major “AI” company and makers of “Claude”, the sloppiest of slopcoding tools. Many of these companies are unimaginably deep in the red when it comes to “AI”, with very little indication they’re ever going to be able to recover any of it. The situation is particularly bad for Oracle and IBM/Red Hat. Oracle’s debt has been downgraded to one notch above junk status because of its “AI” spending, while IBM’s shares experienced the largest crash in its 115 year history only a few days ago. By the way, in the first half of 2025, “AI-related capital expenditures contributed 1.1% to GDP growth, outpacing the U.S. consumer as an engine of expansion”. Fun fact: since most of The Netherlands is effectively a swamp, most of the country’s buildings are built on massive wooden or concrete poles (piles) hammered deep into the ground until they hit something more stable than mushy clay and wet sand. Otherwise, buildings in the country would simply sink into the ground. Every Dutch person who ever lived near a construction site has heard the rhythmic kathunk, kathunk, kathunk, all day long, as the massive piledriver machines spread their gospel. I guess something reminded me of this just now. Anyway, a large chunk of the funding the Linux Foundation, Linus Torvald’s employer, receives is coming from increasingly desperate companies frantically trying to convince a populace deeply skeptical and often downright hostile towards “AI” to spend money on “AI” before the bubble bursts. For some reason, I thought this was interesting.