An anonymous reader quotes a report from 9to5Google: At the Flutter Forward event, Google released Flutter 3.7 with more Material You widgets and menus support, while also teasing the future of the app development framework. Having grown from humble beginnings on Android and iOS, Google's Flutter SDK can now help you create apps for mobile, desktop, web, and more, all from a single Dart codebase. Since launch, over 700,000 Flutter apps have been published across various platforms.

Today in Nairobi, Kenya, the Flutter team hosted Flutter Forward, an event to connect with the growing global community of developers and showcase the future of app development. For starters, Flutter version 3.7 has now been released, bringing with it a whole host of Material 3 (Material You) widgets. To get a feel for what all is possible with the new generation of Material Design in Flutter, Google has prepared a fun web showcase that even allows you to toggle between Material Theming and Material You. You'll also find that Flutter 3.7 includes new support for creating menus for your app -- including native support for macOS menus, new cascading menu widgets, and the ability to add items to right-click/long-press context menus. The built-in text magnifier on Android and iOS also now works as expected with Flutter's text fields. You can learn more about the improvements of Flutter 3.7 in the full release blog.

Looking ahead, the Flutter team has been working for quite some time on replacing the Skia renderer with a more robust solution of its own. Currently dubbed "Impeller," Flutter's new rendering engine has made significant enough progress to now be ready for developers to test it with their iOS apps. [...] Google is also working on new ways to help Flutter apps integrate with the underlying OS or platform. [...] Meanwhile, for Flutter web apps, a new "js" library makes it easy to call your app's Dart code from the outer page's JavaScript code. Relatedly, you can now embed a Flutter view onto a page through a standard HTML div. Both of these can be seen in a fun demonstration page.

Elsewhere in Flutter web news, Google has made strides toward compiling Dart apps using WebAssembly. [...] In time, this should result in significant performance improvements for Flutter on the web. In addition to compiling to WebAssembly, the Dart team has also begun offering full support for the RISC-V architecture, with the ultimate goal of Flutter apps running on RISC-V. Another major announcement today is that Google is moving forward with its plans to release version 3.0 of the Dart programming language upon which Flutter apps are built. Dart 3.0 is available today for early alpha testing with a focus on requiring sound null safety.

Apple has provided iOS 12.5.7, macOS 11.7.3, and other updates for older devices that can't be updated to the latest releases. AppleInsider reports: The new updates are for users still using older devices and operating systems and address similar bugs and security patches available in the recent iOS 16.3 and macOS Ventura releases. The security patch notes list at least 14 different systems affected by security issues that have been patched. The new update versions are: iOS 12.5.7, iOS 15.7.3, iPadOS 15.7.3, macOS Big Sur 11.7.3, and macOS Monterey 12.6.3.

Users may note the skipped iOS versions between iOS 12 and iOS 15. Those are due to where devices were cut off from updating. Every device that could run iOS 13 could run iOS 15, so Apple doesn't update every version. The oldest device supported by iOS 12.5.7, for example, is the iPhone 5s, which was released in September 2013. The oldest Macs supported by macOS Big Sur are the 2013 MacBook Air, Mac Pro, and MacBook Pro. Anyone capable of updating these new updates to the older operating systems should do so as soon as possible. The update addresses known security issues that could put the user at risk.

An anonymous reader quotes a report from ArsTechnica: Google is still reeling from the biggest layoff in company history last Friday. Earlier cost cuts over the past six months have resulted in several projects being shut down or deprioritized at Google, and it's hard to fire 12,000 people without some additional projects taking a hit. The New York Times has a report about which divisions are being hit the hardest, and a big one is Google's future OS development group, Fuchsia. While the overall company cut 6 percent of its employees, the Times pointed out that Fuchsia saw an outsize 16 percent of the 400-person staff take a hit. While it's not clear what that means for the future of the division, the future of Fuchsia's division has never really been clear.

Fuchsia has been a continuous mystery inside Google since it first saw widespread press coverage in 2017. Google rarely officially talks about it, leaving mostly rumors and Github documentation for figuring out what's going on. The OS isn't a small project, though -- it's not even based on Linux, opting instead to use a custom, in-house kernel, so Google really is building an entire OS from scratch. Google actually ships the OS today to consumers in its Nest smart displays, where it replaced the older Cast OS. The in-place operating system swap was completely invisible to consumers compared to the old OS, came with zero benefits, and was never officially announced or promoted. There's not much you can do with it on a locked-down smart display, so even after shipping, Fuchsia is still a mystery.

