EE Journal reports: National Instruments (NI) recently released a new version of its LabView test automation programming environment for the latest Apple Macintosh computers based on the Arm-based Apple M1 CPU/GPU SoC. At the same time, NI let its customers know that this release would be the last one for Apple Macintosh computers, sending a shock through some portion of the company’s customer base. LabView’s importance to test and measurement cannot be overstated. It was the first graphical programming language designed exclusively for test systems. The language has been continually expanded and improved for nearly 40 years and features more than 7000 software drivers for instruments from many vendors as well as support for custom, FPGA-based instruments. LabView supports many instrument interfaces starting with IEEE-488 and extending to MXI, PXI, USB, Ethernet, and probably a few more interfaces that don’t immediately come to mind. It’s a shock to many and will likely punish higher education students and a chunk of the scientific and research segment which is still Mac dominant.
After a few minor delays, FreeBSD 14.0 has officially been released. The highlights according to the FreeBSD team itself: For more details, you can dive into the release notes, and if you’re already using FreeBSD you know exactly how to upgrade.
Firefox users across the internet say that they are encountering an “artificial” five-second load time when they try to watch YouTube videos that exists on Firefox, but not Chrome. Google, meanwhile, told 404 Media that this is all part of its larger effort against ad blockers, and that it doesn’t have anything to do with Firefox at all. I’m sure it doesn’t, Google.
While Elementary OS commits to Wayland, the development team of the Budgie desktop is changing course and will work with the Xfce developers toward Budgie’s Wayland future. There is general consensus now that the future of graphical desktops on Linux lies in Wayland rather than X11, but the path is still not a smooth and easy one. While in Latvia for the Ubuntu Summit, the Reg FOSS desk met with the developers behind Ubuntu Budgie, who told us that the Budgie project is charting a new course toward the brave new Wayland world. It seems that using EFL – the Enlightenment Foundation Libraries – wasn’t the right choice for Budgie, and so they’re now exploring working with Xfce on their Wayland efforts, instead. Considering Enlightenment’s desktop Linux presence is negligible, at best, joining forces with Xfce so that both Xfce and Budgie can make progress on Wayland faster seems like the more optimal choice for the wider desktop Linux community.
Today we want to focus on what came next, Symbian Anna, which arrived a year after the launch of Symbian^3 (Symbian^2 launched only in Japan). Anna was unveiled in early 2011 alongside the Nokia X7 and Nokia E6. The E6 was a bar phone with a QWERTY keyboard (and a 2.45″ touch display), but the X7 was all touch (4.0″ display). Even better, owners of certain older Nokias would receive Anna as an update, that was the case for the Nokia N8 and E7. The Nokia C7 and C6-01 got it too. I have a few Symbian Anna and Belle (its successor) devices, and they’re not exactly great. The software is slow, cumbersome, clunky, and unpleasant to use, and simply no competition for the iPhone and Android, even at the time they came out. They’re fun novelties to play with now, but I genuinely feel sorry for the people who bought into these things back when they were new, thinking they’d get something on the level of the iPhone or Android.
The seL4 microkernel is currently the only kernel that has been fully formally verified. In general, the increased interest in ensuring the security of a kernel’s code results from its important role in the entire operating system. One of the basic features of an operating system is that it abstracts the handling of devices. This abstraction is represented by device drivers – the software that manages the hardware. A proper verification of the software component could ensure that the device would work properly unless there is a hardware failure. In this paper, we choose to model the behavior of a device driver and build the proof that the code implementation matches the expected behavior. The proof was written in Isabelle/HOL, the code translation from C to Isabelle was done automatically by the use of the C-to-Isabelle Parser and AutoCorres tools. We choose Isabelle theorem prover because its efficiency was already shown through the verification of seL4 microkernel. Some light reading that would’ve been for the weekend had I not gotten sick and unable to work on OSNews much.
In the best case, we may be able to avoid feeding the data through the compositing pipeline of the compositor as well, if the compositor supports direct scanout and the dmabuf is suitable for it. In particular on mobile systems, this may avoid using the GPU altogether, thereby reducing power consumption. I don’t understand what’s happening but it seems like a good idea? Can anyone help?
Apple has officially ceased the sale of OS X Lion 10.7 and Mountain Lion 10.8 from its online store. That’s it. That’s the post.
OpenVMS on x86 is now available for hobbyists! Almost a year after the official release. This is a part 1 of my getting started guide, showing you how to install OpenVMS on VirtualBox on Windows 10/11. More parts will follow, documenting license installation, network setup, ssh, application installation etc. If you want to give OpenVMS for x86 a try, this is the series of articles to read and follow along with. Excellent work by Remy van Elst.
A few months ago, I talked about the only PC ever shipped with BeOS preinstalled, the Flora Prius from Hitachi. However, due to illegal pressure from Microsoft, Hitachi disabled the special bootloader required to boot into BeOS, so while the best operating system ever made was right there on the hard drive, buyers couldn’t actually use it without manually restoring the bootloader and BeOS partitions. Of course, I now have to try and find a working example of this Hitachi Flora Prius computer line. They were apparently only sold in Japan, so the odds of finding one anywhere seem slim, at best. It doesn’t help that most people who bought one of these had no idea BeOS was installed or what BeOS even was, so the historical significance was lost on them. I also think these weren’t particularly noteworthy computers otherwise – most likely one of the many dime-a-dozen beige boxes sold all over the world. Searches on eBay and Japanese auction sites yield no results. I got an e-mail today from an OSNews reader, informing me of something quite rare. On the Japanese auction site mercari.com, someone is selling a BeBox, which in and of itself is already a very rare occurrence, as few BeBoxen were ever sold (1800 in total). To further add to the rarity, it’s the dual 133 MHz model, which is the rarer of the two configurations (800 pieces sold). These machines don’t come up for sale very often, and I’m pretty sure the seller is going to net a good price for this museum piece, which seems to be in almost pristine condition, without scratches of scuffs. The price is set at ¥950000 (€5821) excl. shipping (shipping costs to e.g. Europe or the US would be substantial), but I’m pretty sure the seller could ask for more. Seeing a BeBox for sale is already quite exciting, but browsing through the accompanying pictures, there’s something even rarer: documentation and software CD-ROMs for the Hitachi Floria Plus 330j and BeOS. The machine itself is not part of the auction, but even seeing the documentation and CD-ROMs for it is entirely unique, and most likely something we won’t be seeing anywhere else anytime soon. Since the Floria Plus was sold as a generic, uninteresting PC, probably long forgotten and scrapped by most people, I doubt one will ever be found. The documentation and software in this auction might be one of the last surviving tangible relics of the only PC ever sold with BeOS preinstalled.
The PARC facility also is known for the invention of Ethernet, a networking technology that allows high-speed data transmission over coaxial cables. Ethernet has become the standard wired local area network around the world, and it is widely used in businesses and homes. It was honored this year as an IEEE Milestone, a half century after it was born. Truly one of the success stories of the technology world. Sure, those first Ethernet cables and accessories have changed a lot over the decades, but we’re still using it to this day, and we’ll be using it for many more decades to come.
Shortly after announcing the end of three services, one of which is as old as MS-DOS, Microsoft deprecated the Tips app. Now, another utility is about to get the axe: Microsoft has updated its Windows documentation again, detailing the end of the story for Steps Recorder (psr.exe). Steps Recorder is an old utility from the Windows 7 era that lets you, as the name implies, record your steps while doing something in Windows. Although long abandoned, Steps Recorder is a handy tool for describing to your grandma how to perform specific actions in Windows, troubleshoot apps, or report bugs. Steps Recorder is simple and very effective, and you can launch it by pressing Win + R and typing psr. With Windows being as massively popular as it is, even removals of weird, obscure utilities and services that small percentages of Windows users used, still means hundreds of thousands of people can be affected. So, let’s pour one out for psr.
In order to comply with the EU’s Digital Markets Act, Microsoft is planning a number of changes to Windows to comply with this new legislation. Ars sums them up nicely: All of the above will be exclusive to the EU/EEA, so Windows users elsewhere are out of luck.
With these changes in place, we’ve seen support for Manifest V3 increase significantly among the extension developer community. Specifically, we are encouraged by our ongoing dialogue with the developers of content blocking extensions, who initially felt Manifest V3 could impact their ability to provide users with the features they’ve come to expect. Google has made several changes to Manifest V3 specifically to ease concerns among developers of content blocking extensions, and it seems those changes have been positively received. The maximum number of active rulesets has been increased, as well as the number of dynamic rules, which are rules ad blocker developers can change and update without having to update the extension as a whole. Regardless of these changes, I would still advise everyone to get a Raspberry Pi or whatever and run Pi-Hole – this will block ads for your entire network, and all devices, regardless of browser or operating system.
The rumors are true: Microsoft has built its own custom AI chip that can be used to train large language models and potentially avoid a costly reliance on Nvidia. Microsoft has also built its own Arm-based CPU for cloud workloads. Both custom silicon chips are designed to power its Azure data centers and ready the company and its enterprise customers for a future full of AI. Microsoft’s Azure Maia AI chip and Arm-powered Azure Cobalt CPU are arriving in 2024, on the back of a surge in demand this year for Nvidia’s H100 GPUs that are widely used to train and operate generative image tools and large language models. There’s such high demand for these GPUs that some have even fetched more than $40,000 on eBay. Amazon and Google, the two other major cloud providers, are already using all kinds of custom, in-house silicon in their datacentres, so it’s not exactly surprising Microsoft is following in their footsteps.
The European Union making tech better for everyone. We’ll have to wait and see if supporting RCS will be enough to prevent the EU from requiring Apple open up iMessage.
With this release, .NET reshapes the way we build intelligent, cloud-native applications and high-traffic services that scale on demand. Whether you’re deploying to Linux or Windows, using containers or a cloud app model of your choice, .NET 8 makes building these apps easier. It includes a set of proven libraries that are used today by the many high-scale services at Microsoft to help you with fundamental challenges around observability, resiliency, scalability, manageability, and more. Integrate large language models (LLMs) like OpenAI’s GPT directly into your .NET app. Use a single powerful component model to handle all your web UI needs with Blazor. Deploy your mobile applications to the latest version of iOS and Android with .NET MAUI. Discover new language enhancements that make your code more concise and expressive with C# 12. It’s still wild to me to that Microsoft provides detailed installation instructions for .NET for a variety of Linux distributions, down to stuff like Alpine.
Google today is announcing strengthened protections for Android developers publishing apps to its Google Play store. The changes are a part of Google’s broader efforts at keeping low-quality and unsafe apps out of its app store and off consumers’ devices, which also recently included the launch of a new real-time app scanning feature to combat malicious apps. Today, the company says it will now require new Android developers with personal accounts to test their app with a minimum of 20 people for at least 2 weeks prior to publication. It additionally plans to increase its investment in the app review processes, warning of potential slowdowns in approvals for a small number of apps as these changes roll out. At first glance, this sounds like a good idea – more testing leads to better applications, is the reasoning – but it’s going to be a massive burden for many small indie developers to even find 20 testers. In my experience, it’s usually the small indie teams or individual developers that make the best applications on Android, while the large, well-known brands release steady streams of garbage. In other words, this is going to disproportionately affect the wrong people.
It’s definitely clear that Huawei is pulling the plug on Android apps, but it’s still rather hard to believe that the company is throwing away Android (AOSP) entirely. For that, we’ll just have to wait and see, as more digging can be done when “Next” hits the scene next year. The Chinese market is big enough to sustain its own application ecosystem, and many western services are banned in China anyway, so the Play Store is of lesser value there. It makes sense for Huawei to not waste time and resources on maintaining Android application compatibility.
I tried to launch BattleTech over and over and had zero success. I couldn’t figure out why it was struggling on my model 80 board, where it runs just great on 86Box. What is going on? One thing I had stumbled upon was that if I launched an ancient Infocom game in a DOS box, and then launched BattleTech it had a much higher chance of running. But this did not always equate to it working. How is launching an old COM file from the early 80’s excise the ‘devil’ of some 1988 EXE from running? As the title suggests, it’s got to do with the math coprocessor. I know I say this often, but I’m so glad people dive into these sorts of things decades later to figure out what’s going on. It makes for great reading.
Guest post by