Monthly Archive:: February 2021

Unfortunately, Microsoft doesn’t allow you to remove 3D Objects and other folders from File Explorer using Control Panel or Settings. If you want to remove these folders, you need to use Registry editor and delete the entry. With the Sun Valley update, Microsoft is looking to reduce the clutter in File Explorer and they plan to hide the 3D Objects folder by default. After the update, this useless folder will no longer be shown under ‘This PC’ unless you right-click and select the “Show all folders” option on the navigation pane. I know this is a small change, and I know it’s insignificant, but these unremovable garbage folders always feel like such a slap in the face. It’s an annoying reminder that when you use Windows, you don’t really own your computer.

At Framework, we believe the time has come for consumer electronics products that are designed to last. Founded in San Francisco in 2019, our mission is to empower you with great products you can easily customize, upgrade, and repair, increasing longevity and reducing e-waste in the process. Today, we are excited to unveil our first product: the Framework Laptop, a thin, lightweight, high-performance 13.5” notebook that can be upgraded, customized, and repaired in ways that no other notebook can. This product – be sure to read the description and features – seems too good to be true. I hope they can keep their promises, because this is exactly what a lot of people are looking for.

How do you boot a computer from punch cards when the computer has no operating system and no ROM? To make things worse, this computer requires special metadata called “word marks” that can’t be represented on a card. In this blog post, I describe the interesting hardware and software techniques used in the vintage IBM 1401 computer to load software from a deck of punch cards. (Among other things, half of each card contains loader code that runs as each card is read.) I go through some IBM 1401 machine code in detail, which illustrates the strangeness of the 1401’s architecture and instruction set compared to a modern machine. I simply cannot imagine what wizardry these newfangled computers must’ve felt like to the people of the ’50s, when computers first started to truly cement themselves in the public consciousness. Even though they’ve been around for twice as long, I find a world without cars far, far easier to imagine and grasp than a world without computers.

The Playstation 2 was not one of the most powerful consoles of its generation, yet it managed to achieve a level of popularity unthinkable for other companies. This machine is nowhere near as simple as the original Playstation was, but we will see why it didn’t share the same fate of previous complicated consoles. Excellent deep dive into the Playstation 2.

In the middle of last year I reviewed System76’s Lemur Pro, a lightweight, battery-life focused Linux laptop. I concluded that the Lemur Pro did not have any big failings, and packed a few stand-out features such as the amazing battery life and open source firmware few – if any – other laptop makers can offer. Linux user or not, the Lemur Pro was a great all-rounder that could go toe-to-toe with competing Windows laptops any day of the week. Since the publication of that review, System76 has released a new version of the Lemur Pro, focusing entirely on upgrading the internals of the machine. The casing, the keyboard, the trackpad, the display, and so on, remain unchanged, but this time around, it comes packing with Intel’s latest 11th Gen Core i5 or i7 processor – the 1135G7 or 1165G7 – and thus with Intel Iris Xe graphics, which should prove to be a massive boost over the previous generation’s UHD graphics. This won’t be a full review – other than the spec bump, nothing has changed regarding the rest of the Lemur Pro. Aside from possible changes mentioned here, the review of last year’s model still applies. As such, I decided to use the term “re-review”, which I think better describes this article. I opted for the Core i5 model this time around, since I feel the difference between it and the i7 are relatively small, especially considering the intended use case for a lightweight ultrabook such as this. This gave me some more financial room to max out the RAM at 40GB (DDR4 at 3200Mhz) and pick the 1TB SSD (M.2 PCIe gen4). The price of this specific configuration is $1613.00. The remainder of the specifications are identical to last year’s machine. It has the same fairly standard 1920×1080 14.1″ 60Hz panel, which won’t win any awards, but isn’t bad in any way either. Much like last year, I do wish System76 offered higher resolution and especially higher refresh rates as options, since once you go high refresh rate, you just can’t go back. At the same time, however, I know a lot of people are still using 60Hz displays, and wouldn’t care one bit about sticking to it. The ports situation remains the same as well, so you get one USB 3.1 Type-C Gen 2 port (these names…), two USB 3.0 Type-A ports, a MicroSD slot, an HDMI port, a barrel connector for the included charger, a combined headphone/microphone jack, and that Kensington lock thing for corporate or public environments. The Type-C port can be used a DisplayPort as well, and USB-C charging is supported as well. The stand-out feature of last year’s model makes a return here, with the 73Wh battery once again delivering astonishing battery life. I can easily go over 10 hours of normal use – some browsing, some video, some basic document work – and for this model, they’ve fixed the issue I had last year where setting the laptop to battery-saving mode would cause signficiant slowdowns in playing video. I’m sure the brand new Iris Xe graphics play a big role here, and I just leave the battery-saving mode on at all times, since I didn’t notice any downsides. Not noticing any downsides to the battery-saving mode is definitely one of the main advantages of the move to 11th Gen Intel processors and the Iris Xe GPU, but that’s not the only benefit – the laptop gets less hot too, which is great for those of us using laptops on our, you know, laps. Kicking in an open door, overall performance is improved too, with applications opening faster, complex web pages loading faster, and less fans spinning up, too. This being a full Intel machine also means it’s already, well, ready for Wayland, without having to resort to workarounds or hacks. Sadly, if using System76’s own Pop!_OS, you need to manually enable Wayland by commenting out WaylandEnable=false in /etc/gdm3/custom.conf/. Once you’ve done this, Wayland is an option in GDM and you can login. I’m taking Wayland compatibility into account when it comes to my purchasing decisions, and I figured I’m probably not alone in this. I hope System76 makes Wayland easier to enable – or even the default – on its fully Intel machines soon, because it definitely improves responsiveness and performance across the board. This is hard to quantify, and people will understandably ask for proof, but on all three machines I’m currently running in Wayland – my Dell XPS 13 9370, this Lemur Pro, and a Blackbird POWER9 machine – there’s less stutter, less tearing, better video playback performance, and lower heat output when using Wayland compared to X.org. As I mentioned at the beginning, this new Lemur Pro is a spec bump, and as such, the trackpad and keyboard are still the same. While the keyboard was already a solid one, I was less happy with the trackpad, and that remains the same here. It’s still of the diving board type, and its surface doesn’t feel nearly as nice as that of my XPS 13 – which has an excellent trackpad – or other competitors, such as the best-in-class trackpads found on Apple’s laptops. It’s not a bad trackpad, but it’s not particularly good or great either – just average. In conclusion, this new generation of the Lemur Pro is by all accounts an excellent upgrade, with better performance, less heat output and fewer fan spin-ups – all without sacrificing the excellent battery life of its predecessor. If you have one of the earlier generations Lemur Pros with the same design, there’s probably not enough here to warrant an upgrade, but if you were on the fence last year, the spec bump definitely warrants a new, fresh look. System76 took their already excellent all-rounder, and made it even better, without rocking the boat, without large changes in pricing, and still with System76’s unique open source firmware and coreboot which you’ll be hard-pressed to find anywhere else. And that’s exactly what