HPE and Oracle have settled their long-running legal case over alleged copyright infringement regarding Solaris software updates for HPE customers, but it looks like the nature of the settlement is going to remain under wraps. The Register reports: The pair this week informed [PDF] the judge overseeing the case that they'd reached a mutual settlement and asked for the case to be dismissed "with prejudice" -- ie, permanently. The settlement agreement is confidential, and its terms won't be made public. The case goes back to at least 2016, when Oracle filed a lawsuit against HPE over the rights to support the Solaris operating system. HPE and a third company, software support outfit Terix, were accused of offering Solaris support for customers while the latter was not an authorized Oracle partner.

Big Red's complaint claimed HPE had falsely represented to customers that it and Terix could lawfully provide Solaris Updates and other support services at a lower cost than Oracle, and that the two had worked together to provide customers with access to such updates. The suit against HPE was thrown out of court in 2019, but revived in 2021 when a judge denied HPE's motion for a summary judgement in the case. Terix settled its case in 2015 for roughly $58 million. Last year, the case went to court and in June a jury found HPE guilty of providing customers with Solaris software updates without Oracle's permission, awarding the latter $30 million for copyright infringement.

But that wasn't the end of the matter, because HPE was back a couple of months later to appeal the verdict, claiming the complaint by Oracle that it had directly infringed copyrights with regard to Solaris were not backed by sufficient evidence. This hinged on HPE claiming that Oracle had failed to prove that any of the patches and updates in question were actually protected by copyright, but also that Oracle could not prove HPE had any control over Terix in its purported infringement activities. Oracle for its part filed a motion asking the court for a permanent injunction against HPE to prevent it copying or distributing the Solaris software, firmware or support materials, except as allowed by Oracle. Now it appears that the two companies have come to some mutually acceptable out-of-court arrangement, as often happens in acrimonious and long-running legal disputes.

An anonymous reader quotes a report from Ars Technica: As part of the Apple Lisa's 40th birthday celebrations, the Computer History Museum has released the source code for Lisa OS version 3.1 under an Apple Academic License Agreement. With Apple's blessing, the Pascal source code is available for download from the CHM website after filling out a form. Lisa Office System 3.1 dates back to April 1984, during the early Mac era, and it was the Lisa equivalent of operating systems like macOS and Windows today. The entire source package weighs is about 26MB and consists of over 1,300 commented source files, divided nicely into subfolders that denote code for the main Lisa OS, various included apps, and the Lisa Toolkit development system.

First released on January 19, 1983, the Apple Lisa remains an influential and important machine in Apple's history, pioneering the mouse-based graphical user interface (GUI) that made its way to the Macintosh a year later. Despite its innovations, the Lisa's high price ($9,995 retail, or about $30,300 today) and lack of application support held it back as a platform. A year after its release, the similarly capable Macintosh undercut it dramatically in price. Apple launched a major revision of the Lisa hardware in 1984, then discontinued the platform in 1985. [...] Lisa OS defined important conventions that we still use in windowing OSes today, such as drag-and-drop icons, movable windows, the waste basket, the menu bar, pull-down menus, copy and paste shortcuts, control panels, overlapping windows, and even one-touch automatic system shutdown.

According to the latest official Android distribution numbers from Google, Android 13 is running on 5.2% of all devices less than six months after launch. 9to5Google reports: According to Android Studio, devices running Android 13 now account for 5.2% of all devices. Meanwhile Android 12 and 12L now account for 18.9% of the total, a significant increase from August's 13.5% figure. Notably, while Google's chart does include details about Android 13, it doesn't make a distinction between Android 12 and 12L. Looking at the older versions, we see that usage of Android Oreo has finally dropped below 10%, with similar drops in percentage down the line. Android Jelly Bean, which previously weighed in at 0.3%, is no longer listed, while KitKat has dropped from 0.9% to 0.7%. Android 13's 5.2% distribution number "is better than it sounds," writes Ryan Whitwam via ExtremeTech: These numbers show an accelerating pickup for Google's new platform versions. If you look back at stats from the era of Android KitKat and Lollipop, the latest version would only have a fraction of this usage share after half a year. That's because the only phones running the new software would be Google's Nexus phones, plus maybe one or two new devices from OEMs that worked with Google to deploy the latest software as a marketing gimmick.

The improvements are thanks largely to structural changes in how Android is developed and deployed. For example, Project Treble was launched in 2017 to re-architect the platform, separating the OS framework from the low-level vendor code. This made it easier to update devices without waiting on vendors to provide updated drivers. We saw evidence of improvement that very year, and it's gotten better ever since.

An anonymous reader shares a report: Microsoft's Windows 10 operating system has been available on the retail market for over seven years and was superseded by Windows 11 in October 2021. However, despite its age, Windows 10 remains the most popular version of Windows, with a global market share of 67.95% in December 2022 compared to 16.97% for Windows 11, according to StatCounter. But it now looks like Microsoft is ready to put the brakes on issuing new Windows 10 licenses to everyday consumers. Microsoft's official product pages for Windows 10 Home and Windows 10 Pro now include the following disclaimer: "January 31, 2023 will be the last day this Windows 10 download is offered for sale. Windows 10 will remain supported with security updates that help protect your PC from viruses, spyware, and other malware until October 14, 2025."

"If you've been itching to try an Arch Linux distribution and want something outside of the usual GNOME/KDE/Xfce desktop environments, Mabox Linux is an outstanding option...." writes ZDNet's Jack Wallen.

"It reminded me of my early days using Linux, only with a bit of a modern, user-centric twist...." Linux was hard in its infancy. So, when I see a Linux distribution that reminds me of those days but manages to make it easy on users without years of experience under their belts, it reminds me how far the open-source operating system has come. Such is the case with Mabox Linux.... It's not that Mabox doesn't make Arch Linux easy...it does. But when you first log into the desktop, you are greeted with something most hard-core Linux users love to see but can be a real put-off to new users. I'm talking about information...and lots of it.Â

You see, Mabox Linux places four information-centric widgets front and center on the desktop, so you can get an at-a-glance look at how the OS is using your system resources and even two widgets that give you keyboard shortcuts for things like opening various apps, menus, and even window management controls. Also on the OpenBox Window Manager desktop, you'll find a single top panel that gives you quick access to all your installed apps, the Mabox Colorizer... and a system tray with plenty of controls....

Once you have the distribution installed, the big surprise comes by way of performance. Mabox Linux is amazingly fast...like faster than most distributions I've used. A big part of that is due to the OpenBox Window Manager, which is very lightweight. Compared to my regular GNOME-based Linux desktop, Mabox is like driving a Lamborgini instead of a Prius. The difference is that obvious.ÂÂ
The installation process lets you choose between open-source or proprietary video drivers, the article points out. And "you can easily customize the color of your Mabox desktop, including the theme, side panels, Conky (which creates the desktop widgets), wallpaper, Tint2 Panel, and even the terminal theme."

An anonymous reader quotes a report from Ars Technica: It can be done. Android manufacturers can actually support a phone for a sizable amount of time. Fairphone has announced the end of life for the Fairphone 2, which will be March 2023. That phone was released in October 2015, so that's almost seven-and-a-half years of updates. Fairphone is a very small Dutch company with nowhere near as many resources as Google, Samsung, BBK, and the other Big-Tech juggernauts, yet it managed to outlast them with its support program. The whole goal of the company is sustainability, with easily repairable phones, available spare parts, and long update promises. The Fairphone 4 has a five-year hardware warranty and six years of updates, and the company's reputation says it can provide that. Sadly, the phones only ship in the UK and Europe. The Fairphone 2 only promised "three to five years" of updates, and it blew that out of the water.

The Fairphone 2 features the Qualcomm Snapdragon 801 SoC, a chip that Qualcomm ended support for with Android 6.0. In what is probably an Android ecosystem first, that lack of chipset support didn't stop Fairphone, which teamed up with LineageOS and today ships Android 10 on the 7-year-old device. That's not the newest OS in the world, but it passes all of Google's Android compatibility tests. I'm sure there are newer amateur releases in the Android ROM community, but Fairphone's Android 10 build is up to the standard of an official release, as opposed to the "tell me what doesn't work" standard of many amateur ROM releases. Fairphone doesn't say why support is ending in March, but if it's staying on Android 10, it was going to have to kill support sometime this year. Google only supports security patches for the last four versions of Android, so even Google will be shutting down Android 10 support soon.