Solaris is still a thing, even though it’s now developed by a company nobody likes and seems to have lost all of the momentum among enthusiasts, so much so that I doubt anyone will even really care about this news item. Oracle released Solaris 11.4 almost three years ago, and is still updating it with monthly updates. Solaris 11.4 SRU30 is the latest one, released on 16 February. The update consists mainly of updates from upstream packages, but there seems to be little in the way of new features or big improvements. For those, we have to most likely wait until Solaris 11.5 or 12.0, if Oracle ever makes it that far with the formerly open source operating system that they closed back up.

One of the most important tasks of the distribution packager is to ensure that the software shipped to our users is free of security vulnerabilities. While finding and fixing the vulnerable code is usually considered upstream’s responsibility, the packager needs to ensure that all these fixes reach the end users ASAP. With the aid of central package management and dynamic linking, the Linux distributions have pretty much perfected the deployment of security fixes. Ideally, fixing a vulnerable dependency is as simple as patching a single shared library via the distribution’s automated update system. Of course, this works only if the package in question is actually following good security practices. Over the years, many Linux distributions (at the very least, Debian, Fedora and Gentoo) have been fighting these bad practices with some success. However, today the times have changed. Today, for every 10 packages fixed, a completely new ecosystem emerges with the bad security practices at its central point. Go, Rust and to some extent Python are just a few examples of programming languages that have integrated the bad security practices into the very fabric of their existence, and recreated the same old problems in entirely new ways. This post explains the issue packagers run into very well – and it sure does look like these newer platforms are not very good citizens. I know this isn’t related, but this gives me the same feelings and reservations as Flatpak, Snap, and similar tools.

The first Android 12 developer preview hit the streets Thursday, and we’ve played with it for a day. There’s not a lot to see in this release—at least not at first. Most of the interesting bits are hidden, and the developer community is slowly enabling them. Many changes are half-finished alpha tweaks that will look different in the final release; after all, Google says these releases are for “testing and feedback.” This first release of Android 12 is meant to get some APIs and other changes in front of people for feedback, but it’s also designed to not spill the beans too much on what the final build of Android 12 will look like. With that in mind, many of the features in an earlier Android 12 leak seem right on the money. This public release is a sanitized build with a lot of stuff turned off, but the more we flip on hidden flags and catch hints in the documentation, the more this build looks like a solid halfway point between Android 11 and those leaked Android 12 screenshots. Ars always has great overviews of upcoming Android releases, and this one is no exception.

The focus of this update is to support a number of new features that are useful for applications and games, and which have also been considered potential integration pain points for the Wayland driver. These are copy/paste, drag-and-drop and support for changing the display mode. Getting Wine properly supported on Wayland is a hugely important step in the move to Wayland, because thanks to Wine/Proton, gaming on Linux is massively viable. Having to use XWayland for games is not something I’m looking forward to.