OS News cheers the first official release of Vanilla OS, calling it "an immutable desktop Linux distribution that brings some interesting new technologies to the table, such as the Apx package manager."

From the official release announcement: "By default, Apx provides a container based on your Linux distribution (Ubuntu 22.10 for Vanilla OS 22.10) and wraps all commands from the distribution's package manager (apt for Ubuntu). Nevertheless, you can install packages from other package distributions.... Using the --dnf flag with apx will create a new container based on Fedora Linux. Here, apx will manage packages from Fedora's DNF repository, tightly integrating them with the host system.
ZDNet calls Vanilla OS "a new take on Linux that is equal parts heightened security and user-friendly." Among other things, "the developers opted to switch to ABRoot, which allows for fully atomic transactions between 2 root partitions." The official release announcement explains: ABRoot will check which partition is the present root partition (i.e A), then it will mount an overlay on top of it and perform the transaction. If the transaction succeeds, the overlay will be merged with the future root partition (i.e B). On your next boot, the system will automatically switch to the new root partition (B). In case of failure, the overlay will be discarded and the system will boot normally, without any changes to either partition.
But ZDNet explains why this comes in handy: Another really fascinating feature is called Smart Updates, which is enabled in the Vanilla OS Control Center, and ensures the system will not update if it's either under a heavy load or the battery is low. To enable this, open the Vanilla OS Control Center, click on the Updates tab, and then click the ON/OFF slider for SmartUpdate. Once enabled, updates will go through ABRoot transitions and aren't applied until the next reboot. Not only does this allow the updates to happen fully in the background, but it also makes them atomic, so they only proceed when it's guaranteed they will succeed.

The only caveat to this system is that you are limited to either weekly or monthly updates, as there is no daily option for scheduling. However, if you're doing weekly updates, you should be good to go.... Setting aside that which makes Vanilla OS special, the distribution is as stock a GNOME experience as you'll find and does a great job serving as your desktop operating system. It's easy to use, reliable, and performs really well...especially considering this is the first official release.
"Every wallpaper has a light and a dark version," adds the release announcement, "so you can choose the one that best suits your needs."

Raymond Chen, writing for Microsoft DevBlogs: In the mid-1980's, Microsoft produced an expansion card for the IBM PC and PC XT, known as the Mach 10. In addition to occupying an expansion slot, it also replaced your CPU: You unplugged your old and busted 4.77 MHz 8088 CPU and plugged into the now-empty socket a special adapter that led via a ribbon cable back to the Mach 10 card. On the Mach 10 card was the new hotness: A 9.54 MHz 8086 CPU. This gave you a 2x performance upgrade for a lot less money than an IBM PC AT. The Mach 10 also came with a mouse port, so you could add a mouse without having to burn an additional expansion slot. Sidebar: The product name was stylized as MACH [PDF] in some product literature. The Mach 10 was a flop.

Undaunted, Microsoft partnered with a company called Portable Computer Support Group to produce the Mach 20, released in 1987. You probably remember the Portable Computer Support Group for their disk cache software called Lightning. The Mach 20 took the same basic idea as the Mach 10, but to the next level: As before, you unplugged your old 4.77 MHz 8088 CPU and replaced it with an adapter that led via ribbon cable to the Mach 20 card, which you plugged into an expansion slot. This time, the Mach 20 had an 8 MHz 80286 CPU, so you were really cooking with gas now. And, like the Mach 10, it had a mouse port built in. According to a review in Info World, it retailed for $495. The Mach 20 itself had room for expansion: it had an empty socket for an 80287 floating point coprocessor. One daughterboard was the Mach 20 Memory Plus Expanded Memory Option, which gave you an astonishing 3.5 megabytes of RAM, and it was high-speed RAM since it wasn't bottlenecked by the ISA bus on the main motherboard. The other daughterboard was the Mach 20 Disk Plus, which lets you connect 5 1/4 or 3 1/2 floppy drives.

A key detail is that all these expansions connected directly to the main Mach 20 board, so that they didn't consume a precious expansion slot. The IBM PC came with five expansion slots, and they were in high demand. You needed one for the hard drive controller, one for the floppy drive controller, one for the video card, one for the printer parallel port, one for the mouse. Oh no, you ran out of slots, and you haven't even gotten to installing a network card or expansion RAM yet! You could try to do some consolidation by buying so-called multifunction cards, but still, the expansion card crunch was real. But why go to all this trouble to upgrade your IBM PC to something roughly equivalent to an IBM PC AT? Why not just buy an IBM PC AT in the first place? Who would be interested in this niche upgrade product?

It's still possible to learn a lot of interesting things about old operating systems. Sometimes those things were documented, or at least hinted at, in blog posts that miraculously still exist. One such quirk showed up recently when someone noticed how Microsoft made sure that SimCity and other popular apps worked on Windows 95. From a report: A recent tweet by @Kalyoshika highlights an excerpt from a blog post by Fog Creek Software co-founder, Stack Overflow co-creator, and longtime software blogger Joel Spolsky. The larger post is about chicken-and-egg OS/software appeal and demand. The part that caught the eye of a Hardcore Gaming 101 podcast co-host is how the Windows 3.1 version of SimCity worked on the Windows 95 system. Windows 95 merged MS-DOS and Windows apps, upgraded APIs from 16 to 32-bit, and was hyper-marketed. A popular app like SimCity, which sold more than 5 million copies, needed to work without a hitch. Spolsky's post summarizes how SimCity became Windows 95-ready, as he heard it, without input from Maxis or user workarounds.

Jon Ross, who wrote the original version of SimCity for Windows 3.x, told me that he accidentally left a bug in SimCity where he read memory that he had just freed. Yep. It worked fine on Windows 3.x, because the memory never went anywhere. Here's the amazing part: On beta versions of Windows 95, SimCity wasn't working in testing. Microsoft tracked down the bug and added specific code to Windows 95 that looks for SimCity. If it finds SimCity running, it runs the memory allocator in a special mode that doesn't free memory right away. That's the kind of obsession with backward compatibility that made people willing to upgrade to Windows 95.

Spolsky (in 2000) considers this a credit to Microsoft and an example of how to break the chicken-and-egg problem: "provide a backwards compatibility mode which either delivers a truckload of chickens, or a truckload of eggs, depending on how you look at it, and sit back and rake in the bucks."

An anonymous reader quotes a report from Electrek: Audi is preparing to convert its entire network of global production factories to manufacture electric vehicles as it gears up to compete in the auto industry's future. ;...] Audi announced last year that its last combustion car would roll off the line in 2033 (if they are still around then), launching only electric vehicles from 2026. To better compete in the new EV era and ease the transition, Audi will convert all exiting existing production factories to build electric vehicles by 2029. Audi board member for production and logistics Gerd Walker said, "Step by step, we are bringing all our sites into the future" as the automaker prepares to go all in on electric vehicles.

In a press release Tuesday, Audi presented the "plan for the production of the future," including converting its network of global factories to produce purely electric vehicles. Walker added: "The path Audi is taking conserves resources and accelerates our transformation to a provider of sustainable premium mobility. Rather than building new facilities like some competitors, Audi will work to incorporate the flexibility these new state-of-the-art plants provide into its existing operations."

A primary focal point of Audi's production plan is to cut annual factory costs in half by 2033, aligning with when it plans to phase out combustion models. To do so, the company will continue to digitalize and streamline its manufacturing processes with solutions like Edge Cloud 4 Production. According to Audi, less expensive industrial PCs will result in lower IT costs with software updates and OS changes. To have the ability to respond to fluctuating consumer demand, Walker says: "We want to structure both product and production so we get the optimum benefit for our customers." He adds an example of building the new Audi Q6 e-tron on the same line as the A4 and A5 as it phases out its gas models.

Esper: The world's biggest tech companies have lost confidence in one of the Internet's behind-the-scenes gatekeepers. Microsoft, Mozilla, and Google are dropping TrustCor Systems as a root certificate authority in their products. Starting in Chrome version 111 for desktops, the browser will no longer trust certificates issued by TrustCor Systems. The same change is coming to Android, but unlike Chrome for desktops, Android's root certificate store can't be updated independently of the OS, meaning it'll take some time for the certificate changes to roll out. Thankfully, that may no longer be the case in Android 14, as Google is preparing to implement updatable root certificates in the next release.