A new court filing has revealed that, as part of the ongoing legal battle between Apple and Epic Games, Apple subpoenaed Valve Software in November 2020, demanding it provide huge amounts of commercial data about Steam sales and operations going over multiple years. Apple is demanding Valve – who is not a party to this lawsuit in any way, shape, or form – provide Apple with detailed data and information about, initially, every single game sold on Steam, including “names, prices, configurations and dates of every product on Steam, as well as detailed accounts of exactly how much money Steam makes and how it is all divvied-up”. Apple later scaled this down to just the top 600 games on Steam. Valve is not having any of it, of course. Valve’s argument goes on to explain to the court that it is not a competitor in the mobile space (this is, after all, a dispute that began with Fortnite on iOS), and makes the point that “Valve is not Epic, and Fortnite is not available on Steam.” It further says that Apple is using Valve as a shortcut to a huge amount of third party data that rightfully belongs to those third parties. The conclusion of Valve’s argument calls for the court to throw Apple’s subpoena out. “Somehow, in a dispute over mobile apps, a maker of PC games that does not compete in the mobile market or sell ‘apps’ is being portrayed as a key figure. It’s not. The extensive and highly confidential information Apple demands about a subset of the PC games available on Steam does not show the size or parameters of the relevant market and would be massively burdensome to pull together. Apple’s demands for further production should be rejected.” This feels weird and wrong in so many ways, so much so that it almost feels as if Apple is trying to gain insight into a massive market – PC games – that it is not a part of – yet. The amount and detailed nature of the data Apple is requesting is so bizarre and over the top, that the only logical conclusion I can draw is that Apple wants this data for potential competitive purposes, and not for legal purposes at all.

You may have noticed that it’s kind of hard to find any new graphics card as of late, since supplies are limited for a whole variety of reasons. For the launch of its upcoming RTX 3060 GPU, which might prove to be a relatively affordable and capable upgrade for many, NVIDIA is going to try and do something about the shortage – by crippling the card’s suitability for cryptominers. RTX 3060 software drivers are designed to detect specific attributes of the Ethereum cryptocurrency mining algorithm, and limit the hash rate, or cryptocurrency mining efficiency, by around 50 percent. To address the specific needs of Ethereum mining, we’re announcing the NVIDIA CMP, or, Cryptocurrency Mining Processor, product line for professional mining. CMP products — which don’t do graphics — are sold through authorized partners and optimized for the best mining performance and efficiency. They don’t meet the specifications required of a GeForce GPU and, thus, don’t impact the availability of GeForce GPUs to gamers. It’s a good first step, I guess, but I feel the market is so starved at the moment this will be a drop in the ocean.

Today, we are introducing the next feature update to Windows 10, version 21H1. As people continue to rely on Windows more than ever to work, learn and have fun, we understand the importance of providing the best possible update experience to help people and organizations stay protected and productive. It is a responsibility we do not take lightly and why for the first time an H1 (first half of the calendar year) feature update release will be delivered in an optimized way using servicing technology, while continuing our semi-annual feature update cadence. In today’s blog I will cover details on how we plan to service the release, its scope, and next steps. Since I’ve lost track of the Windows release process and everything feels random and messy, I’m just going to say nothing at all.

The KDE team has released Plasma 5.21, and this is one hell of a release. They’ve paid a lot of attention to presentation for this release, with visual improvements in both first and third party applications, including a new main menu (the old menu, as well as the basic cascading menu, are of course still available if you want them). On the application front, Plasma 5.21 introduces the System Monitor, a brand new resource and task manager that gives you all the information you’d ever need on your running system – and in true KDE fashion, it includes the ability to create your own personalised pages with just the information you need. Another big focus was Wayland: We have extensively refactored the compositing code in KWin and the changes should reduce latency throughout all compositing operations. We have also added a control in the compositing settings so you can choose whether you prefer lower latency or smoother animations. In addition, we have also added support for mixed-refresh-rate display setups on Wayland, e.g. you can have one screen refreshing at 144Hz and another at 60Hz, which is ideal for improving work-stations with multiple monitors. Preliminary support for multiple GPUs was also added on Wayland. There’s much more in this release, and I’m excited to try it out.

Go 1.16 has been released. The new embed package provides access to files embedded at compile time using the new //go:embed directive. Now it is easy to bundle supporting data files into your Go programs, making developing with Go even smoother. You can get started using the embed package documentation. Carl Johnson has also written a nice tutorial, “How to use Go embed”. Go 1.16 also adds macOS ARM64 support (also known as Apple silicon). Since Apple’s announcement of their new arm64 architecture, we have been working closely with them to ensure Go is fully supported; see our blog post “Go on ARM and Beyond” for more. More details can be found in the release notes.