An anonymous reader quotes a report from Ars Technica: Pine64, makers of ARM-based, tinker-friendly gadgets, is making the PineTab 2, a sequel to its Linux-powered tablet that mostly got swallowed up by the pandemic and its dire global manufacturing shortages. The PineTab 2, as described in Pine64's "December Update," is based around the RK3566, made by RockChip. Pine64 based its Quartz64 single-board system on the system-on-a-chip (SoC), and has all but gushed about it across several blog posts. It's "a dream-of-a-SoC," writes Community Director Lukasz Erecinski, a "modern mid-range quad-core Cortex-A55 processor that integrates a Mali-G52 MP2 GPU. And it should be ideal for space-constrained devices: it runs cool, has a variety of I/O options, solid price-to-performance ratio, and "is genuinely future-proof."

The PineTab 2 is a complete redesign, Erecinski claims. It has a metal chassis that "is very sturdy while also being easy to disassemble for upgrades, maintenance, and repair." The tablet comes apart with snap-in tabs, and Pine64 will offer replacement parts. The insides are modular, too, with the eMMC storage, camera, daughter-board, battery, and keyboard connector all removable "in under 5 minutes." The 10.1-inch IPS display, with "modern and reasonably thin bezels," should also be replaceable, albeit with more work. On that easily opened chassis are two USB-C ports, one for USB 3.0 I/O and one for charging (or USB 2.0 if you want). There's a dedicated micro-HDMI port, and a front-facing 2-megapixel camera and rear-facing 5-megapixel (not the kind of all-in-one media production machine Apple advertises, this tablet), a microSD slot, and a headphone jack. While a PCIe system is exposed inside the PineTab, most NVMe SSDs will not fit, according to Pine64. All of this is subject to change before final production, however.

As with the original PineTab, this model comes with a detachable, backlit keyboard cover, included by default. That makes supporting a desktop OS for the device far more viable, Erecinski writes. The firmware chipset is the same as in the PineBook Pro, which should help with that. No default OS has been decided as of yet, according to Pine64. The tablet should ship with two memory/storage variants, 4GB/64GB and 8GB/128GB. It's due to ship "sometime after the Chinese New Year" (January 22 to February 5), though there's no firm date. No price was announced, but "it will be affordable regardless of which version you'll settle on." A video version of the "December Update" can be found on YouTube.

The Z-Wave Alliance, the Standards Development Organization (SDO) dedicated to advancing the smart home and Z-Wave technology, today announced the completion of the Z-Wave Source Code project, which has been published and made available on GitHub to Alliance members. From a report: The Z-Wave Source Code Project opens development of Z-Wave and enables members to contribute code to shape the future of the protocol under the supervision of the new OS Work Group (OSWG). The goal of the project is to provide a rich development environment that contains the relevant source code and sample applications to those seeking to play a direct role in the advancement of the Z-Wave standard. The quality and interoperability of products utilizing Z-Wave Source Code will also be enforced by a new mandatory Silicon & Stack Certification program. Full Z-Wave certification will continue to test and certify for Z-Wave S2 security, network connectivity, range, battery life, and interoperability including backwards and forwards compatibility.

"The Z-Wave Alliance is deeply committed to the global smart home market," said Mitch Klein, Executive Director of the Z-Wave Alliance. "This year the smart home conversations have focused largely on Matter. Shiny and new, and with big brands supporting the initiative, Matter is bringing a lot of attention to the smart home. This makes it easy to overlook Z-Wave as the most established, trusted, and secure smart home protocol, that also happens to have the largest certified interoperable ecosystem in the market. We firmly expect that Z-Wave will play a key role in connecting devices and delivering the experience users really want."

Microsoft's Chromium-based Edge browser was an improvement over the initial version of Edge in many ways, including its support for Windows 7 and Windows 8. But the end of the road is coming: Microsoft has announced that Edge will end support for Windows 7 and Windows 8 in mid-January of 2023, shortly after those operating systems stop getting regular security updates. From a report: Support will also end for Microsoft Edge Webview2, which can use Edge's rendering engine to embed webpages in non-Edge apps. The end-of-support date for Edge coincides with the end of security update support for both Windows 7 and Windows 8 on January 10, and the end of Google Chrome support for Windows 7 and 8 in version 110. Because the underlying Chromium engine in both Chrome and Edge is open source, Microsoft could continue supporting Edge in older Windows versions if it wanted, but the company is using both end-of-support dates to justify a clean break for Edge.

Anyone remember the high-end commercial UNIX workstations from a few decades ago — like from companies like IBM, DEC, SGI, and Sun Microsystems?

Today OSnews looked back — but also explored what happens when you try to buy one today> : As x86 became ever more powerful and versatile, and with the rise of Linux as a capable UNIX replacement and the adoption of the NT-based versions of Windows, the days of the UNIX workstations were numbered. A few years into the new millennium, virtually all traditional UNIX vendors had ended production of their workstations and in some cases even their associated architectures, with a lacklustre collective effort to move over to Intel's Itanium — which didn't exactly go anywhere and is now nothing more than a sour footnote in computing history.

Approaching roughly 2010, all the UNIX workstations had disappeared.... and by now, they're all pretty much dead (save for Solaris). Users and industries moved on to x86 on the hardware side, and Linux, Windows, and in some cases, Mac OS X on the software side.... Over the past few years, I have come to learn that If you want to get into buying, using, and learning from UNIX workstations today, you'll run into various problems which can roughly be filed into three main categories: hardware availability, operating system availability, and third party software availability.
Their article details their own attempts to buy one over the years, ultimately concluding the experience "left me bitter and frustrated that so much knowledge — in the form of documentation, software, tutorials, drivers, and so on — is disappearing before our very eyes." Shortsightedness and disinterest in their own heritage by corporations, big and small, is destroying entire swaths of software, and as more years pass by, it will get ever harder to get any of these things back up and running.... As for all the third-party software — well, I'm afraid it's too late for that already. Chasing down the rightsholders is already an incredibly difficult task, and even if you do find them, they are probably not interested in helping you, and even if by some miracle they are, they most likely no longer even have the ability to generate the required licenses or release versions with the licensing ripped out. Stuff like Pro/ENGINEER and SoftWindows for UNIX are most likely gone forever....

Software is dying off at an alarming rate, and I fear there's no turning the tide of this mass extinction.
The article also wonders why companies like HPE don't just "dump some ISO files" onto an FTP server, along with patch depots and documentation. "This stuff has no commercial value, they're not losing any sales, and it will barely affect their bottom line.

An anonymous reader quotes a report from Ars Technica: Following Google's beta rollout of the feature in October, passkeys are now hitting Chrome stable M108. "Passkey" is built on industry standards and backed by all the big platform vendors -- Google, Apple, Microsoft -- along with the FIDO Alliance. Google's latest blog says: "With the latest version of Chrome, we're enabling passkeys on Windows 11, macOS, and Android." The Google Password Manager on Android is ready to sync all your passkeys to the cloud, and if you can meet all the hardware requirements and find a supporting service, you can now sign-in to something with a passkey. [...]

Now that this is actually up and running on Chrome 108 and a supported OS, you should be able to see the passkey screen under the "autofill" section of the Chrome settings (or try pasting chrome://settings/passkeys into the address bar). Next up we'll need more websites and services to actually support using a passkey instead of a password to sign in. Google Account support would be a good first step -- right now you can use a passkey for two-factor authentication with Google, but you can't replace your password yet. Everyone's go-to example of passkeys is the passkeys.io demo site, which we have a walkthrough of here.

Microsoft has released an out-of-band update to nudge laggards toward Windows 11 amid a migration pace that company executives would undoubtedly prefer is rather faster. From a report: The software giant is offering an option of upgrading to Windows 11 as an out of box experience to its Windows 10 22H2 installed base, the main aim being to smooth their path forward to the latest operating system. "On November 30, 2022, an out-of-band update was released to improve the Windows 10, version 2004, 20H2, 21H1, 21H2, and 22H2 out-of-box experience (OOBE). It provides eligible devices with the option to upgrade to Windows 11 as part of the OOBE process. This update will be available only when an OOBE update is installed."

The update, KB5020683, applies only to Windows 10 Home and Professional versions 2004, 20H2, 21H1, 22H2. There are some pre-requisites that Microsoft has listed here before users can make the move to Windows 11. The operating system was released on October 5 last year but shifting stubborn consumers onto this software has proved challenging for top brass at Microsoft HQ in Redmond. According to Statcounter, a web analytics service that has tracking code installed on 1.5 million websites and records a page view for each, some 16.12 percent of Windows users had installed Windows 11 in November, higher than the 15.44 percent in the prior month, but likely still not close to the figures that Microsoft was hoping for.